linux-ide.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: Mikael Pettersson <mikpe@it.uu.se>, linux-ide@vger.kernel.org
Subject: Re: 2.6.23-rc1: pata_via cable detection differs from via82cxxx
Date: Sat, 4 Aug 2007 01:12:01 +0200	[thread overview]
Message-ID: <200708040112.01486.bzolnier@gmail.com> (raw)
In-Reply-To: <20070803233217.54c82022@the-village.bc.nu>

On Saturday 04 August 2007, Alan Cox wrote:
> On Fri, 3 Aug 2007 20:28:39 +0200 (MEST)
> Mikael Pettersson <mikpe@it.uu.se> wrote:
> 
> > The machine is an Athlon64 laptop with a K8T800 chipset. With the IDE
> > VIA driver the disk is detected as udma/100:
> 
> Currently old IDE via driver has a hack in it which goes 'did the BIOS
> set UDMA3+' then I guess the cable is 80 wire regardless. libata doesn't
> do that as it breaks with hotplug, breaks with suspend/resume before the
> driver is loaded and other bits.
> 
> Instead we have two things - an ACPI snoop and a table of wonky laptops
> (eg those that use 40 wire ultrashort cables which are valid for UDMA133
> but not detected as 80 wire). If your laptop is done that way then it
> just needs adding to the magic list and/or 2.6.23-rc1-mm should spot it
> by ACPI. I'd prefer the table entry anyway as I don't like relying on ACPI
> so an lspci -vvxx would be appreciated

Please also add it to the laptop table in IDE VIA driver.

Thanks,
Bart

  reply	other threads:[~2007-08-03 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 18:28 2.6.23-rc1: pata_via cable detection differs from via82cxxx Mikael Pettersson
2007-08-03 22:32 ` Alan Cox
2007-08-03 23:12   ` Bartlomiej Zolnierkiewicz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-04 10:59 Mikael Pettersson

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=200708040112.01486.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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).