All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] AHCI updates: Marvell AHCI PATA works; pata_marvell fate?
Date: Fri, 17 Apr 2009 06:39:58 -0400	[thread overview]
Message-ID: <49E85C7E.5020200@garzik.org> (raw)
In-Reply-To: <20090417105031.607a771e@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> Marvell PATA on 6121 and similar chips should also work, but that hasn't
>> yet been tested.  Here's the full list of what still needs testing:
>>
>> - master + slave devices
>> - ATAPI
>> - 6121 (6123? others?)
> 
> LBA48

And 80-pin cables...  I cannot find where it permits cable detection or 
where DMA/PIO mode in AHCI mode, complicating things :(


>> Also, there is the open question of how to deal with pata_marvell
>> co-existence
> 
> I think for the moment make PATA support by AHCI a config option and as
> soon as we trust it we can get rid of the option and of pata_marvell.

I'm not sure I see the worth of making PATA, solely, a config option?

Today, the choice is either pata_marvell (PATA) or ahci w/ module option 
(SATA).

My patches morph that choice into: pata_marvell (PATA) or mv-ahci (PATA 
+ SATA).

Thus, considering the hardware, if the user disables PATA support in 
mv-ahci, they still have the problem of two drivers competing for the 
same PCI IDs - no matter that the drivers would each probe different bus 
types (PATA, or SATA).

We could skip SATA_MV_AHCI if PATA_MARVELL is set in .config...  Now 
that mv-ahci solely contains Marvell PCI IDs, that would have the effect 
at compile-time that a module option would have at runtime.

	Jeff



  reply	other threads:[~2009-04-17 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  2:39 [PATCH 0/3] AHCI updates: Marvell AHCI PATA works; pata_marvell fate? Jeff Garzik
2009-04-17  2:40 ` [PATCH 1/3] ahci: move core code into new libahci module Jeff Garzik
2009-04-17  2:41 ` [PATCH 2/3] mv-ahci: Add Marvell PATA support Jeff Garzik
2009-04-17  2:42 ` [PATCH 3/3] acard-ahci: Add new ACard ATP AHCI driver Jeff Garzik
2009-04-17  9:50 ` [PATCH 0/3] AHCI updates: Marvell AHCI PATA works; pata_marvell fate? Alan Cox
2009-04-17 10:39   ` Jeff Garzik [this message]
2009-04-17 18:03   ` Ville Syrjälä
2009-04-17 19:14     ` Jeff Garzik
2009-12-27  5:13 ` Raman Gupta
2009-12-27 21:52   ` Robert Hancock
2009-12-28  0:26     ` Raman Gupta
2009-12-28  5:19       ` Raman Gupta
2009-12-30 17:16       ` Tim Small
2010-01-02  8:44         ` Marvell exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (was Re: [PATCH 0/3] AHCI updates: Marvell AHCI PATA works; pata_marvell fate?) Raman Gupta

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=49E85C7E.5020200@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --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 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.