Stefan Monnier wrote:
> Interesting. So that would mean that as long as I don't actually use
> a jffs partition, I can just strip off the last 4kB excess?
I guess so (the startup scripts may need some mangling too as they'll be
expecting a jffs filesystem there by default IIRC), but if you don'
>> Ping? Doesn't someone have some idea of where that might come from?
> I'm not familiar with .trx in particular, but at least for AR7 squashfs
> images there is a 4-byte jffs marker at the very end that is
> deliberately aligned to the start of the next erase block after the end
> of the real f
Stefan Monnier wrote:
> Ping? Doesn't someone have some idea of where that might come from?
I'm not familiar with .trx in particular, but at least for AR7 squashfs
images there is a 4-byte jffs marker at the very end that is
deliberately aligned to the start of the next erase block after the end
Ping? Doesn't someone have some idea of where that might come from?
Stefan
> "Stefan" == Stefan Monnier writes:
> Why is it that my .trx files (which I build for my WL-700gE, a brcm47xx
> target) always have a size of the form N*65536+4096.
> So, for example, I can have a firmwar
The patch below tweaks the broadcom-diag module so as to complement
/proc/diag/led with a /proc/diag/button subdirectory which shows the
current status of the various buttons.
The same information can already be obtained via `gpioctl' (which
requires the `gpio_dev' kernel module), except that gpio
