From: Simon Oosthoek <simon.oosthoek@ti-wmc.nl>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SATA status report updated
Date: Fri, 19 Aug 2005 10:09:14 +0200 [thread overview]
Message-ID: <430593AA.50201@ti-wmc.nl> (raw)
In-Reply-To: <42FC2EF8.7030404@pobox.com>
Jeff Garzik wrote:
>
> Things in SATA-land have been moving along recently, so I updated the
> software status report:
>
> http://linux.yyz.us/sata/software-status.html
>
> Although I have not updated it in several weeks, folks may wish to refer
> to the hardware status report as well:
>
> http://linux.yyz.us/sata/sata-status.html
>
> Thanks to all the hard-working SATA contributors!
>
Good overview!
I'm wondering how the support for the SIS 182 controller is doing, I
noticed they have a GPL driver on their website for kernel 2.6.10, which
is not a drop in replacement for sata_sis.c in 2.6.12.5, I haven't tried
compiling it as an add-on module outside the tree, though...
Adding the 0x182 identifier to the 180 driver does compile (duh!), but I
haven't tried it on hardware.
As a temporary measure, there was a patch posted to this list [1] a
while ago, would it be a good idea to include this while full support is
being worked on?
Cheers
Simon
[1]
Patch signed-off-by: Rainer Koenig <Rainer.Koenig@fujitsu-siemens.com>
--- linux-2.6.12.4/drivers/scsi/sata_sis.c 2005-08-05 09:04:37.000000000
+0200
+++ linux/drivers/scsi/sata_sis.c 2005-08-11 10:22:07.000000000 +0200
@@ -62,6 +62,7 @@
static struct pci_device_id sis_pci_tbl[] = {
{ PCI_VENDOR_ID_SI, 0x180, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sis_180 },
{ PCI_VENDOR_ID_SI, 0x181, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sis_180 },
+ { PCI_VENDOR_ID_SI, 0x182, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sis_180 },
{ } /* terminate list */
};
next prev parent reply other threads:[~2005-08-19 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 5:09 SATA status report updated Jeff Garzik
2005-08-12 5:40 ` Rob van Nieuwkerk
2005-08-12 5:45 ` Jeff Garzik
2005-08-12 18:07 ` David Greaves
2005-08-12 10:44 ` Matthew Garrett
2005-08-12 21:30 ` Jeff Garzik
2005-08-13 8:45 ` Erik Slagter
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:46 ` Luben Tuikov
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 21:33 ` Jeff Garzik
2005-08-19 8:09 ` Simon Oosthoek [this message]
2005-08-21 17:11 ` Mogens Valentin
2005-08-21 18:05 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-12 10:24 Daniel J Blueman
2005-08-12 21:30 ` Jeff Garzik
[not found] <4AA7B-4jm-5@gated-at.bofh.it>
[not found] ` <4DagM-7c8-43@gated-at.bofh.it>
2005-08-19 9:14 ` Rainer Koenig
2005-08-19 18:34 ` Jeff Garzik
2005-08-19 23:01 ` Simon Oosthoek
2005-08-20 0:02 ` Jeff Garzik
[not found] <4DbcF-8ux-3@gated-at.bofh.it>
[not found] ` <4DbcG-8ux-5@gated-at.bofh.it>
[not found] ` <4DbcF-8ux-1@gated-at.bofh.it>
[not found] ` <4DjWG-4ea-19@gated-at.bofh.it>
[not found] ` <4Do9X-1IZ-5@gated-at.bofh.it>
[not found] ` <4Dp62-304-15@gated-at.bofh.it>
2005-08-20 15:36 ` Rainer Koenig
2005-08-22 8:07 ` Simon Oosthoek
2005-08-22 18:07 ` Rainer Koenig
2006-05-15 15:20 Jeff Garzik
2006-05-15 17:07 ` Sven-Haegar Koch
2006-05-15 18:17 ` Jeff Garzik
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=430593AA.50201@ti-wmc.nl \
--to=simon.oosthoek@ti-wmc.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox