What is the correct way to make an mtdchar device available?
James Olin Oden
james.oden at gmail.com
Thu Aug 9 15:03:12 EDT 2007
On 8/8/07, Ralph Siemsen <ralphs at netwinder.org> wrote:
> On Wed, Aug 08, 2007 at 01:50:29PM -0400, James Olin Oden wrote:
> > I have a system with the ST Micro M50FW080 firmware hub. I have
> > checked the source code and the jedec_probe module has detection code
> > for that driver. So I've done:
> I'm not familiar with this device, but you appear to be missing a
> mapping driver (see drivers/mtd/maps, the most common being "physmap").
> You'll likely need to know the physical address and size of your flash
> device. Once addresses are known, then the xyz_probe routines will be
> called to identify the device supposedly there.
Is there any documentation anywhere that talks about the mapping
driver, their uses and requriements?
I started looking into this and the config involves answering things
like "physical start address of flash mapping". I guess that would
be the start adress of where the FWH maps itself into memory, but
since there are two on the system setting this does not seem
Also, is there anything that explains what one might need to do in the
context of simply making a flash chip available for reading and
writing through mtdchar mtdblock?
> I could be way off base, maybe the "firmware hub" works more magically.
> My description is more for flash that is soldered on the board.
More information about the linux-mtd