linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tyler <pml@dtbb.net>
Cc: Brett Russ <russb@emc.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.13] libata: Marvell SATA support (PIO mode)
Date: Sat, 03 Sep 2005 13:29:30 -0400	[thread overview]
Message-ID: <4319DD7A.7000702@pobox.com> (raw)
In-Reply-To: <4319AE7B.3010304@dtbb.net>

Tyler wrote:
> Brett Russ wrote:
> 
>> Some (non-functional) cleanup modifications since the version 0.10
>> driver I sent out 2005-08-30.  Also adding signed-off-by for Jeff's
>> upstream push.  This is my libata compatible low level driver for
>> the Marvell SATA family.  Currently it successfully runs in PIO mode
>> on a 6081 chip.  EDMA support is in the works and should be done
>> shortly.  Review, testing (especially on other flavors of Marvell),
>> comments welcome.
>>
>> Thank you,
>> BR
>>
>> Signed-off-by: Brett Russ <russb@emc.com>
>>
>>  
>>
> [snip..]
> 
> Please find attached patches that add the Adaptec 1420SA controller to 
> the PCI ID list in the driver, and a small note in the kernel config 
> option to state so.  This is untested as of currently, if anyone has a 
> 1420SA to try, that would be great..  The one I had access to is now 
> gone to a remote location out of reach for testing.  I read in one post 
> I found with google, that the 1420SA uses a 6541 chip instead of a 6041, 
> but I am not able to verify this, and also don't know if it may still 
> work as a 6041.  The card is still a Sata2, PCI-X card, with 4 ports, 
> the same as the 6041 based cards.  This patch may or may not be 
> useful..  The card comes with a manufacturer ID of 9005 according to a 
> linux PCI-ID list, which is a secondary id of Adaptec's known as 
> ADAPTEC2, and an actual PCI Id of 0241.

I would prefer to have it tested, before accepting this patch...

	Jeff

  reply	other threads:[~2005-09-03 17:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 18:36 [RFC][PATCH 2.6.13] Marvell SATA support (PIO mode) Brett Russ
2005-08-30 20:48 ` Jeff Garzik
2005-09-01 14:27   ` [PATCH 2.6.13] libata: " Brett Russ
2005-09-01 14:40     ` Christoph Hellwig
2005-09-01 19:48       ` Jeff Garzik
2005-09-01 19:58         ` Christoph Hellwig
2005-09-01 20:03           ` Jeff Garzik
2005-09-01 20:04             ` Jeff Garzik
2005-09-01 20:05             ` Christoph Hellwig
2005-09-01 20:28               ` Jeff Garzik
2005-09-01 22:26       ` Brett Russ
2005-09-02  1:32         ` Brett Russ
2005-09-02 17:16         ` Bogdan Costescu
2005-09-02 17:55         ` Ray Lee
2005-09-07  5:56         ` Jeff Garzik
2005-09-07 14:40           ` Brett Russ
2005-09-07 16:31             ` Bogdan Costescu
2005-09-03 14:08     ` Tyler
2005-09-03 17:29       ` Jeff Garzik [this message]
2005-09-27  5:36       ` Tyler
2005-08-31 10:35 ` [RFC][PATCH 2.6.13] " Jiri Slaby
2005-08-31 11:37   ` Brett Russ
  -- strict thread matches above, loose matches on Subject: below --
2005-09-01 20:19 [PATCH 2.6.13] libata: " linux

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=4319DD7A.7000702@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pml@dtbb.net \
    --cc=russb@emc.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 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).