Searched hist:ace36475 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/openbmc/meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/ |
| H A D | defconfig | ace36475 Sun Jul 11 23:21:15 CDT 2021 Joel Stanley <joel@jms.id.au> linux-aspeed: Disable IPV6 SIT device
No one is using this device on OpenBMC systems, and there is no
code to manage it in phosphor-networkd as of March 2021:
> [...] if you don't add IPv6 addresses to the sit interface
> it doesn't do anything. The defacto way to do that on an interface in
> OpenBMC is to have it managed by phosphor-networkd. On top of this, to
> support sit you would need a way to configure the local / remote IPv4
> addresses used to back it. You can configure the linux kernel to build
> sit functionality but not create sit devices by default (I don't know
> how they haven't changed this yet in default kconfigs...) and it will
> still let you make them on the fly.
Facebook and Google systems force this option off already:
meta-facebook/meta-tiogapass/recipes-kernel/linux/linux-aspeed/tiogapass.cfg:CONFIG_IPV6_SIT=n
meta-google/recipes-kernel/linux/files/gbmc.cfg:CONFIG_IPV6_SIT=n
Change-Id: I9df02c761e82eeb2cca562bf68b9b755bc6feeb9
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
| /openbmc/openbmc/meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/ |
| H A D | defconfig | ace36475 Sun Jul 11 23:21:15 CDT 2021 Joel Stanley <joel@jms.id.au> linux-aspeed: Disable IPV6 SIT device
No one is using this device on OpenBMC systems, and there is no
code to manage it in phosphor-networkd as of March 2021:
> [...] if you don't add IPv6 addresses to the sit interface
> it doesn't do anything. The defacto way to do that on an interface in
> OpenBMC is to have it managed by phosphor-networkd. On top of this, to
> support sit you would need a way to configure the local / remote IPv4
> addresses used to back it. You can configure the linux kernel to build
> sit functionality but not create sit devices by default (I don't know
> how they haven't changed this yet in default kconfigs...) and it will
> still let you make them on the fly.
Facebook and Google systems force this option off already:
meta-facebook/meta-tiogapass/recipes-kernel/linux/linux-aspeed/tiogapass.cfg:CONFIG_IPV6_SIT=n
meta-google/recipes-kernel/linux/files/gbmc.cfg:CONFIG_IPV6_SIT=n
Change-Id: I9df02c761e82eeb2cca562bf68b9b755bc6feeb9
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
| /openbmc/openbmc/meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/ |
| H A D | defconfig | ace36475 Sun Jul 11 23:21:15 CDT 2021 Joel Stanley <joel@jms.id.au> linux-aspeed: Disable IPV6 SIT device
No one is using this device on OpenBMC systems, and there is no
code to manage it in phosphor-networkd as of March 2021:
> [...] if you don't add IPv6 addresses to the sit interface
> it doesn't do anything. The defacto way to do that on an interface in
> OpenBMC is to have it managed by phosphor-networkd. On top of this, to
> support sit you would need a way to configure the local / remote IPv4
> addresses used to back it. You can configure the linux kernel to build
> sit functionality but not create sit devices by default (I don't know
> how they haven't changed this yet in default kconfigs...) and it will
> still let you make them on the fly.
Facebook and Google systems force this option off already:
meta-facebook/meta-tiogapass/recipes-kernel/linux/linux-aspeed/tiogapass.cfg:CONFIG_IPV6_SIT=n
meta-google/recipes-kernel/linux/files/gbmc.cfg:CONFIG_IPV6_SIT=n
Change-Id: I9df02c761e82eeb2cca562bf68b9b755bc6feeb9
Signed-off-by: Joel Stanley <joel@jms.id.au>
|