From: Andries Brouwer <aebr@win.tue.nl>
To: Jonathan Corbet <corbet@lwn.net>
Cc: gen-lists@blueyonder.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Problems accessing USB Mass Storage
Date: Wed, 18 Sep 2002 11:22:54 +0200 [thread overview]
Message-ID: <20020918092254.GA14568@win.tue.nl> (raw)
In-Reply-To: <20020917181513.9217.qmail@eklektix.com>
On Tue, Sep 17, 2002 at 12:15:13PM -0600, Jonathan Corbet wrote:
> SmartMedia cards are weird in that they have a (seemingly) random amount of
> waste space at the beginning of the card. Your 8MB card, in particular,
> has nothing of interest in the first 25 sectors. Some cards have a
> reasonable partition table in the first sector, and some don't. Modern
> Windows systems (and cameras, of course) seem to be able to access the
> filesystem on the card without needing to see a partition table.
>
> A little while I posted a Lexar SmartMedia driver patch which hacked around
> this by substituting a fake partition table when the first sector was read.
The structure of SmartMedia cards is well-known and precisely documented.
See, e.g., http://www.win.tue.nl/~aeb/linux/smartmedia/SmartMedia_Format.pdf
What varies is how readers present this to the outside world.
The card starts with the CIS, followed by a remapping table that tells
where on the card a given user sector lives. There are also sector checksums
and information about bad sectors.
Some readers have this as built-in knowledge, and present to card to
the outside world as an ordinary block device.
Some readers give direct access to the bits on the card, and then
understanding this remapping business is a job for the driver.
If you see non-understood space at the beginning of the card,
then one might suspect that your reader is of the latter kind.
The partition table will be on the card, but not on sector zero.
Andries
next prev parent reply other threads:[~2002-09-18 9:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 18:15 Problems accessing USB Mass Storage Jonathan Corbet
2002-09-17 18:22 ` Randy.Dunlap
2002-09-17 19:46 ` Mark C
2002-09-17 20:12 ` jbradford
2002-09-17 21:21 ` Jonathan Corbet
2002-09-17 19:50 ` Thomas Dodd
2002-09-17 19:58 ` Matthew Dharm
2002-09-17 20:13 ` Thomas Dodd
2002-09-17 21:13 ` [Linux-usb-users] " Mark C
2002-09-17 21:40 ` Thomas Dodd
2002-09-17 21:51 ` Mark C
2002-09-17 21:58 ` Rogier Wolff
2002-09-17 22:17 ` Thomas Dodd
2002-09-17 22:23 ` Randy.Dunlap
2002-09-18 9:28 ` Andries Brouwer
2002-09-18 9:22 ` Andries Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 11:25 Mark C
2002-09-17 15:18 ` Greg KH
2002-09-17 17:37 ` Thomas Dodd
2002-09-17 17:46 ` Greg KH
2002-09-17 18:06 ` Richard B. Johnson
2002-09-17 20:09 ` Thomas Dodd
2002-09-17 21:01 ` Mark C
2002-09-17 21:43 ` Rogier Wolff
2002-09-17 22:04 ` Thomas Dodd
2002-09-17 22:21 ` Patrick Mansfield
2002-09-17 22:51 ` Mark C
[not found] ` <mailman.1032306001.9987.linux-kernel2news@redhat.com>
2002-09-18 1:37 ` Pete Zaitcev
2002-09-18 6:01 ` Rogier Wolff
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=20020918092254.GA14568@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=corbet@lwn.net \
--cc=gen-lists@blueyonder.co.uk \
--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