Hi, first of all thanks for the feedback, but I'm stuck again.
> > There are few device specific kernel modules (eg. wireless, bluetooth) > > what's the correct way to deal with them? I assume they should be built > > as separate packages, as not all kirkwood based devices need them. > > Exactly, if they are not packaged, they should be packaged in > package/kernel/modules/*.mk I've changed the following files: package/kernel/modules/crypto.mk - HW AES accelerator package/kernel/modules/block.mk - SATA package/kernel/modules/other.mk - MMC Card reader - Bluetooth, firmware req. package/kernel/modules/wireless.mk - wireless µAP, firmware req. The following issues are left: 1) Firmware Both bluetooth and wireless requires firmware files to be loaded. The whole firmware is a set of four files. It would be wrong to bundle the firmware with either bluetooth or wireless, as this would created a additional dependency. Instead I'm trying to create a firmware package, but I found no example of a "copy only files" package (a package without need for compiling etc.). Can someone point me to an example? 2) UBIFS/UBI Block Device The default root filesystem for guruplug is UBIFS, which is a appropriate choice, considering the 512MB NAND Flash available. UBIFS isn't available, and changing this in package/kernel/modules/fs.mk and package/kernel/modules/block.mk is the wrong way. Instead it should be possible to choose UBIFS as root file system (like ext2, jffs2 or squashfs) in "Traget Images". Is this task already ongoing? Another issue is that boot from UBIFS requires CRC16 static in the kernel, not as module. The package kmod-crc16 is no longer available for this, but kmod-bluetooth requires kmod-crc16. How can this be solved? Roland _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
