From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Andre Hedrick <andre@linux-ide.org>,
reid@reidspencer.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: Any experience with Promise PDC20376 and SATA RAID?
Date: 31 May 2003 17:06:32 +0100 [thread overview]
Message-ID: <1054397191.27312.11.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3ED8D709.9060807@gmx.net>
On Sad, 2003-05-31 at 17:23, Carl-Daniel Hailfinger wrote:
> Reid Spencer wrote:
> > I think the kernel doesn't know about the device number (105a:3376 =
> > PDC20376) since it isn't in the kernel's drivers/pci/pci.ids file
> > (latest device is 7275 PDC20277)and it doesn't recognize the device when
> > it processes the IDE devices at boot up. All I get is:
20376 is not currently supported. Promise do have their own GPL driver
which handles this device as if it were a scsi adapter. In the same way
that Jeff Garzik has realised we need to go this path for smart SATA
stuff so have promise.
Figuring out what to do about all this for 2.4 is on my pending pile
still - do we merge a minimal support into base 2.4.x as FreeBSD did
with their support or do we merge a scsi layer driver that can actually
make use of the command queueing (not neccessarily tagged) on the device
and/or the hardware XOR engine.
next prev parent reply other threads:[~2003-05-31 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030528160001.21400.75235.Mailman@listman.rdu-colo.redhat.com>
[not found] ` <1054139205.1257.11.camel@bashful.x10sys.com>
2003-05-31 16:23 ` Carl-Daniel Hailfinger
2003-05-31 16:06 ` Alan Cox [this message]
2003-06-02 9:22 ` Andre Hedrick
2003-05-31 17:07 Mitch
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=1054397191.27312.11.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=andre@linux-ide.org \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reid@reidspencer.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
all inboxes | Powered by JetHome®