324918de46
The gma500_gfx driver will match certain devices on which it causes incorrect functionality, we want to avoid inserting this module, basicallly blacklist it for specific hardware, but still allow it to work on other hardware by default; usually when we have an already working system, using udev rules would do the job, but since we are building it, it is impossible to blacklist a driver when a certain udev rule matches, since rootfs isn't writeable at this point during boot time, the solution is to use modprobe install, which runs a certain command instead of inserting a matching module this command needs to insert the module manually afterwards and have a flag --ignore-install so it doesn't create an infinite loop executing itself everytime it wants to insert the module, busybox's modprobe doesnt provide this functionality, so a small hack had to be used to avoid the infite loop instead. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| intel-core2-32.conf | ||
| intel-corei7-64.conf | ||
| intel-quark.conf | ||
| README | ||
The intel-* BSPs, also known as the intel-common BSPs, provide a few carefully selected tune options and generic hardware support to cover the majority of current Intel CPUs and devices. The naming follows the convention of intel--, where TUNE is the gcc cpu-type (used with mtune and march typically) and BITS is either 32 bit or 64 bit.
intel-core2-32 This BSP is optimized for the Core2 family of CPUs as well as all Atom CPUs prior to the Silvermont core.
intel-corei7-64 This BSP is optimized for Nehalem and later Core and Xeon CPUs as well as Silvermont and later Atom CPUs, such as the Baytrail SoCs.
These BSPs use what we call the intel-common Linux kernel package architecture. This includes core2-32-intel-common and corei7-64-intel-common. These kernel packages can also be used by any of the BSPs in meta-intel that choose to include the intel-common-pkgarch.inc file. To minimize the proliferation of vendor trees, reduce the sources we must support, and consolidate QA efforts, all BSP maintainers are encouraged to make use of the intel-common Linux kernel package architecture.
Of the BSPs presently included in meta-intel, the following have passed initial testing with the intel-common BSPs (rather than the named BSP):
For intel-corei7-64: crystalforest-server crystalforest-gladden haswell-wc nuc (Ivy Bridge and Haswell, manual audio config required) sugarbay
For intel-core2-32:
If you are interested in a BSP not listed here, chances are we are currently working on resolving some configuration issues with it. Please check the bugzilla and check in with us on the meta-intel mailing list.