linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.10-rc2+] ide1=ata66 -- OBSOLETE OPTION, WILL BE REMOVED SOON!
Date: Thu, 16 Dec 2004 15:29:19 +0100	[thread overview]
Message-ID: <58cb370e04121606295fe384fc@mail.gmail.com> (raw)
In-Reply-To: <1103154772.3585.24.camel@localhost.localdomain>

On Wed, 15 Dec 2004 23:52:52 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Llu, 2004-12-13 at 21:47, Bartlomiej Zolnierkiewicz wrote:
> > > I do need a way to force an 80c cable on this AMD756 (ATA66 max) board,
> > > since the BIOS doesn't seem to be setting the cable bits correctly.
> >
> > Ugh, I checked AMD datasheets and AMD756 doesn't support host
> > side cable detection.  Well, we can try doing disk side only for it.
> > [ ATi and ITE (in -ac kernels) drivers are also doing this. ]
> 
> That is probably a good change but not sufficient for things like
> bladeservers where some vendors use short 40c cables which are within
> specification but break drive side detection. Removing ata66 forcing
> doesn't work because of these although perhaps it could be done using
> subvendor ids so it is automatic ?

Yes, one of the aims of deprecating ata66 override was to see what can
be done automatically.  The fewer special kernel parameters the better
(w/o sacrificing functionality of course).

> Right now I plan to keep ata66 overrides in -ac.

Fine but I'm not going to remove them soon (warning is a bit strong
to help us gain more knowledge :), however it would be nice if somebody
could move them from IDE core to specific host drivers.

Bartlomiej

  reply	other threads:[~2004-12-16 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-05 19:23 [2.6.10-rc2+] ide1=ata66 -- OBSOLETE OPTION, WILL BE REMOVED SOON! Rene Herman
2004-12-13 21:47 ` Bartlomiej Zolnierkiewicz
2004-12-14  6:51   ` Andre Hedrick
2004-12-14 16:15   ` Rene Herman
2004-12-15 23:52   ` Alan Cox
2004-12-16 14:29     ` Bartlomiej Zolnierkiewicz [this message]
2004-12-16 14:32       ` Bartlomiej Zolnierkiewicz

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=58cb370e04121606295fe384fc@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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).