In order to use the LAN9512 chip, we had to use a custom yocto kernel using bitbake linux-yocto -c menuconfig to add the smsc95xx.ko module. In order to add our own scripts and allow others to contribute to our work, we are currently storing the inflated root filesystems in their own repos (yocto and debian). Our src/package.sh script creates a compatible image out of the specified repo for flashing.
Ideally, we would have a custom BitBake layer(s) for a Debian-based distro that included the smsc95xx module, along with any other custom scripts/utilities (i.e., the macchanger script).
Currently, in the Intel Edison Yocto Linux Source, there is a directory in ./out/current/poky named meta-skeleton. This could probably be used to model a new BitBake layer with the correct parameters for Debian.
This would allow people to truly contribute to source, and not the inflated filesystem.
In order to use the LAN9512 chip, we had to use a custom yocto kernel using
bitbake linux-yocto -c menuconfigto add thesmsc95xx.komodule. In order to add our own scripts and allow others to contribute to our work, we are currently storing the inflated root filesystems in their own repos (yocto and debian). Oursrc/package.shscript creates a compatible image out of the specified repo for flashing.Ideally, we would have a custom BitBake layer(s) for a Debian-based distro that included the
smsc95xxmodule, along with any other custom scripts/utilities (i.e., the macchanger script).Currently, in the Intel Edison Yocto Linux Source, there is a directory in
./out/current/pokynamedmeta-skeleton. This could probably be used to model a new BitBake layer with the correct parameters for Debian.This would allow people to truly contribute to source, and not the inflated filesystem.