public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Nelson <mdnelson8@gmail.com>,
	linux-ide@vger.kernel.org, Mikael Pettersson <mikpe@it.uu.se>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [RFC][PATCH] ahci: Add support for Promise PDC42819
Date: Tue, 02 Sep 2008 15:22:42 -0400	[thread overview]
Message-ID: <48BD9282.702@garzik.org> (raw)
In-Reply-To: <20080902145710.2034690d@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> Refresh my memory...  what is the problem with loading pata_marvell first?
> 
> The fact its almost impossible to do with a distribution kernel. eg
> you can't make it work with Fedora (see the Fedora bugs assigned to
> you)

Hogwash -- just load one driver before the other.


> If pata_marvell should be driving these chips please remove the entries
> from the ahci.c driver as I asked before.
> 
> If ahci.c should be driving them then we need the documentation for
> whatever extension they use driving the ports via AHCI. Clearly there is
> one as its possible under Windows.

Situation before ahci mod:

	Users with PATA may use pata_marvell.
	Users wanting SATA screwed.
	Users wanting PATA+SATA screwed.

Situation after ahci mod:

	Users with PATA may use pata_marvell
	Users with SATA may use ahci
	Users wanting PATA+SATA screwed


>> AFAICS, if you load pata_marvell before ahci, it will grab the PATA 
>> disks and the PCI device itself.
> 
> If you have a degree in initrd-foo

Just switch the order of 'ahci' and 'pata_marvell' in 
/etc/modprobe.conf, then use Fedora's tools regenerate the initrd.

See?  It's not rocket science, and the current configuration can be 
easily made to work for Fedora users.

	Jeff




  reply	other threads:[~2008-09-02 19:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65a6ef750809020403i52228319u9e3197e4062941bc@mail.gmail.com>
2008-09-02 11:19 ` [RFC][PATCH] ahci: Add support for Promise PDC42819 Jeff Garzik
2008-09-02 11:53   ` Alan Cox
2008-09-02 12:01     ` Jeff Garzik
2008-09-02 13:57       ` Alan Cox
2008-09-02 19:22         ` Jeff Garzik [this message]
2008-09-02 22:18           ` Alan Cox
2008-09-02 22:30           ` Alan Cox
2008-09-02 11:55   ` Mark Nelson
2008-09-02 12:08     ` Mikael Pettersson
2008-09-02 12:21       ` Mark Nelson
2008-09-04 10:37         ` Jeff Garzik
2008-09-04 11:59           ` Mark Nelson
2008-09-04 13:43             ` Jeff Garzik
2008-09-04 14:27               ` Mikael Pettersson
2008-09-04 14:28               ` Alan Cox
2008-09-05  2:31                 ` Mark Nelson
2008-09-05  2:28               ` Mark Nelson
2008-10-16 11:18               ` Mark Nelson

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=48BD9282.702@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdnelson8@gmail.com \
    --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