What is the correct way to make an mtdchar device available?

James Olin Oden james.oden at gmail.com
Wed Aug 8 16:16:50 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.
Yeah, I saw something about "physmap" in one web page.  The module was
not available on my system, but it looks like its in the source code,
which means RedHat did not have it configured to build.  I can work
with that.

> 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.
No its just a flash chip soldered on the board, that they call a
firmware hub, because the intent of the mother board manufacturer was
to place BIOS in it.

Thank you...james

> -R

More information about the linux-mtd mailing list