On Thu, 2010-10-14 at 20:33 +0100, davidMbrooke wrote: > On Thu, 2010-10-14 at 10:24 +0300, Andrew wrote: > > 13.10.2010 23:42, davidMbrooke пишет: > > > So, if I understand correctly, I should: > > > 1. Amend source/modules/buildtool.cfg to create lib/firmware/ (in the > > > same way that it creates lib/modules/ today) > > > 2. Create a firmware.tgz along the same lines as modules.tgz, > > > containing ALL of the firmware (I can do that in buildimage.pl) > > > 3. Amend source/kmodules/common.cfg to include the e100 firmware > > > files in the initial moddb.lrp (and moddb_ipv6.lrp) alongside the > > > e100.ko file > > > > > > Let me know if I misunderstood your suggestion. > > > > > > I will give this a try on my development system when I get chance > > > (hopefully later this week). > > > > > > dMb > > Yes, you're right. > > Thanks Andrew. I have step #1 and #3 working in my development > environment and my original e100 problem has gone away. > Turns out there needs to be a step #4 since apkg has it hard-coded to > only process /lib/modules when re-generating moddb.lrp and it now needs > to include /lib/firmware too. > > dMb
Should all be fixed now. Updated files checked in to CVS. When using buildimage.pl there will be a new "firmware.tgz" alongside "modules.tgz" in the disk image. dMb ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
