mirror of
https://git.yoctoproject.org/poky
synced 2026-05-08 05:09:24 +00:00
Petr Štetiar
46197c431d
In the current state, udev init script is loaded as 3rd and modutils.sh as 20th, so udevadm called in udev init script loads all kernel modules in some unpredictable order, not honoring in any way specified order of modules in /etc/modules. This causes some troubles mainly in the first boot. So to fix this we now move loading of the kernel modules just before we exec udev init script. Example of the current state: Starting udev rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc0 rtc-m48t86 rtc-m48t86: battery ok ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc1 root@ts72xx:~# cat /etc/modules rtc-ep93xx ohci-hcd ts72xx_sbcinfo rtc-m48t86 As you can guess, this is really wrong behaviour, because I've rtc1 as the main time source for my system. root@ts72xx:~# cat /etc/default/hwclock HWCLOCKACCESS=yes HWCLOCKDEVICE=/dev/rtc1 Expected behaviour with this patch applied: Please wait: booting... ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0 usbcore: registered new device driver usb ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ... rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1 rtc-m48t86 rtc-m48t86: battery ok Starting udev (From OE-Core rev: a0629aa0dc55829565b7ab1725875eac065ab2f1) Signed-off-by: Petr Štetiar <ynezz@true.cz> (based on http://patches.openembedded.org/patch/1917/) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
====
Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.
Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a
reference manual which can be found at:
http://yoctoproject.org/community/documentation
For information about OpenEmbedded see their website:
http://www.openembedded.org/