public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Johan Adolfsson" <johan.adolfsson@axis.com>
To: "David Woodhouse" <dwmw2@infradead.org>, <ian.nelson@echostar.com>
Cc: <mtd@infradead.org>
Subject: Re: Proc stuff
Date: Thu, 5 Apr 2001 16:41:50 +0200	[thread overview]
Message-ID: <175f01c0bdde$8cb38ae0$0a070d0a@axis.se> (raw)
In-Reply-To: 27773.986474836@redhat.com

I guess we would like that kind of information available somewhere
as well. Either through /proc or through an ioctl().

We (Axis) have an ioctl() to get that info with our own flash driver
and JFFS available on developer.axis.com (not using mtd).
It is typically used to verify that a certain type of chip is mounted
during production test where boot messages are not even enabled
and not a nice way to get the information for that purpose anyway.

Since mtd is not flash specific, perhaps a generic info string
about the device media could be added?

/Johan


----- Original Message -----
From: David Woodhouse <dwmw2@infradead.org>
To: <ian.nelson@echostar.com>
Cc: <mtd@infradead.org>
Sent: Thursday, April 05, 2001 14:47
Subject: Re: Proc stuff


>
> ian.nelson@echostar.com said:
> > I need some extra bits added to the proc/mtd.  For the product I'm
> > building we want to have things from the flash registers like the
> > Device ID and "AMD flash"
>
> Those aren't particularly generic bits of information - why do you think
> they should be present at that level? That kind of detail is reported in
the
> boot messages, not in /proc/mtd. Does your eth0 device provide a way to
find
> out which chipset it is?
>
> Perhaps we could make the CFI drivers put slightly more informative
> information in the 'name' field, but that doesn't work nicely if you have
> partitions which override the original name.
>
> --
> dwmw2
>
>
>
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
>



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

  reply	other threads:[~2001-04-05 14:45 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 [this message]
2001-04-05 14:50     ` David Woodhouse
2001-04-05 16:08   ` Ian S. Nelson
2001-04-05 16:33     ` David Woodhouse
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='175f01c0bdde$8cb38ae0$0a070d0a@axis.se' \
    --to=johan.adolfsson@axis.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox