how to access jffs2 partition properties?

how to access jffs2 partition properties?

[Robert P. J. Day]

  on a PPC system using a 2.4.22 kernel, is there a way to access the
properties for the jffs2 filesystems that have been defined on the two
flash chips this system has?

  it's easy enough to see the devices /dev/mtdblock/[0-4] that
represent the partitions, and the file /proc/partitions contains:

  31     0         64 mtdblocka
  31     1        384 mtdblockb
  31     2        128 mtdblockc
  31     3       3072 mtdblockd
  31     4      29184 mtdblocke

but can i examine, for each of these, its chip, starting address,
ending address, etc?  thanks.

rday

Re: how to access jffs2 partition properties?

[Jörn Engel]

On Sat, 12 March 2005 12:20:27 -0500, Robert P. J. Day wrote:
> 
>   on a PPC system using a 2.4.22 kernel, is there a way to access the
> properties for the jffs2 filesystems that have been defined on the two
> flash chips this system has?
> 
>   it's easy enough to see the devices /dev/mtdblock/[0-4] that
> represent the partitions, and the file /proc/partitions contains:
> 
>   31     0         64 mtdblocka
>   31     1        384 mtdblockb
>   31     2        128 mtdblockc
>   31     3       3072 mtdblockd
>   31     4      29184 mtdblocke
> 
> but can i examine, for each of these, its chip, starting address,
> ending address, etc?  thanks.

Not all mtd are flash based.  Mtd code should have zero knowledge
about chip, start address, etc.  If you need that information, you
have to tweak the mapping driver to give it out.

Jörn

-- 
Premature optimization is the root of all evil.
-- Donald Knuth

Re: how to access jffs2 partition properties?

[Jörn Engel]

On Mon, 14 March 2005 15:15:09 +0100, Jörn Engel wrote:
> 
> Not all mtd are flash based.  Mtd code should have zero knowledge
                                      ^
mtd core, i meant.

> about chip, start address, etc.  If you need that information, you
> have to tweak the mapping driver to give it out.

Jörn

-- 
Invincibility is in oneself, vulnerability is in the opponent.
-- Sun Tzu

Re: how to access jffs2 partition properties?

[Artem B. Bityuckiy]

> Not all mtd are flash based.  Mtd code should have zero knowledge
> about chip, start address, etc.  If you need that information, you
> have to tweak the mapping driver to give it out.
> 
> Jörn

May be /proc/mtd is what you are looking for ?

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

Re: how to access jffs2 partition properties?

[Jörn Engel]

On Mon, 14 March 2005 17:41:28 +0300, Artem B. Bityuckiy wrote:
> 
> >Not all mtd are flash based.  Mtd code should have zero knowledge
> >about chip, start address, etc.  If you need that information, you
> >have to tweak the mapping driver to give it out.
> 
> May be /proc/mtd is what you are looking for ?

Nope.  mphysmap (the old version from several years ago) created its
own proc file.  That one, in combination with /proc/mtd would contain
the necessary information.

New mphysmap is missing the proc file.  And the person that requested
the driver has been silent for a while, so I have no idea if it even
works.  Lack of hardware.

Jörn

-- 
When in doubt, use brute force.
-- Ken Thompson

Re: how to access jffs2 partition properties?

[Josh Boyer]

On Mon, 2005-03-14 at 15:59 +0100, Jörn Engel wrote:
> 
> New mphysmap is missing the proc file.  And the person that requested
> the driver has been silent for a while, so I have no idea if it even
> works.  Lack of hardware.

Who was that?  Me?  I haven't had a chance to look at it yet, but it
looked nicer than the one I'm currently using anyway.  I'll try to get
to it eventually.

josh

Re: how to access jffs2 partition properties?

[Jörn Engel]

On Mon, 14 March 2005 09:33:52 -0600, Josh Boyer wrote:
> On Mon, 2005-03-14 at 15:59 +0100, Jörn Engel wrote:
> > 
> > New mphysmap is missing the proc file.  And the person that requested
> > the driver has been silent for a while, so I have no idea if it even
> > works.  Lack of hardware.
> 
> Who was that?  Me?  I haven't had a chance to look at it yet, but it
> looked nicer than the one I'm currently using anyway.  I'll try to get
> to it eventually.

No, it was some private mail from about a month ago.

Jörn

-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
-- Brian W. Kernighan