public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: jgarzik@pobox.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI driver support for pata
Date: Wed, 21 Feb 2007 23:45:54 -0600	[thread overview]
Message-ID: <45DD2E12.6000705@shaw.ca> (raw)
In-Reply-To: <fa.IjFXvdcBtWXV65pRZipPd0NVTOA@ifi.uio.no>

Alan wrote:
> - Add a driver for motherboard ACPI method devices
> - Link it after normal drivers so ACPI is not preferred
> - Hook the AMD driver to prefer ACPI for the Nvidia devices if ACPI is
> active
> - While we are at it fix up the simplex clear the AMD driver.
> 
> Depends upon the set_mode -> do_set_mode wrapper patch
> 
> Signed-off-by: Alan Cox <alan@redhat.com>

I tried out 2.6.21-rc1 with the pata_acpi patch. First off, when you 
enable pata_acpi, it appears that the Fedora mkinitrd stuff decides that 
that should be loaded as the first driver. On boot it promptly attempts 
to attach to all of the ATA controllers, including the nForce SATA 
controllers, which somehow it fails to actually drive causing a failure 
to mount the root filesystem. I got around that by blacklisting 
pata_acpi in /etc/modprobe.conf before installing the kernel and 
un-blacklisting it afterwards, so it wouldn't make the initrd try and 
load it, but there must be a better solution.

It does seem to drive the PATA controllers, but the cable detection 
doesn't seem to be working:

scsi5 : pata_acpi
ata5.00: ATAPI, max UDMA/66
ata5.00: limited to UDMA/33 due to 40-wire cable
ata5.00: configured for UDMA/33

I can assure you that is an 80-wire cable on that device :-) I suppose 
next step is adding debug to see where it is having issues?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-22  5:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.IjFXvdcBtWXV65pRZipPd0NVTOA@ifi.uio.no>
2007-02-22  5:45 ` Robert Hancock [this message]
2007-02-22  6:58   ` [PATCH] ACPI driver support for pata Jeff Garzik
2007-02-22 14:24     ` Alan
2007-02-22 17:11       ` Jeff Garzik
2007-02-22 18:29         ` Alan
2007-02-23  0:15           ` Robert Hancock
2007-02-23  9:36             ` Allen Martin
2007-02-23 12:50             ` Alan
2007-02-23 14:38               ` Robert Hancock
2007-02-23 15:53                 ` Alan
2007-02-20 18:12 Alan

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=45DD2E12.6000705@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox