public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Folkert van Heusden" <folkert@vanheusden.com>
To: "'John Bradford'" <john@grabjohn.com>
Cc: <szepe@pinerecords.com>, <linux-kernel@vger.kernel.org>
Subject: RE: reading from devices in RAW mode
Date: Sat, 18 Jan 2003 17:03:39 +0100	[thread overview]
Message-ID: <003501c2bf0b$2ae93ff0$3640a8c0@boemboem> (raw)
In-Reply-To: <200301181430.h0IEUK6D001055@darkstar.example.net>

> > Is it such a newby question? Your suggestion of using dd is totally NOT
> > what I meant: I want to read from devices with the devices ignoring
their
> > CRC-checks and such. Like what the CDROMREADRAW ioctl does for CD-ROMs.
> CD-ROMs, floppy disks, and hard disks work in completely different
> ways:
> All modern forms of storage use powerful error correction below the
> sector level.  Floppies are the exception here, they typically use MFM
> encoding, which is relatively straightforward.
> Audio Compact discs use powerful error correction anyway, but CD-ROMs
> use some of the capacity which was previously used for audio data for
> a second level of error correction, so there are two sector sizes,
> (RAW, and COOKED).  Reading RAW sectors, does not come close to
> allowing you to read individual pits and flats on the disc, it just
> lets you bypass the top level of error correction.  The data is still
> being error corrected by lower layers.

oh, ok. But I will still get more data back then with reading through
the regular, say, /dev/hdc-device wouldn't I? As far as I know, read
will only give you data when no I/O error occured.

> There is no floppy or hard disk equivillent to reading raw sectors
> from CD-ROMs.

Really? Are you really sure about that?

Back in the old days, when I did assembly on my Atari ST, I would just
say to the controller "gimme this and that track, in RAW" and it
would do so. I thought that I could do that at least for floppy, not
sure about harddisk (RLL through ACSI interface).


  reply	other threads:[~2003-01-18 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030118132315.GF19381@louise.pinerecords.com>
2003-01-18 14:00 ` reading from devices in RAW mode Folkert van Heusden
2003-01-18 14:30   ` John Bradford
2003-01-18 16:03     ` Folkert van Heusden [this message]
2003-01-18 16:15       ` John Bradford
2003-01-18 17:09         ` Folkert van Heusden
2003-01-18 17:33           ` John Bradford
2003-01-19 21:03 Arnaud Boulan
     [not found] <1042896128.1157.4.camel@RobsPC.RobertWilkens.com>
2003-01-18 13:58 ` Folkert van Heusden
  -- strict thread matches above, loose matches on Subject: below --
2003-01-18 13:16 Folkert van Heusden
2003-01-18 18:50 ` Andrew Morton

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='003501c2bf0b$2ae93ff0$3640a8c0@boemboem' \
    --to=folkert@vanheusden.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.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