From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Thayne Harbaugh <tharbaugh@lnxi.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: device info in /proc/mtd
Date: Mon, 21 Apr 2003 13:44:14 +0200 [thread overview]
Message-ID: <20030421114414.GA9550@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1050513945.1172.265.camel@tubarao>
On Wed, 16 April 2003 11:25:45 -0600, Thayne Harbaugh wrote:
>
> It's nice that loading the amd76xrom module outputs probe information
> about a device manufacturer and chip:
>
> [root@172 2466]# modprobe amd76xrom
> Found: PMC Pm49FL004
> number of JEDEC chips: 1
> amd76xrom chip at offset: 480000
>
> I hoped this same information would be in /proc/mtd - it's not.
>
> [root@172 2466]# cat /proc/mtd
> dev: size erasesize name
> mtd0: 00080000 00001000 "AMD76X rom"
>
> Is there someplace where the manufacturer and chip are available other
> than in the printk() messages? It would be nice to be able to query
> this information at any time - a specific model of motherboard might
> socket a different chip depending on cost/availability and I'd like to
> be able to track which BIOS flash chip is being used.
>
> Something like this in /proc/mtd might be nice:
>
> dev: size erasesize name manufacturer chip chip_name
> mtd0: 00080000 00001000 "AMD76X rom" 009d 006e "PMC Pm49FL004"
>
> Am I crazey? Is this plain wrong? Does anyone have objections if I
> submit a patch?
You are not crazy, but I consider this to be the wrong spot for the
information. /proc/mtd should hold those informations that mtd core
code knows about. Device specifics should go somewhere else.
Or could you find a nice common interface for mtdblock (which hard
drive?), mtdram (physical ram addresses), mtdram2 (dynamic allocation,
print the whole list?), NAND (no idea), NOR (manufacturer, chip),
really odd stuff like NOR with hardware ECC and all the nice goodies
that are yet to appear?
Put it into /proc/<find a nice name>, make it as general as possible,
but not more.
Jörn
--
Eighty percent of success is showing up.
-- Woody Allen
prev parent reply other threads:[~2003-04-21 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 17:25 device info in /proc/mtd Thayne Harbaugh
2003-04-17 12:34 ` John Burch
2003-04-17 13:05 ` Holger Schurig
2003-04-21 11:44 ` Jörn Engel [this message]
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=20030421114414.GA9550@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=tharbaugh@lnxi.com \
/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