2015-09-25 10:26 GMT+03:00 Guillaume Gardet
Hi,
Le 24/09/2015 21:30, Matwey V. Kornilov a écrit :
24.09.2015 20:27, Matwey V. Kornilov пишет:
Hello,
In JeOS.kiwi for armv7hl I see the following:
<drivers> <file name="drivers/ata/*"/> <!-- For SATA --> <file name="drivers/dma/*"/> <!-- For DMA --> <file name="drivers/gpio/*"/> <!-- Needed for TWL6040 GPO for MMC boot on pandaboard --> <file name="drivers/gpu/*"/> <!-- For display --> <file name="drivers/mmc/*"/> <!-- For SD/MMC --> <file name="drivers/phy/*"/> <!-- Various phy: sata, usb, video, ... --> </drivers>
but in the generated initrd I see that all drivers are present:
lib/modules/4.3.0-rc2-1.g2b75354-default/kernel/drivers> ls ata cdrom dma gpu hwmon input media mfd mmc ntb phy ptp soc thermal uwb video block char gpio hid iio md message misc net parport pps scsi ssb usb vhost virtio
And I cannot understand how this is supposed to work. What <drivers> is used for?
There is a predifined list of drivers to include (in kiwi) and we also had those within <drivers> and </drivers>.
I am sorry, I don't still understand. Both initrd and main image carries all existing kernel modules. Why do we need to specify something? Isn't it supposed that not all kernel modules have to be present inside initrd? For instance, initrd has parport/*.ko. Could you show me ARM board with LPT onboard, and explain why do we ever need LPT at boot time?
Also, why do we need /usr/lib/ldscripts provided by binutils inside initrd? Who is going to link something?
Marcus ?
I failed to learn how to build dependency graphs with zypper. binutils is pulled as requirement of some other package, but I don't know how to easily find what package. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org