summaryrefslogtreecommitdiffstats
path: root/meta-phosphor/classes/config-in-skeleton.bbclass
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2016-09-14 20:40:07 +0930
committerPatrick Williams <patrick@stwcx.xyz>2016-09-21 12:49:55 +0000
commit0eb7c392d8fe24b390c04fba05af70d8cf8c7638 (patch)
treed57e72d66566866835f323cfe728834f54088824 /meta-phosphor/classes/config-in-skeleton.bbclass
parented52dc14feeeceda50b3f2d58515587eb81b6b42 (diff)
downloadtalos-openbmc-0eb7c392d8fe24b390c04fba05af70d8cf8c7638.tar.gz
talos-openbmc-0eb7c392d8fe24b390c04fba05af70d8cf8c7638.zip
linux-obmc: Work around host IPL issues using GPIO hogs in Palmetto devicetree
The commit message in the kernel patch applied by this commit outlines the critical information on how it was generated and the limitations that apply to using GPIO hogs to produce a bootable host. Please refer to the kernel patch commit message. Note the patch is best applied during the OpenBMC build process, rather than being carried by the OpenBMC kernel fork. The OpenBMC kernel fork is used to test Aspeed SoC support at large, often with non-OpenBMC userspaces. While the OpenBMC userspace is sometimes not used in kernel testing, the tests often take place on OpenBMC supported machines such as the Palmetto. As kernel development and maintenance often includes exporting various GPIOs to poke at, it's best that we minimise the number of GPIOs tied up in hogs. It's acknowledged that this opens an opportunity for predictable flaws if a kernel is booted with the OpenBMC userspace without this patch applied, but it's assumed the user knows what they are doing in this case*. * Having said that, it will no doubt trip me up. Change-Id: I08f5f5b29cc81257655bb9a35dbb6c5ce3f11292 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Diffstat (limited to 'meta-phosphor/classes/config-in-skeleton.bbclass')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud