summaryrefslogtreecommitdiffstats
path: root/meta/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
...
* feature-arm-thumb: respect ARM_INSTRUCTION_SETMartin Jansa2011-08-011-1/+2
| | | | | | | | (From OE-Core rev: e23f9ce928353c9da2b9c4bfa9a1a125a7d160f2) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-xscale: fix xscale/xscale-be confusionDmitry Eremin-Solenikov2011-08-011-1/+1
| | | | | | | | | | | Currently tune-xscale.inc has options wrt. setting of xscale/xscale-be tunes. Fix that. (From OE-Core rev: 90ce6e4b7ffaaf1e3af39583ca62b20f08e78959) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-armv6, arch-armv5-dsp: correct endianness confusionPhil Blundell2011-08-012-6/+6
| | | | | | | | | | | | | | | | | | | PACKAGE_EXTRA_ARCHS_tune-armv5eb needs to be defined in terms of the non-e with the same endianness, i.e. PACKAGE_EXTRA_ARCHS_tune-armv5b not PACKAGE_EXTRA_ARCHS_tune-armv5, otherwise PACKAGE_EXTRA_ARCHS will end up containing a semi-random mixture of endiannesses and disaster will ensue. Likewise for the vfp and armv6 variants. This is all a bit confusing because TUNE_FEATURES is done the opposite way around, i.e. TUNE_FEATURES_tune-armv5eb is derived by taking the armv5e version and adding bigendian. But fixing that is probably a subject for a separate patch. (From OE-Core rev: 391c0102a81455c76244d13b6878e3a76cca65dc) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortex{m1, m3, r4}: correct spelling of "cortex"Phil Blundell2011-08-013-4/+3
| | | | | | | | | | Otherwise the test in TUNE_CCARGS will never match. (From OE-Core rev: 3b7784021259ac745c80043bec16189fa8f4e45e) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add basic PowerPC core tune configRichard Purdie2011-07-277-18/+96
| | | | | | (From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add basic Mips core tune configRichard Purdie2011-07-272-3/+76
| | | | | | | Acked-by: Mark Hatle <mark.hatle@windriver.com> (From OE-Core rev: b33cdc23c04acfa55df0f764e1648bf030ae5e9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add ARM tune file overhaul based largely on work from Mark HatleRichard Purdie2011-07-2723-74/+435
| | | | | | (From OE-Core rev: 789dcb8e68a2ab9784ac10ab36815010c61af2fc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemu: set preferred linux-yocto kernel versionBruce Ashfield2011-07-271-0/+1
| | | | | | | | | | | The introduction of the linux-yocto-3.0 kernel is taking precedence over the known working 2.6.37 version. Forcing 2.6.37 until 3.0 is validated on the qemu machines. (From OE-Core rev: 77a41ab5ca92606ee08f002a8dfc631f642a3179) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2.inc: Drop X86ARCH32 usageRichard Purdie2011-07-271-1/+0
| | | | | | | | | Using i686 doesn't work well with locale generation and doesn't gain anything so revert to the i586 default. (From OE-Core rev: 79b7b1aab5d3d002bfa7a49887d5d834c29eae45) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-ia32.inc: Fix up TUNE_ARCH variable conflictsRichard Purdie2011-07-262-3/+5
| | | | | | | | | The current approach causes duplicate values to appear in the TUNE_ARCH field and this patch addresses that. (From OE-Core rev: 02031d766f983cd7e01e468cb2c926604313cd2a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Rename SITEINFO_ENDIANESS to SITEINFO_ENDIANNESSKhem Raj2011-07-261-2/+2
| | | | | | | | | | | | | There is this discrepency in spelling. Lets fix it in core. There are lot of layers using SITEINFO_ENDIANNESS This was shielded since meta-oe had its own copy of siteinfo class. But that class has now been deleted in favor of oe-core (From OE-Core rev: 54a54778fad39931ac7d43daaf37ce7c1946a29b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Move architecture specific TARGET_OS mangling into tune filesRichard Purdie2011-07-252-0/+4
| | | | | | (From OE-Core rev: f10a3457cdfbb4a94978da998d178d4254632fa7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: Start to fill out architecture specific tune include ↵Richard Purdie2011-07-2528-35/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | files and tune features These changes revolve around the idea of tune features. These are represented by 'flag' strings that are included in the TUNE_FEATURES variable. Any string included in TUNE_FEATURES should also add a TUNEVALID[<name>] entry so we can know which flags are available in TUNE_FEATURES and have documentation about what the flags do. We will add sanity code to error if flags are listed in TUNE_FEATURES but are not documented in TUNEVALID. A given tune configuration will want to define one or more predetermined sets of _FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-<name>. For defined tune configuation, <name> should be added to the AVAILTUNE list so that we can determine what tune configurations are available. Flags cannot be used in this case as with TUNEVALID since its useful to be able to build up tune lists from other TUNE_FEATURES_tune-yyy options. A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune-<name> and BASE_LIB_tune-<name> to control the multilib location. All options can be overridden by the distro or local user configuration. (From OE-Core rev: 5f9d56bd64997b93ed7e46c117851002a0556654) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCHRichard Purdie2011-07-2527-31/+31
| | | | | | | | | | | | | | Since we're updating the tune file format, it makes sense to abstract the compiler tune arguments at this point too. This means that should these need to be overridden at any point, the original values can still be obtained in a similar manner to the other TUNE* variables. Whilst this isn't strictly necessary for any current need, its likely good practise to standardise this behaviour. (From OE-Core rev: 3a3c69a1bc3cf0b6f6a3b13d86c12ed21798d48e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/tune: Overhaul tune include file variablesRichard Purdie2011-07-2531-54/+87
| | | | | | | | | | | | | | | | | | | | | | There is currently consideradble confusion over how the tune files operate and how these interact with the rest of the build system. This update/overhaul changes things so the tune files are primarily resonsible for setting: TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that represents the architecture we're targetting. TUNE_PKGARCH - The value that represents the tune confuration that this set of tune parameters results in. This allows the significant improvement that the core can now always determine the target architecture value, even when TARGET_ARCH needs to be reset to something different and likewise, there is one package architecture variable the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH and FEED_ARCH variables. (From OE-Core rev: a10de4cf8b424ee95c8e283e75d486be5b3b8eac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-ppce500mc: Add a tune file for PowerPC e500mc coreKumar Gala2011-07-201-0/+4
| | | | | | | (From OE-Core rev: 8f37792dc422f81e39e3b32df5e56d915c87216f) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-ppce500v2: Add a tune file for PowerPC e500v2 coresKumar Gala2011-07-201-0/+4
| | | | | | | (From OE-Core rev: 1448b6381b2039d0da7ab06c522d973bd8126747) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "qemu.inc: append to IMAGE_FSTYPES instead of weakly assigning them"Richard Purdie2011-06-141-1/+1
| | | | | | This reverts commit a205c32dcb229e30c5e8eead1472593fc8bc96a6. This was accidentally committed.
* qemu.inc: append to IMAGE_FSTYPES instead of weakly assigning themKoen Kooi2011-06-141-1/+1
| | | | | | | | | The ext3 format is pretty much mandatory for qemu usage, so always create it. (From OE-Core rev: 94da548810eece652bd32fb68a36f978b7d7cf2a) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* IMAGE_ROOTFS_SIZE CleanupSaul Wold2011-05-251-2/+0
| | | | | | | | | | | | | | | | | This basic cleanup removes the _ext2/3 overrides from places they no longer belong since they did not allow further overrides. In doing this the core-image-minimal* recipes can now set a reasonably small rootfs so that it's a realistic size for minimal. The new default for minimal is 8M and will be adujsted upward by the IMAGE_OVERHEAD_FACTOR (default of 1.3). This also fixes the ROOTFS_SIZE usage in the IMAGE_CMD_<fstype> code (From OE-Core rev: d3f6e1e6106ab539e73c19037915b2e4a5f2efa9) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu machines: drop MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "qemu-config"Koen Kooi2011-05-231-1/+0
| | | | | | | | | Things like 'distcc' and 'bash' are not essential to booting a qemu machine. (From OE-Core rev: 65f1109faf9548c5d083089561d5b9d99dbacc83) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop unused *GUI* and MACHINE_DISPLAY variablesRichard Purdie2011-05-111-2/+0
| | | | | | (From OE-Core rev: baf136a9c95a94c5bf89c9a818960d616439682c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemu: Add qemu-config as an essential machine speicfic dependency ↵Richard Purdie2011-05-113-2/+3
| | | | | | | | and drop specific distro config (From OE-Core rev: 617b8f2ae26a6b4ac57795fead39ef20b1f92ecc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuppc: add libqtopengl4 for ppcMei Lei2011-04-041-0/+2
| | | | | | | | | | Modify some configs for ppc to enable the libqtopengl4 support. This fixes [YOCTO #848] (From OE-Core rev: cc6763b81fafddcb112a6126373c594e3ec4b140) Signed-off-by: Mei Lei <lei.mei@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/include/tune-atom.inc: Remove FULL_OPTIMIZATION_pn-gtk+Khem Raj2011-03-241-4/+0
| | | | | | | | | | * Since bitbake.conf has got rid of -fomit-frame-pointer this is no longer required (From OE-Core rev: ba89ba8e02185c7adb92240f119a57e7b21adfa7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/tune files: Adjust PACKAGE_EXTEA_ARCHSRichard Purdie2011-03-2314-14/+14
| | | | | | | | | | | | | | | | | | | | | There is a problem with the current PACKAGE_EXTRA_ARCHS implementation since its impossible to control which extra architectures sort higher than TARGET_ARCH and which sort lower. In the x86 case for example, TARGET_ARCH might be "i586", i486 should be lower than this and i686 should be higher. There are also complications where its easy to inject duplicate entries into the variable. I tried various versions of this patch and concluded that it was simplest just to force the tune files to include TARGET_ARCH in the list in the right place if they're planning to customise it themselves. Other approaches with appends and prepends just complicated the code for no good reason. The TARGET_ARCH definitions should also move to the tune files but I'll leave this for a separate patch. (From OE-Core rev: d492ebf8b1801da99c679f465be98ce54fd3061a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* atom-pc: work around gcc bug for core2Darren Hart2011-03-171-0/+4
| | | | | | | | | | | | | | Fixes [YOCTO #853] Without these added optimization flags, the matchbox-panel (and possibly other) applications would segfault. This patch applies the changes to all machines derived from atom-pc.conf. [Tweaked by RP to apply to gtk+ only] (From OE-Core rev: 5eb24b1cb57d1e0b43dfc993a635cd2b58d58fcf) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-atom.inc: Remove duplicate TARGET_ARCH entry to avoid ipk rootfs issues ↵Richard Purdie2011-03-151-1/+1
| | | | | | | | as temp workaround for problems pending a proper fix (From OE-Core rev: a39610f0ac4c77f225671916610f78a18ff70350) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto: Move files inappropriate to OE-Core from metaRichard Purdie2011-03-034-127/+0
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine: Use linux-libc-headers instead of linux-libc-headers-yoctoRichard Purdie2011-02-254-4/+4
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-intel: add config option to support rootless XYu Ke2011-02-231-0/+2
| | | | | | | | | | | - add global config option ROOTLESS_X to control if enable rootless X for the machine. ROOTLESS_X requires graphics driver supporting KMS (kernel mode setting), so far, only atom_pc support this. so enable ROOTLESS_X for atom_pc machine - add config options for xf86-video-intel to support rootless X Signed-off-by: Yu Ke <ke.yu@intel.com>
* zaurus: remove zaurus linux includesDarren Hart2011-02-212-87/+0
| | | | | | | | | | | | Zaurus support was removed with: 673abd92f999829bdd67d0273c43570a62123a63 conf/machine: Drop older machines with no recent updates which removed both the linux-rp and sharp-flash-header recipes required by the zaurus includes removed by this patch. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* conf/machine: Drop older machines with no recent updatesRichard Purdie2011-02-1817-517/+0
| | | | | | | | | These are all moving to meta-extras. Ideally in the future machines such as these will be maintained to topic specific layers as we move to a more layer oriented model. If this causes a problem for anyone please discuss it on the mailing list. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mpc8315-rdb: add dtb generation configurationBruce Ashfield2011-02-091-0/+1
| | | | | | | | | | Fixes [BUGID #610] dtb files were not being built for the mpc8315e-rdb, since they weren't being configured into the machine. With this and the related dtc fixes, we now get a dtb in the deployment directories. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* beagleboard: allow kernel provider overrideDarren Hart2011-02-071-1/+1
| | | | | Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
* beagleboard: set kernel provider to linux-yocto (2.6.37)Darren Hart2011-02-031-1/+1
| | | | | | | | | Support has been added for basic Beagleboard xM functionality, including networking, to the linux-yocto kernel repository. Tested on the Beagleboard xM. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
* mpc8315e-rdb: set UBOOT_ENTRYPOINTBruce Ashfield2011-02-011-0/+3
| | | | | | | | | | Fixes [BUGID #685] Although not used if the in kernel uImage is booted, it is a good idea to set the UBOOT_ENTRYPOINT just as the other uImage based boards do. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* beagleboard: Not ready for 2.6.37 kernel yet, use stable insteadSaul Wold2011-01-241-1/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* overo: use the new upstream u-boot recipeDarren Hart2011-01-211-1/+1
| | | | | | | | | In preparation to remove the u-boot-omap3 recipe, update the overo machine to use the new upstream u-boot recipe. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
* beagleboard: add x-load and u-boot dependsDarren Hart2011-01-211-0/+3
| | | | | | | | | The Beagleboard xM requires x-load and u-boot to be installed on the MMC as it has no NAND (as of rev B and onward). Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
* machine/qemu: Allow for users to override the preferred kernel versionDarren Hart2011-01-201-1/+1
| | | | | | | | The linux-yocto-rt kernel has been boot tested on qemux86-64. Unlock the preferred provider for virtual/kernel so it can be selected and used. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
* linux-yocto: beagleboard enablementBruce Ashfield2011-01-191-3/+3
| | | | | | | | | | | | Enable beagleboard support for 2.6.37. The only non-kernel related change for the board is to update the serial console designation. The Beagleboard use omap serial driver, so we replace ttyS2 with ttyO2. This is described in following link: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg40838.html Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Liming Wang <liming.wang@windriver.com>
* linux-yocto: add routerstation pro and mpc8315e-rdb supportBruce Ashfield2011-01-122-4/+4
| | | | | | | | | The routerstation pro and mpc8315e-rdb have been validated on 2.6.37 so we can switch their preference to linux-yocto and update the machine compatibility to add them to the support list. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* machines: move PACKAGE_EXTRA_ARCHS to tune filesKoen Kooi2011-01-1041-29/+38
| | | | | | | | This gets us closer to making including tune-<arch>.inc "just work". Moving the TARGET_ARCH definitions is something for a follup patch. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: match kernel headers to preferred kernelBruce Ashfield2010-12-231-1/+1
| | | | | | | | | As the yocto-kernel advances, the libc headers must also advance. This commit fixes the SRC_URI and SRCPV to work properly with the latest linux-yocto kernel. It also switches the qemu* targets to prefer this libc recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* yocto-kernel: factor common routes, update to 2.6.37 and branch renamingBruce Ashfield2010-12-105-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to extend and create more kernel recipes based on the supported yocto kernel common routines need to be placed in re-usable blocks. To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb is broken into three parts: - meta/classes/kernel-yocto.bbclass: contains common routines for checking out and configuring a yocto kernel git repository. This should be inherited by recipes that need this functionality. - meta/recipes-kernel/linux/linux-yocto.inc: Contains the machine mappings, compatibility, build directives and common task definitions for a yocto kernel based recipe. This inherits kernel-yocto, and is the typical point of entry for other recipes. - meta/recipes-kernel/linux/linuux-tools.inc: tasks and function definitions for kernel recipes that want to build/export perf It also updates the linux-yocto recipe to default to 2.6.37. As part of the update to 2.6.37 the branch naming and conventions have been modified to show inheritance, and be more generic. For example: master meta yocto/base yocto/standard/arm_versatile_926ejs yocto/standard/base yocto/standard/beagleboard yocto/standard/common_pc/atom-pc yocto/standard/common_pc/base yocto/standard/common_pc_64 yocto/standard/fsl-mpc8315e-rdb yocto/standard/intel_atom_z530 yocto/standard/intel_core_qm57_pch yocto/standard/mti_malta32_be yocto/standard/preempt_rt/base yocto/standard/preempt_rt/common_pc yocto/standard/preempt_rt/common_pc_64 yocto/standard/preempt_rt/intel_atom_z530 yocto/standard/preempt_rt/intel_core_qm57_pch yocto/standard/qemu_ppc32 yocto/standard/routerstationpro In this structure: master: tracks the mainline kernel meta: meta information for the BSPs and kernel features yocto/base: baseline kernel branch yocto/standard/base: 'standard' kernel, contains features and configs for all BSPs yocto/standard/<machine>: represents a BSP with specific features or configurations The tools, tree and libc-headers have all been updated to deal with this new structure. Also in addition to dealing with the new structure, they continue to work with the existing tree and will adapt at runtime to the differences. The linux-yocto-stable_git.bb recipe continues to build the 2.6.34 based tree,and linux-yocto_git.bb builds 2.6.37. As boards are enabled for the new kernel they will move from -stable to the development kernel. As of now, only the emulated targets have moved to 2.6.37-rcX Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH.Lianhao Lu2010-12-101-0/+1
| | | | | | | | | | | Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH for cross-canadian packages. This is due to the TARGET_ARCH of x86_64 would results incorrect packaging in cross-canadian packages. The pacakge name appendix of x86_64 target in cross-canadian packages is x86-64. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* linux-wrs: rename to linux-yoctoBruce Ashfield2010-11-185-5/+5
| | | | | | | | | | | | | | | | | | The existing preferred yocto kernel wasn't named appropriately and needs to be updated. In keeping the changes small and isolated, this commit simply renames the recipe and some internal variables. Future commits will refactor the code into more usable blocks. Now that linuy-wrs has been renamed linux-yocto, we need to rename and update an board configurations and append files. Now that linux-wrs has been renamed linux-yocto, we need to update the SRCREVs to have the new name. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* mpc8315e-rdb: align PACKAGE_EXTRA_ARCHS with tuningBruce Ashfield2010-10-211-1/+1
| | | | | | | | | | | | Fixes [BUGID #500] While the tuning for the mpc8315e is 603e, the PACKAGE_EXTRA_ARCHES was ppce300. This created a mismatch and resulted in rootfs assembly issues due to missing locales. We align both at 603 and can revist a better tuning in the future. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* atom-pc: remove kernel video mode parametersDarren Hart2010-10-151-1/+1
| | | | | | | | | | | | | | | | | The kernel video mode parameters are not needed with the atom-pc linux-wrs configuration. Without them, we boot up with a standard 80x25 text display until the Intel i915 driver is initialized, at which point we switch to a higher resolution text mode. Afterwards, a sato image will start the splash screen and successfully boot to X. Tested on the Toshiba NB305 netbook and the Black Sand development board. [BUGID #450] Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com> CC: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-07 15:00:36 +0000