All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Meier <gf435@gmx.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Driver for sata adapter promise sata300 tx4
Date: Mon, 01 Aug 2005 17:12:00 +0200	[thread overview]
Message-ID: <42EE3BC0.6010002@gmx.net> (raw)
In-Reply-To: <42EE3501.7010107@gentoo.org>

Daniel Drake wrote:
> Otto Meier wrote:
>> This card use the sata chip pdc 40718 (as of my card)
>> the lastest sata_promise kernel with sata promise patch driver 
>> doesn't recognise
>> this card.
>>
>> I added the following line to static struct pci_device_id 
>> pdc_ata_pci_tbl[] in sata_promise.c:
>>
>> { PCI_VENDOR_ID_PROMISE, 0x3d17, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
>> board_20319 },
>>
>> and the card was recognised and seam to work without errors so far.
>
> Yes, this should be fine (this is a 4-port SATA card right?)
>
> Are you happy to produce and submit a patch yourself (read 
> Documentation/SubmittingPatches) or should I submit one for you?
>
> Thanks,
> Daniel
>
>
Yes you are right it is a 4-port sata-II 300 card (PDC40718 ). According to
the promise feature list it should support :

SATA300™ TX4 Highlights

    * Native Command Queuing (NCQ)
    * SATA Tagged Command Queuing (TCQ)
    * Large LBA support for drives above 137GB
    * Supports Serial ATAPI devices
    * Disk Activity LED Headers
    * Flexible future-proof upgrade for users with motherboards that
      only have a PCI interface


My question is also are these features (NCQ/TCQ) and the heigher 
datarate be supported by this
modification? or is only the basic feature set of sata 150 TX4 supported?

Here is the patch:

--- linux/drivers/scsi/sata_promise.c.orig 2005-08-01 17:09:48.474824778 
+0200
+++ linux/drivers/scsi/sata_promise.c 2005-07-31 12:57:06.415979512 +0200
@@ -183,6 +183,8 @@ static struct pci_device_id pdc_ata_pci_
board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },
+ { PCI_VENDOR_ID_PROMISE, 0x3d17, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3d18, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },



Thanks
Otto



  reply	other threads:[~2005-08-01 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  9:19 Driver for sata adapter promise sata300 tx4 Otto Meier
2005-08-01 14:43 ` Daniel Drake
2005-08-01 15:12   ` Otto Meier [this message]
2005-08-01 15:28   ` Otto Meier
2005-08-01 16:16     ` Daniel Drake
2005-08-01 20:17       ` Jens Axboe
2005-08-01 20:30         ` Jeff Garzik
2005-08-01 20:35           ` Jens Axboe
2005-08-02  8:18             ` Otto Meier
2005-08-01 20:32         ` Jens Axboe
2005-08-01 20:36           ` Jeff Garzik
2005-08-01 20:42             ` Jens Axboe
2005-08-01 20:49               ` Jeff Garzik
2005-08-02  6:48                 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01 14:14 Otto Meier

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=42EE3BC0.6010002@gmx.net \
    --to=gf435@gmx.net \
    --cc=dsd@gentoo.org \
    --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.