From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: Early ATA devices
Date: Wed, 01 Aug 2007 15:02:36 +0900 [thread overview]
Message-ID: <46B021FC.20507@gmail.com> (raw)
In-Reply-To: <20070801014137.4ab39e94@the-village.bc.nu>
Alan Cox wrote:
> So I've been doing a scan of the code versus the early ATA specifications
> (English translation not the original Latin ;))
>
> I've found a couple of problem cases we don't deal with but I'm not sure
> matter, and an inconsistency
>
> #1 We assume identify works. Early ATA actually lists this command
> as optional
> #2 We don't allow for INIT_DEV_PARAMS failing which it may do on
> some early IDE pre ATA devices
>
> and the inconsistency
>
> We check ATA < 4 || non-LBA capable when deciding whether to issue
> INIT_DEV_PARAMS. ATA 4+ however mandate LBA so the second case isn't
> theoretically at least possible.
>
> Aside from those cases the command issue (but not the detection paths)
> appear to be clean for everything from ST412 upwards providing a drive is
> being used in 16 head mode and does its own write precompensation
> selection.
>
> So in theory we can persuade libata to drive original MFM/RLL disks with
> relatively few changes
Does anyone have a working device to test?
--
tejun
next prev parent reply other threads:[~2007-08-01 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 0:41 Early ATA devices Alan Cox
2007-08-01 6:02 ` Tejun Heo [this message]
2007-08-02 20:47 ` Alan Cox
2007-08-15 17:19 ` Erik Mouw
2007-08-15 17:48 ` Alan Cox
2007-08-01 13:47 ` Jeff Garzik
2007-08-01 15:31 ` Alan Cox
2007-08-01 18:06 ` Alan Cox
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=46B021FC.20507@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).