On Tuesday 16 June 2009 11:55:59 Ferenc Wagner wrote: > Thanks, that's good to know! Don't you feel like putting this into > the Wiki and linking it from the WAP54g page from WiP? :)
Ah well. The WAP is officially not supported. But there's not that much to write about it anyway. Just disable anything that's not required. ;) > Thanks for reminding me of BusyBox. The menuconfig interface hides > that submenu, like, completely! Yeah, read those options carefully. There are also a few options that need to be enabled to safe space (space-time-tradeoff options) > > The second step is to search for big flash consumers. It turns out > > the crypto modules do consume a large amount of flash. Even if the > > functionality is already compiled into the kernel image itself. > > Which of them are really needed, btw? This only applies to 2.6 kernel. The crypto modules needed by mac80211 are only required. I compiled them into the image. That saves some space. In general, compile as much as possible into the kernel and avoid modules. > > Attached is a patch which strips down several hundred kiB of flash > > space. I think it doesn't apply anymore to current trunk, but you > > might get the idea. > > Yes, I was experimenting with things like this. But there's some > more to do, as it seems. Yeah this stuff was changed recently. There might be more. > > Another rather big flash consumer is the b43 driver firmware. > > There's an option in openwrt config to include only the necessary > > firmware files. Use it. > > Yes, that's pretty important. I've found it already. And did you try > optimising your kernel for size (CONFIG_CC_OPTIMIZE_FOR_SIZE)? Yeah sure. > > I'm not sure if this is any useful for you running a 2.4 image, but > > I just wanted to drop it into the discussion. Have fun! > > No, I'm running 2.6, so this was immensely useful. Thank you very > much! A question, though: after you managed to get your 5th erase > block and had a working jff2, did you actually use it for anything > else than setting up a couple of variables, like eg. operating mode > and IP addresses? Just for the net config. There's really no service running on the device (not even syslogd, klogd, etc...), so there's really nothing else to config. ;) > Because if not, then I think a startup/shutdown script pair, which > translated between nvram variables and /etc/config, could work just as > well, without requiring us to squeeze things this bad. Yes sure. -- Greetings, Michael. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
