From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata ATA vs SATA detection and workaround.
Date: Mon, 30 Aug 2004 20:34:43 +0400 [thread overview]
Message-ID: <41335723.40907@wasp.net.au> (raw)
In-Reply-To: <413350A2.1000003@pobox.com>
> I'm still pondering what Alan was hinting at, a bit. You (Brad) are
> correct in pointing out that this code should only trigger for the
> correct situations (lba48, etc.) which are only present on modern
> drives, but... there is still a chance that word 93 will be zero on
> some weird (probably non-compliant) device.
I agree completely, though my feeling is that if someone plugs a device that broken into a SATA
controller via a bridge then there "aint nuffin we can do about it" anyway and if it breaks it
breaks. I guess we could offer the option you suggested before where we load the individual drivers
as modules and provide a "knobble" module parm that will limit max_sectors to 200 and udma_mask to
udma/100.
Then we get the hassle if someone wants to use it as the root device, but I guess then you move to
an initrd and load the module from there.
How far do we want to take it?
Regards,
Brad
next prev parent reply other threads:[~2004-08-30 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 17:09 libata dev_config call order wrong Brad Campbell
2004-08-29 17:29 ` Jeff Garzik
2004-08-29 17:47 ` Brad Campbell
2004-08-29 17:59 ` Jeff Garzik
2004-08-29 18:25 ` Jeff Garzik
2004-08-29 18:59 ` Alan Cox
2004-08-30 9:12 ` Brad Campbell
2004-08-30 13:22 ` Alan Cox
2004-08-30 14:38 ` Brad Campbell
2004-08-30 14:42 ` [PATCH] libata ATA vs SATA detection and workaround Brad Campbell
2004-08-30 14:57 ` Brad Campbell
2004-08-30 14:57 ` Brad Campbell
2004-08-30 16:06 ` Jeff Garzik
2004-08-30 16:34 ` Brad Campbell [this message]
2004-08-30 16:37 ` Jeff Garzik
2004-08-30 17:17 ` Brad Campbell
2004-08-30 17:59 ` Jeff Garzik
2004-08-31 7:47 ` Brad Campbell
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=41335723.40907@wasp.net.au \
--to=brad@wasp.net.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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 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.