Re: [leaf-devel] Bering-uClibc4: NIC Firmware Loading
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 leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering-uClibc4: NIC Firmware Loading
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 > > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > ___ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering-uClibc4: NIC Firmware Loading
13.10.2010 23:42, davidMbrooke пишет: > On Mon, 2010-10-11 at 23:26 +0300, Andrew wrote: >> 11.10.2010 22:58, e-mail dmb.leaf-devel пишет: >>> Hi Team, >>> >>> I am getting an error testing v4 with an e100 NIC: "Failed to load >>> firmware" and referencing file e100/d101s_ucode.bin >>> I understand that such files are normally located under /lib/firmware >>> and sure enough in buildtool/staging/ the files are there. >>> >>> I am considering creating a new package "firmware.lrp" so that these >>> can be loaded. Does that seem sensible or should they be included in >>> an existing .lrp? The total size of the lib/firmware/ directory is >>> about 500K though it may be smaller when compressed in a .lrp file. >>> >>> Thanks, >>> >>> davidMbrooke >> Hi. >> IMHO it'll be better to include firmware directory into modules.lrp; and >> place firmware separately in .tgz (or in modules.lrp for drivers that >> are included by default). But this is only my opinion. >> > Thanks for the feedback Andrew. Your understanding of the 2.6 kernel is > much better than mine so your opinion is valuable and I am happy to > follow your suggestion if others agree. > > I like the idea that if we include a NIC driver module as standard we > should also include any matching firmware as standard. > > The firmware files under $(BT_STAGING_DIR)/lib/firmware/ are: > - bnx2/*.fw for Broadcom GbE NIC > - e100/*.binfor Intel Pro/100 NIC > - edgeport/*for Digi Edgeport USB<-> RS-232 > - keyspan_pda/*.fw for some USB<-> RS-232 device? > - mts_*.fw for MTS EDGE/GSM/CDMA cellphone > - ti_*.fw for TI USB<-> RS-232 > - tigon/*.bin for Alteon Networks Tigon GbE NIC > - whiteheat*.fw for ConnectTech WhiteHEAT USB<-> RS-232 > > Of those I believe it is only the e100 driver that we include as > standard in the default moddb.lrp (at the moment). > > 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. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering-uClibc4: NIC Firmware Loading
On Mon, 2010-10-11 at 23:26 +0300, Andrew wrote: > 11.10.2010 22:58, e-mail dmb.leaf-devel пишет: > > Hi Team, > > > > I am getting an error testing v4 with an e100 NIC: "Failed to load > > firmware" and referencing file e100/d101s_ucode.bin > > I understand that such files are normally located under /lib/firmware > > and sure enough in buildtool/staging/ the files are there. > > > > I am considering creating a new package "firmware.lrp" so that these > > can be loaded. Does that seem sensible or should they be included in > > an existing .lrp? The total size of the lib/firmware/ directory is > > about 500K though it may be smaller when compressed in a .lrp file. > > > > Thanks, > > > > davidMbrooke > Hi. > IMHO it'll be better to include firmware directory into modules.lrp; and > place firmware separately in .tgz (or in modules.lrp for drivers that > are included by default). But this is only my opinion. > Thanks for the feedback Andrew. Your understanding of the 2.6 kernel is much better than mine so your opinion is valuable and I am happy to follow your suggestion if others agree. I like the idea that if we include a NIC driver module as standard we should also include any matching firmware as standard. The firmware files under $(BT_STAGING_DIR)/lib/firmware/ are: - bnx2/*.fw for Broadcom GbE NIC - e100/*.binfor Intel Pro/100 NIC - edgeport/*for Digi Edgeport USB <-> RS-232 - keyspan_pda/*.fw for some USB <-> RS-232 device? - mts_*.fw for MTS EDGE/GSM/CDMA cellphone - ti_*.fw for TI USB <-> RS-232 - tigon/*.bin for Alteon Networks Tigon GbE NIC - whiteheat*.fw for ConnectTech WhiteHEAT USB <-> RS-232 Of those I believe it is only the e100 driver that we include as standard in the default moddb.lrp (at the moment). 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 > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > ___ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering-uClibc4: NIC Firmware Loading
11.10.2010 22:58, e-mail dmb.leaf-devel пишет: > Hi Team, > > I am getting an error testing v4 with an e100 NIC: "Failed to load > firmware" and referencing file e100/d101s_ucode.bin > I understand that such files are normally located under /lib/firmware > and sure enough in buildtool/staging/ the files are there. > > I am considering creating a new package "firmware.lrp" so that these > can be loaded. Does that seem sensible or should they be included in > an existing .lrp? The total size of the lib/firmware/ directory is > about 500K though it may be smaller when compressed in a .lrp file. > > Thanks, > > davidMbrooke Hi. IMHO it'll be better to include firmware directory into modules.lrp; and place firmware separately in .tgz (or in modules.lrp for drivers that are included by default). But this is only my opinion. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Bering-uClibc4: NIC Firmware Loading
Hi Team, I am getting an error testing v4 with an e100 NIC: "Failed to load firmware" and referencing file e100/d101s_ucode.bin I understand that such files are normally located under /lib/firmware and sure enough in buildtool/staging/ the files are there. I am considering creating a new package "firmware.lrp" so that these can be loaded. Does that seem sensible or should they be included in an existing .lrp? The total size of the lib/firmware/ directory is about 500K though it may be smaller when compressed in a .lrp file. Thanks, davidMbrooke -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
