Re: [leaf-devel] b43 firmware
Am 18.02.2015 um 18:04 schrieb kp kirchdoerfer: Hi Erich; ... IMHO it should be unpacked if the driver module gets installed. So we need some dependency mechanism between modules and firmware. Keep in mind: a fully build firmware.tgz will be about 45MB. I don't build it that way, just what's required by users, but it could be that big or at least a lot bigger than the less than 1MB we have today. I am aware of that. Therefor I don't think we should unpack a package like that by default - it does waste RAM and it will raise startup time even for those who don't need or want firmware. And most users don't want every firmware files available unpacked. We will have to decide if we are building something for an end user or a developer. Right now LEAF is adressing enthusiasts which can manage moderatly complex tasks like selecting the right module set, e.t.c Given the enormous variability of our target hardware it is close to impossible to anticipate what module set and possibly firmware set a user needs. Maybe we will need a site where missing modules/firmware BLOBS can be installed from to make this more user friendly. The current situation is IMHO not really attractive to end users. In the past LEAF would be running on obsolete HW which has now mostly changed to be embedded systems (I believe). We are still building for the complex set of standard PC hardware without really knowing if this is the most common target. I am surprised by the extended set of hardware a project like openWRT supports, maybe this is due to the similarity of those platforms. Would you think we could build a set of relatively modest basic configurations which would allow to be upgraded by simply connecting to a web site and selecting additional functional modules? I have never used the preconfigured packets as I felt they were too big and contained too much cruft. It proves to be quite an effort though. Just look at the invariable serial console problem. I believe we have addressed the needs of the enthusiasts with our various packages and images. I also believe we should present something new for end users, trying to get where the commercial suppliers of embedded systems are but be more flexible. Consider a system on a USB stick, which would allow to taylor a LEAF image by selecting the necessary modules from a WEB interface, using either some kind of HW detection or user interaction if the hardware canot be booted from a USB stick. That would be quite a challenge. cheers ET smime.p7s Description: S/MIME Cryptographic Signature -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] b43 firmware
Hi KP Am 17.02.2015 um 20:48 schrieb kp kirchdoerfer: Hi; Am Montag, 16. Februar 2015, 00:06:15 schrieb Mega: Hi KP Am 15.02.2015 um 14:25 schrieb kp kirchdoerfer: Hi Erich; ... IMHO it should not unpacked, because it will shrink and clutter the RAM with almost unused stuff. I'd prefer a modification of hwdetect, which also scans /etc/modules to load modules that are not detected by scanning modules.dep to load just the firmware required. IMHO it should be unpacked if the driver module gets installed. So we need some dependency mechanism between modules and firmware. cheers ET smime.p7s Description: S/MIME Cryptographic Signature -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] b43 firmware
Hi Erich; Am Mittwoch, 18. Februar 2015, 12:14:45 schrieb Erich Titl: Hi KP Am 17.02.2015 um 20:48 schrieb kp kirchdoerfer: Hi; Am Montag, 16. Februar 2015, 00:06:15 schrieb Mega: Hi KP Am 15.02.2015 um 14:25 schrieb kp kirchdoerfer: Hi Erich; ... IMHO it should not unpacked, because it will shrink and clutter the RAM with almost unused stuff. I'd prefer a modification of hwdetect, which also scans /etc/modules to load modules that are not detected by scanning modules.dep to load just the firmware required. IMHO it should be unpacked if the driver module gets installed. So we need some dependency mechanism between modules and firmware. Keep in mind: a fully build firmware.tgz will be about 45MB. I don't build it that way, just what's required by users, but it could be that big or at least a lot bigger than the less than 1MB we have today. Therefor I don't think we should unpack a package like that by default - it does waste RAM and it will raise startup time even for those who don't need or want firmware. And most users don't want every firmware files available unpacked. A con to my idea ist that each time a user upgrades his router the firmware files in /lib/firmware are gone, because if they are saved in moddb.lrp, they'll be gone when moddb.lrp is upgraded along with the kernel. But this is also true for non-default modules - so part of upgrading is always running hwdetect - something similar for the firmware could do the job for a given firmware as well. It will be then saved to moddb.lrp as the modules added, and users will be fine until next upgrade. kp -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] b43 firmware
Hi KP Am 15.02.2015 um 14:25 schrieb kp kirchdoerfer: Hi Erich; I've just added a new package with linux-firmware from kernel.org to add support firmware support for the r8169 driver lshw shows: driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168e-2.fw Am Montag, 29. Dezember 2014, 16:41:30 schrieb Erich Titl: Hi folks I am playing with the b43 driver and it appears there is firmware needed to usre this card. This firmware is not included in the firmware.tgz tarball. I built b43-fwcutter and extracted the firmware from broadcom's binary distribution. root@leafbuilder:/home/mega/leaf/firmware/broadcom/fwdir# find b43 b43 b43/ucode16_sslpn.fw b43/sslpn2bsinitvals19.fw b43/lp0initvals13.fw b43/ucode15.fw . Now a few questions pop up 1) where is the firmware loaded at boot if it's placed in /lib/firmware it will be loaded during boot by mdev /lib/firmware is saved to moddb.lrp I booted, extracted rtl_nic from firmware.tgz and copied it to /lib/firmware, did a backup for modules and rebootedand got firmware support. I could not find any code in linuxrc to load firmware. Would it make sense to package it into a .lrp file? Where is firmware.tgz unpacked in the start up prodess. AFAIK it is not and therefore has to be unpacked manually. If this is the case I would call this a glitch. cheers ET -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] b43 firmware
Hi folks I am playing with the b43 driver and it appears there is firmware needed to usre this card. This firmware is not included in the firmware.tgz tarball. I built b43-fwcutter and extracted the firmware from broadcom's binary distribution. root@leafbuilder:/home/mega/leaf/firmware/broadcom/fwdir# find b43 b43 b43/ucode16_sslpn.fw b43/sslpn2bsinitvals19.fw b43/lp0initvals13.fw b43/ucode15.fw . Now a few questions pop up 1) where is the firmware loaded at boot I could not find any code in linuxrc to load firmware. Would it make sense to package it into a .lrp file? 2) What is the correct path to include this firmware in the firmware tarball The local path is b43, so I assume it could be either broadcom or broadcom/b43 cheers Erich smime.p7s Description: S/MIME Cryptographic Signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
