[patch/rfc 2.6.29 1/2] MTD: driver model updates
david-b at pacbell.net
Tue Mar 31 23:21:25 EDT 2009
On Tuesday 31 March 2009, Kevin Cernekee wrote:
> On Tue, Mar 31, 2009 at 2:18 PM, David Brownell <david-b at pacbell.net> wrote:
> > Hmm, no comments? I had understood there was interest over on
> > the MTD side of things in exposing more information through
> > sysfs, to help avoid the need to add Even More Ioctls as part
> > of support for things like NAND chips with 4KB pages, or which
> > handle more than 4GBytes ...
> Based on this post:
> I am inferring that the following attributes are wanted in the MTD
> sysfs interface:
> 1) mtd_info_user fields - type, flags, size, erasesize, writesize,
> oobsize. So far we have "type," but it should be easy to add the
Yes, easy to add those. As noted in the $SUBJECT patch, the set
consisting of just "type" is a "starter set". :)
For procfs elimination, a name/label would be needed too; that can
be an input to, or output from, cmdlinepart.
My question about the $SUBJECT patch is whether there's any reason
not to use that as the start of such driver model enhancements.
I'm thinking the answer to that seems to be "no", and that someone
more involved in *using* those sysfs attributes would be a better
choice for growing that set of attributes.
> 2) region_info_user fields? Not really sure how this would work.
> Maybe a separate subdirectory for each region?
I'm not sure I've ever had reason to care about a "region" (whatever
that is!) with MTD hardware.
I suspect that a lot of interesting questions could come up in
the context of enhancing mtd-utils to work with sysfs and bigger
NAND chips. Some might relate to "regions".
More information about the linux-mtd