All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Bill Waddington <william.waddington@beezmo.com>
Subject: Re: SATA Conflict with PATA DMA
Date: Sun, 16 Apr 2006 00:51:02 +0100	[thread overview]
Message-ID: <1145145062.32107.1.camel@localhost.localdomain> (raw)
In-Reply-To: <444182B3.4050608@shaw.ca>

On Sad, 2006-04-15 at 17:33 -0600, Robert Hancock wrote:
> The other way around is to make libata handle the PATA devices. I'm not 
> sure if the support for that on combined mode is in mainline or if you 
> need Alan's libata PATA patch for that?

There should be enough in 2.6.17-rc1 to just add the needed PCI
identifiers for recent chips to work SATA/PATA. There are some ugly bugs
left in the base code that the -ac patches fix in ata_piix but the core
stuff needed is in the base tree


  reply	other threads:[~2006-04-15 23:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <61Y0s-AN-23@gated-at.bofh.it>
     [not found] ` <61UzA-43O-5@gated-at.bofh.it>
     [not found]   ` <61Y0s-AN-25@gated-at.bofh.it>
     [not found]     ` <61Y0s-AN-21@gated-at.bofh.it>
2006-04-15 23:33       ` SATA Conflict with PATA DMA Robert Hancock
2006-04-15 23:51         ` Alan Cox [this message]
     [not found] <fa.m9JwGQvLBixssS4UodPQfih6Ygk@ifi.uio.no>
2006-04-15 17:02 ` Esben Stien
2006-04-15 16:41   ` Jeff Garzik
2006-04-23 17:54     ` Esben Stien
2006-04-23 18:00       ` Esben Stien
2006-06-10 20:39         ` Esben Stien
2006-06-15 17:29         ` Esben Stien
     [not found]   ` <fa.foo0W8w4UdiDztK9eBiA9awyAi8@ifi.uio.no>
2006-04-15 18:38     ` Bill Waddington
2006-04-16  3:48       ` Alistair John Strachan
2006-04-16  4:30         ` Randy.Dunlap
     [not found]     ` <fa.UjEGyG0y7x3qVLsO0eHpXVza2r8@ifi.uio.no>
2006-06-10 22:58       ` Bill Waddington

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=1145145062.32107.1.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.waddington@beezmo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.