changing mtd sizes

[johnbock]

Where are the mtd device properties? I haven't found them in the kernel...

 

[RalfFriedl]

They are defined in the ADAM2 bootloader environment.

But I don't know whether it is a good idea to change them.

 

[johnbock]

Combing the 512kB left over from my current config and the 256kB from tffs would be a substantial amount of flash memory for jffs2 and mini_fo, unionfs or aufs at boot

 

[abraXxl]

hi !

Combing the 512kB left over from my current config and the 256kB from tffs would be a substantial amount of flash memory for jffs2 and mini_fo, unionfs or aufs at boot

That is not a good idea. The AVM binary only tools rely heavily on the tffs device files, so erasing tffs or setting its partition size to 0 is no a good idee. Despite the partitions are created nevertheless in the kernel flash map in the default kernel.

I tried on my USB Root to minimize flash usage, and substituted the character devices in /var/flash with normal files with the same name.
ctlmgr, telefon, voipd, dsld, multi, ar7cfgctl, wlanctl all these tools are rely on the fact that these files are char devs. If one file needed is not a char dev, the tool deletes it and makes a char dev with the same name. afterwards it writes default settings to the create tffs device file.



cya

 

[johnbock]

all these tools are rely on the fact that these files are char devs.

Do you know if the require any char device or specifically tffs?

If any char device is required one could create a char device that binds to a specified file; like the old raw devices did...

 

[RalfFriedl]

I think they are always deleted and then created, or it may depend on the program using the file.