Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Grozdan <neutrino8@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Wed, 3 Jun 2009 13:14:07 +0100	[thread overview]
Message-ID: <20090603131407.57c490ed@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <c5bd819b0906030435w466368cbsd48be91a97597437@mail.gmail.com>

> ACPI: PCI Interrupt Link [ALKA] disabled and referenced, BIOS bug
> ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
> pata_via 0000:00:0f.0: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
> scsi0 : pata_via
> scsi1 : pata_via
> ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14
> ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15
> ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
> ata1.00: 160086528 sectors, multi 16: LBA
> ata1.01: ATA-5: ST340016A, 3.10, max UDMA/100
> ata1.01: 78165360 sectors, multi 16: LBA
> ata1.00: limited to UDMA/33 due to 40-wire cable
> ata1.01: limited to UDMA/33 due to 40-wire cable

The via driver hasn't changed its cable detect handling between 2.6.27
and now. The actual detection is done by the BIOS either by setting flags
or via ACPI.

To trace it down I'd need to at minimum to know exactly which kernel the
behaviour you see changed.

  reply	other threads:[~2009-06-03 12:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c5bd819b0906021525l13ee9282j1fb270e141985f66@mail.gmail.com>
2009-06-03  4:05 ` Kernel 2.6.30rc7 limits IDE to UDMA33 Robert Hancock
2009-06-03 11:35   ` Grozdan
2009-06-03 12:14     ` Alan Cox [this message]
2009-06-03 12:52       ` Grozdan
2009-06-03 13:01         ` Alan Cox
2009-06-03 13:15           ` Grozdan
2009-06-03 13:39           ` Grozdan
2009-06-04 14:50             ` Grozdan
2009-06-05  9:05               ` Alan Cox
2009-06-05 10:35                 ` Grozdan
2009-06-05 10:42                   ` Alan Cox
2009-06-05 12:43                     ` Grozdan
2009-06-05 13:21                       ` Alan Cox
2009-06-05 14:02                         ` Grozdan
2009-06-06  1:07                     ` Robert Hancock
2009-06-06 14:56                       ` Alan Cox
2009-06-06 18:16                         ` Robert Hancock
2009-06-06 22:08                           ` Alan Cox
2009-06-07  4:39                           ` Grozdan
     [not found]                             ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24                               ` Grozdan
2009-06-07 18:46                                 ` Michael S. Zick
2009-06-07 19:54                                   ` 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=20090603131407.57c490ed@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neutrino8@gmail.com \
    /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