On 2014-03-16 03:18, Bruce Dubbs wrote: > I checked out your procedure and it works quite well. The problem is > that the directory after using make install is 67M for the entire tree. > My entire /lib directory is only 20M.
Yeah, I am struggling with the same problem. Even if diskspace is less of a problem as it was 25 years go, I would still like to keep things as small as possible. > I don't know that users would want the whole tree. At least I wouldn't. > How does a user know what firmware is needed? If we could do that, we > could just mirror the tree, updated daily, and let users download from > there. > > The only way I would think that the user would know what is needed is to > start with the entire tree in /lib/firmware and check dmesg to see what > it wants and then delete the rest. I would think there is a better way. I had following idea (still to be implemented/tested), in chapter 8.3.1 the LFS user more or less chooses his kernel config and the required stuff is build. By using modinfo -F firmware <module> it is possible to list the firmware files. So using a script that tests all modules should be produce a list of blobs that matches. Then copy only those instead of running make install. > One note is that I am suprised that there are copies of firmware in the > main directory and not in vendor specific subdirectories. My guess is that most modules have not been modified/adjusted. Olaf -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
