From: Scott E. <sc...@ju...> - 2013-06-05 14:15:39
|
I don't have any answers about your particular USB device. To add/remove modules to your kernel you can directly modify the defconfig if you are confident you know the changes or you can run the kernel config tool as you did with OE classic like this bitbake -c menuconfig virtual/kernel When it's done and you've saved the changes, the new config will be found here $TMPDIR/work/overo-poky-linux-gnueabi/linux-gumstix/<kernel-version>/git/.config If you are using the meta-gumstix kernel layer unmodified you can replace the defconfig that it uses <some-dir>/meta-gumstix/recipes-kernel/linux/linux-gumstix-3.5/overo/defconfig If you have your own layer then you probably want to create recipes-kernel/linux directory with a .bbappend for the kernel recipe and a subdir for the custom defconfig and any custom patches you might have. To rebuild after a defconfig change I always use bitbake -ccleansstate virtual/kernel && bitbake virtual/kernel There should be an ipk or maybe rpm directory under $TMPDIR/deploy/ Supposing it's ipk, then under $TMPDIR/deploy/ipk/overo you'll find a bunch of kernel-module-<driver>*.ipk packages that got built with the kernel. You can manually try installing any of these for testing. You can also add them to your image recipe explicitly if for some reason you are not finding them on your image now. Hope that helps. -- View this message in context: http://gumstix.8.x6.nabble.com/D-Link-USB-Ethernet-Adapter-tp4967366p4967368.html Sent from the Gumstix mailing list archive at Nabble.com. |