From: David Woodhouse <dwmw2@infradead.org>
To: Holly Gates <hgates@eink.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Smartmedia block mapping
Date: Tue, 22 Jul 2003 16:17:58 -0400 [thread overview]
Message-ID: <1058905076.32360.45.camel@lapdancer.baythorne.internal> (raw)
In-Reply-To: <3F1D98F4.8060904@eink.com>
On Tue, 2003-07-22 at 16:05, Holly Gates wrote:
> Maybe I could see using the mapping table if it was on the card
> somewhere,
It is. It's in the 'out of band' area of the data blocks I believe --
see the SmartMedia specs for details.
> but ideally I could just write the binary file to the sectors
> in true, physical, incrementing order. Anyone know of a utility I could
> use to do this?
You need special hardware which gives you access to the raw flash
without doing the translation _for_ you. Most 'card readers' will do it
for you and hence you don't get this option.
> I suppose I could build a parallel port adapter and write some software
> or something, but that is annoying since I know the computer is capable
> of doing what I want if I could get at the right layer of the driver
> stack...
No, it's not. Your USB card reader doesn't let you have access to the
raw flash; it has the translation built-in.
Either implement the full SMTL in your FPGA, or make sure you use
hardware which accesses the flash directly, when writing to the device.
--
dwmw2
next prev parent reply other threads:[~2003-07-22 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 20:05 Smartmedia block mapping Holly Gates
2003-07-22 20:17 ` David Woodhouse [this message]
2003-07-22 20:34 ` Holly Gates
2003-07-24 22:27 ` Charles Manning
2003-07-24 22:33 ` Matthew Dharm
2003-07-24 22:47 ` Charles Manning
2003-07-24 22:57 ` Matthew Dharm
2003-07-25 0:26 ` David Woodhouse
2003-07-22 21:11 ` Thomas Gleixner
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=1058905076.32360.45.camel@lapdancer.baythorne.internal \
--to=dwmw2@infradead.org \
--cc=hgates@eink.com \
--cc=linux-mtd@lists.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