From: Phil Dibowitz <phil@ipom.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise 20378
Date: Mon, 04 Jul 2005 22:50:22 -0700 [thread overview]
Message-ID: <42CA1F9E.4090305@ipom.com> (raw)
In-Reply-To: <42C9F50B.4000508@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Jeff Garzik wrote:
> Phil Dibowitz wrote:
>
>> So, there doesn't appear to be a driver for the 20378 in the kernel...
>> though google showed a few people using some proprietary drivers with
>> varying luck. Ew.
>>
>> I noticed there are a lot of other Promise drivers in the kernel for the
>> same general line, which leads me to believe there may be some interest
>> in getting a 20378 driver in the kernel.
>>
>> So, since I now own a machine with one, I thought I'd drop this list a
>> line and say "I can test stuff and provide info on the chipset"...
>
>
> Just add the PCI ID to drivers/scsi/sata_promise.c...
Markus K. emailed me to let me know about sata_promise, which already
binds to my controller with no errors. I'm wondering if it'll support
the PATA controller on there as well - we'll see. I'll play around with
it and report back. Thanks.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-07-05 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 9:53 Promise 20378 Phil Dibowitz
2005-07-05 2:48 ` Jeff Garzik
2005-07-05 5:50 ` Phil Dibowitz [this message]
2005-07-23 20:38 ` Phil Dibowitz
2005-09-04 7:54 ` Phil Dibowitz
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 19:21 mreuther
2006-04-10 2:50 ` Phil Dibowitz
2006-04-16 21:32 ` Phil Dibowitz
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=42CA1F9E.4090305@ipom.com \
--to=phil@ipom.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).