using sato-sdk images in nightly build 20110305-4 http://autobuilder.pokylinux.org/nightly/20110305-4/machines/mpc8315e-rdb/ppc/ git info : c192fefd868be53c20dfd8bc44e3e815cf53a10a when the physical board boot up , insert a usb stick , the usb stick can not be detected by the physcial board. and found in the systems below : root@mpc8315e-rdb:~# cd /lib/modules/2.6.37.2-yocto-standard+/kernel root@mpc8315e-rdb:~# ls crypto fs net just as description added in defect 766 (comment 5): http://bugzilla.pokylinux.org/show_bug.cgi?id=766 the usb related modules is in the "drivers/usb/" subdir in the dir which created by decompressing the file modules-2.6.37.2-yocto-standard+-r16-mpc8315e-rdb.tgz , but the related modules not found in this sato-sdk images and the modules file not found in the nightly build dir above.
Can the .config from the linux build directory be attached to this case ?
Created attachment 108 [details] the mpc8315e-rdb kernel config file. kernel configuraton file.
(In reply to comment #1) > Can the .config from the linux build directory be attached to this case ? the attachment is the configuration file from the mpc8315e-rdb physical machine using command 'zcat /proc/config.gz'.
I see the updated kernel config option CONFIG_USB_FSL_MPH_DR in the attached config. As for why the modules aren't making it into sato image or night build directory, I can't say. The kernel part of this bug is complete, we should update this to a product where Beth (or someone) can check the autobuilders to see what was built, and then potentially pass this onto someone looking at the build system. I'm not sure what that product part should be.
Change the defect title due to the kernel part the bug is complete.
In the beagleboard sato-sdk images the drivers dir exists ,and usb stick do work.
the driver module "loop.ko" is needed by "Core test" from lsb test suite. so the modules package is necessary for lsb test on platfrom mpc8315e
Xiaofeng: we are mixing multiple issues here. Can you confirm that in your builds, you now see the USB_FSL_MPH kernel modules being built for the board ? And that the issue is that they are missing in nightly/SDK builds ? And that there's a second issue where loop.ko is missing and is required for tests ? Confirm this as well, and we can break it out into a separate bug.
Hi Bruce. We make lsb test with lsb-image from nightly build. We have no mpc8315e lsb-image compiled by ourselves. We have lsb-image for qemux86. I look at the result from command "make menuconfig" on qemux86 is below: ** USB Host Controller Drivers *** <M> Cypress C67x00 HCD support <M> xHCI HCD (USB 3.0) support (EXPERIMENTAL) [ ] Debugging for the xHCI host controller <*> EHCI HCD (USB 2.0) support [*] Root Hub Transaction Translators [*] Improved Transaction Translator scheduling <M> OXU210HP HCD support <M> ISP116X HCD support <M> ISP 1760 HCD support <M> ISP1362 HCD support <*> OHCI HCD support <*> UHCI HCD (most Intel and VIA) support <M> Elan U132 Adapter Host Controller <M> SL811HS HCD support <M> CF/PCMCIA support for SL811HS HCD <M> R8A66597 HCD support <M> Wireless USB Host Controller Interface (WHCI) driver (EXPERIMENTAL) <M> Host Wire Adapter (HWA) driver (EXPERIMENTAL) No USB_FSL_MPH. loop.ko which locate in the directory "lib/modules/2.6.37.3-yocto-standard\+/kernel/drivers/block/loop.ko" is needed by test item "Core test" from LSB Test Suite
I'm not quite following. For qemux86 you definitely won't see USB_FSL_MPH, since it depends on FSL Kconfig items and menuconfig will hide the option. I did enable that option for the BSP, my question for it is: - it's on for the BSP, is it showing up in the build directory, but not on the target rootfs ? As for loop.ko: - are you saying that it is in the build directory, but not on the target rootfs by default ?
(In reply to comment #10) > I'm not quite following. For qemux86 you definitely won't see USB_FSL_MPH, > since > it depends on FSL Kconfig items and menuconfig will hide the option. I did > enable > that option for the BSP, my question for it is: > > - it's on for the BSP, is it showing up in the build directory, but not on > the target rootfs ? > hi bruce, yes , it is showing up in the build dir,not the target rootfs. liang li > As for loop.ko: > > - are you saying that it is in the build directory, but not on the target > rootfs by default ?
(In reply to comment #10) > I'm not quite following. For qemux86 you definitely won't see USB_FSL_MPH, > since > it depends on FSL Kconfig items and menuconfig will hide the option. I did > enable > that option for the BSP, my question for it is: > > - it's on for the BSP, is it showing up in the build directory, but not on > the target rootfs ? > > As for loop.ko: > > - are you saying that it is in the build directory, but not on the target > rootfs by default ? Hi bruce, In the newest nightly build (for final release of 1.0) , loop.ko was found in modules file modules-2.6.37.3-yocto-standard+-r16-mpc8315e-rdb.gz , not in the target rootfs: decompressed the file modules-2.6.37.3-yocto-standard+-r16-mpc8315e-rdb.gz to /home/root dir: root@mpc8315e-rdb:~/lib/modules/2.6.37.3-yocto-standard+/kernel/drivers/block# p wd /home/root/lib/modules/2.6.37.3-yocto-standard+/kernel/drivers/block root@mpc8315e-rdb:~/lib/modules/2.6.37.3-yocto-standard+/kernel/drivers/block# l s cryptoloop.ko loop.ko nbd.ko liang li
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f8cddd74574756174a82c856cecdeb6f83b9dea5
verified on nightly build 20110824-1,drivers subdir now exists in rootfs of mpc8315e-rdb sato-sdk images,usb subdir and loop.ko also exists in the drivers subdir,see below: root@mpc8315e-rdb:/lib/modules/2.6.37.6-yocto-standard+/kernel# pwd /lib/modules/2.6.37.6-yocto-standard+/kernel root@mpc8315e-rdb:/lib/modules/2.6.37.6-yocto-standard+/kernel# ls crypto drivers fs lib net root@mpc8315e-rdb:/lib/modules/2.6.37.6-yocto-standard+/kernel/drivers# pwd /lib/modules/2.6.37.6-yocto-standard+/kernel/drivers root@mpc8315e-rdb:/lib/modules/2.6.37.6-yocto-standard+/kernel/drivers# ls block char crypto hid mmc net scsi usb watchdog git info: f8cddd74574756174a82c856cecdeb6f83b9dea5 git branch: poky/master
usb stick now work normally.