linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Erik Slagter <erik@slagter.name>, Mark Lord <liml@rtr.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata and PATA devices
Date: Thu, 11 Aug 2005 16:25:50 -0400	[thread overview]
Message-ID: <42FBB44E.1020004@pobox.com> (raw)
In-Reply-To: <42FBB33D.8050003@pobox.com>

Jeff Garzik wrote:
> The system is thus:
> 
> 1) drivers/pci/quirks.c reserves SATA ports (only!) for libata
> 2) Legacy IDE driver claims the unreserved PATA port
> 3) libata loads and uses the ports reserved in #1
> 
> This requires a specific kernel configuration:
> (a) CONFIG_IDE_GENERIC be set, and
> (b) IDE driver is built into the kernel.
> 
> This also requires that your SATA device is listed in drivers/pci/quirks.c.
> 
> Both (a) and (b) are kernel configuration issues.  I never saw anything 
> in any email thread indicating that (a) and (b) were verified and 
> eliminated as problem sources.

To be more clear:

The legacy ISA IDE driver, not the PIIX IDE driver, must claim the PATA 
port.

That is why it was incorrect to add ICH SATA PCI IDs to 
drivers/ide/pci/piix.c.

	Jeff



  reply	other threads:[~2005-08-11 20:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 17:48 libata and PATA devices Andreas Klöckner
2005-08-08  1:43 ` Tejun Heo
2005-08-08  3:02   ` Jeff Garzik
2005-08-08 10:10     ` Erik Slagter
2005-08-09 13:48       ` Mark Lord
2005-08-09 14:10         ` Mark Lord
2005-08-09 18:01           ` Jeff Garzik
2005-08-09 17:05         ` Erik Slagter
2005-08-09 18:02           ` Jeff Garzik
2005-08-09 17:59         ` Jeff Garzik
2005-08-11  3:57         ` Jeff Garzik
2005-08-11  9:37           ` Erik Slagter
2005-08-11 10:03             ` Bartlomiej Zolnierkiewicz
2005-08-11 10:17               ` Erik Slagter
2005-08-11 10:26                 ` Bartlomiej Zolnierkiewicz
2005-08-11 15:29                   ` Erik Slagter
2005-08-11 15:57                     ` Bartlomiej Zolnierkiewicz
2005-08-11 16:48                       ` Erik Slagter
2005-08-11 17:05           ` Mark Lord
2005-08-11 17:19             ` Jeff Garzik
2005-08-11 19:38               ` Erik Slagter
2005-08-11 20:19                 ` Wes Newell
2005-08-11 20:21                 ` Jeff Garzik
2005-08-11 20:25                   ` Jeff Garzik [this message]
2005-08-13 11:30                   ` Erik Slagter
2005-08-13 15:33                     ` Jeff Garzik
2005-08-13 15:50                       ` Erik Slagter
2005-08-13 15:56                         ` Jeff Garzik
2005-08-13 16:03                           ` Erik Slagter
2005-08-13 16:44                             ` Jeff Garzik
2005-08-13 16:53                               ` Erik Slagter
2005-08-15 21:39                                 ` Mark Lord
2005-08-16  7:21                                   ` Erik Slagter
2005-08-13 15:56                       ` Tyler
2005-08-13 15:57                         ` Jeff Garzik
2005-08-13 16:05                           ` Erik Slagter
2005-08-13 16:42                             ` Jeff Garzik

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=42FBB44E.1020004@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=erik@slagter.name \
    --cc=liml@rtr.ca \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).