From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: libATA PATA status report, new patch
Date: Fri, 10 Feb 2006 15:46:37 +0000 [thread overview]
Message-ID: <1139586397.12521.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20060210120157.GB28676@harddisk-recovery.com>
On Gwe, 2006-02-10 at 13:01 +0100, Erik Mouw wrote:
> Alan, can this related to LBA48 compatibility? I remember having
> problems with this when Andre Hedrick added LBA48 support around
> linux-2.4.19. The drive (Maxtor 4D040H2) advertised it supported LBA48,
> but the chipset (Ali 1543 rev C3, IIRC) didn't.
I don't think so. There is code to handle it. More likely the tuning
code is wrong and loaded incorrect values. We identify at PIO0 then
select modes.
Best way to test:
Boot with mwdma/udma set to zero in "info" block
then
Boot with only pio 0 claimed as supported and the mode setting logic
commented out.
That gives a good idea what broke.
next prev parent reply other threads:[~2006-02-10 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:46 libATA PATA status report, new patch Alan Cox
2006-02-06 20:04 ` Meelis Roos
2006-02-06 22:53 ` Alan Cox
2006-02-07 8:43 ` Meelis Roos
2006-02-07 11:05 ` Alan Cox
2006-02-07 11:10 ` Meelis Roos
2006-02-07 11:29 ` Ed Sweetman
2006-02-07 11:32 ` Meelis Roos
2006-02-07 11:38 ` Alan Cox
2006-02-07 15:04 ` Alan Cox
2006-02-07 17:02 ` Meelis Roos
2006-02-07 19:38 ` Duplicated SCSI messages (Was: Re: libATA PATA status report, new patch) Tomasz Kłoczko
2006-02-07 17:30 ` libATA PATA status report, new patch Meelis Roos
2006-02-07 17:50 ` Meelis Roos
2006-02-08 13:31 ` Alan Cox
2006-02-08 7:42 ` Meelis Roos
2006-02-08 18:28 ` Meelis Roos
2006-02-09 15:31 ` Alan Cox
2006-02-09 21:12 ` Meelis Roos
2006-02-10 12:01 ` Erik Mouw
2006-02-10 15:46 ` Alan Cox [this message]
2006-02-12 18:07 ` Kyle Moffett
2006-07-07 16:29 ` Wakko Warner
2006-07-07 16:52 ` 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=1139586397.12521.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.