From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: sddr09.c
Date: Mon, 8 Apr 2002 23:10:43 GMT [thread overview]
Message-ID: <UTC200204082310.XAA559533.aeb@cwi.nl> (raw)
This evening I cleaned up sddr09.c, and after some playing
succeeded in writing to a SM card.
Remains the question: does anyone have docs for this thing?
(The "read control" command gives 64 bytes for each 16kB block.
The last 48 look like junk. The first 16 either are all zero,
or start with six FF bytes followed by two groups of five bytes.
The first two bytes of both groups of five are equal, and
describe the PBA <-> LBA correspondence.
I do not know what the final three bytes of both groups mean.
They have five nybbles of even parity and one nybble that ends
in two 1 bits.
What is the purpose of this PBA <-> LBA mapping?
To avoid bad blocks? Or is rewriting a sector much slower
than relocating it and writing a fresh one?
I invented a "write_data" command, but have not yet tried
to do a "write_control".)
Andries
next reply other threads:[~2002-04-08 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 23:10 Andries.Brouwer [this message]
2002-04-08 23:30 ` sddr09.c Matthew Dharm
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=UTC200204082310.XAA559533.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®