All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: ian.nelson@echostar.com
Cc: "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: Proc stuff
Date: Thu, 05 Apr 2001 17:33:41 +0100	[thread overview]
Message-ID: <22237.986488421@redhat.com> (raw)
In-Reply-To: <3ACC986E.DE2F4C61@echostar.com>


ian.nelson@echostar.com said:
>  Maybe the solution is to create a /proc/mtd directory and then have a
> few different files in there which can either be generic or specific.
> There are other places in the kernel that do this so it's un
> unprecedented.  /proc is nice and easy to read so you can build
> scripts and simple things to read it. An ioctl could also work. 

/proc is nicer, if we really have to do it. How about /proc/driver/mtd/$n,
each one containing something along the lines of...

name: "blah"
size: 0x1000000
erasesize: 0x10000

The standard lines can be provided by a generic function, and we add a
proc_filler method to the mtd_info stucture which overrides that to allow
you to do whatever else you want.

Actually, mtdfs is probably nicer than adding yet more cruft to /proc. 

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-04-05 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 22:48 Proc stuff Ian S. Nelson
2001-04-05 12:47 ` David Woodhouse
2001-04-05 14:41   ` Johan Adolfsson
2001-04-05 14:50     ` David Woodhouse
2001-04-05 16:08   ` Ian S. Nelson
2001-04-05 16:33     ` David Woodhouse [this message]
2001-04-05 20:09       ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22237.986488421@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ian.nelson@echostar.com \
    --cc=mtd@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.