M5485EVB Running Linux 2.6.25, JFFS2 file system size

[jkimble]

I have been running with the old 2.6.10 kernel and file system in flash and that never created a file system larger than 24MB (16MB when I cleaned it up). I've worked through a lot of issues on the new 2.6.25 kernel and am ready to distribute it and I find that it's creating a JFFS2 file system that's 114MB!! Where's all that coming from?

I also just realized no compressed kernel like 2.6.10. I know I can work this out (hopefully find the space hogs in the file system) but this was one part of 2.6.10 that seemed to work pretty well. What happened? Am I missing something in the build that allows you to compress/optimize the file system for size? I've got 64MB of flash but I thought that was way overkill....

Any help/suggestions appreciated.

[raulen]

Have you disabled the kernel debug option?

[jkimble]

I just started over with LTIB. I had been doing a lot of development in (and out) of that kernel. With my changes the new one was only 11 MB. Not sure what got into the other one but I suspect even with the packages turned off LTIB doesn't do a great job of clean up.

I've another problem though. Everytime I try to boot up with the MTD support for my flash I get the message:

                                                    :

Driver 'sd' needs updating - please use bus_type methods
physmap platform flash device: 04000000 at fc000000
physmap-flash physmap-flash.0: Failed to ioremap flash region
physmap-flash: probe of physmap-flash.0 failed with error 5
sysfs: duplicate filename 'physmap-flash.0' can not be created
                                                     :

Not sure what the "Driver sd" means but the duplicate filename seems related to the fact that we have files in the sys file system that conflict with what's being created during device initialization. However I can't seem to find where these devices are being created.  My sys file contains the following flash devices:

-sh-2.05b# du -a | grep physmap
0       ./devices/platform/physmap_flash.0/uevent
0       ./devices/platform/physmap_flash.0/modalias
0       ./devices/platform/physmap_flash.0/subsystem
0       ./devices/platform/physmap_flash.0
0       ./devices/platform/physmap-flash.0/uevent
0       ./devices/platform/physmap-flash.0/modalias
0       ./devices/platform/physmap-flash.0/subsystem
0       ./devices/platform/physmap-flash.0
0       ./bus/platform/devices/physmap_flash.0
0       ./bus/platform/devices/physmap-flash.0
0       ./bus/platform/drivers/physmap-flash/uevent
0       ./bus/platform/drivers/physmap-flash/unbind
0       ./bus/platform/drivers/physmap-flash/bind
0       ./bus/platform/drivers/physmap-flash

 Any ideas?