From: David Woodhouse <dwmw2@infradead.org>
To: Ricky Beam <jfbeam@bluetopia.net>
Cc: Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: MTD and Adapter ROMs
Date: Fri, 07 Sep 2001 15:14:08 +0100 [thread overview]
Message-ID: <18492.999872048@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0109070954400.1190-100000@sweetums.bluetronic.net>
In-Reply-To: <Pine.GSO.4.33.0109070954400.1190-100000@sweetums.bluetronic.net>
jfbeam@bluetopia.net said:
> Well, just having documentation on how all the spooge in drivers/mtd
> actually goes together would go along way to helping people use it.
Bah. That takes all the fun out of it.
> The flash chip is an SST 39SF010. It will appear somewhere in PCI
> memory space once I reenable the adapter ROM. It is a JEDEC compilant
> device. I have some code from SST for programming it, but I'd rather
> go the general route instead of the one-shot flash-and-run module.
> I think it'll be as "simple" as adding the ID to jedec.c. Load chips/
> *, maps/hpt-rom (doctored physmap to enable the rom and use it's
> location), and then see if I can get mtdchar to drive the mess.
Basically right. Once your map driver has successfully probed the chip and
registered the MTD device, you should be able to open /dev/mtd0 and read,
write and ioctl(MEMERASE) it. Not necessarily in that order.
--
dwmw2
next prev parent reply other threads:[~2001-09-07 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 3:19 MTD and Adapter ROMs Ricky Beam
2001-09-07 10:13 ` David Woodhouse
2001-09-07 14:04 ` Ricky Beam
2001-09-07 14:14 ` David Woodhouse [this message]
2001-09-07 15:37 ` Ricky Beam
2001-09-07 15:43 ` David Woodhouse
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=18492.999872048@redhat.com \
--to=dwmw2@infradead.org \
--cc=jfbeam@bluetopia.net \
--cc=linux-kernel@vger.kernel.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