From: Chris Haumesser <chris@mail-test.us>
To: kallol@nucleodyne.com
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: promise sx8 sata driver
Date: Tue, 24 May 2005 11:00:24 -0700 [thread overview]
Message-ID: <42936BB8.3070903@mail-test.us> (raw)
In-Reply-To: <1116909972.15027.3.camel@driver>
I don't understand either. The Promise driver (I think this is carmel?)
found at
http://www.promise.com/support/download/download2_eng.asp?productID=125&category=all&os=100#
seems to be GPL. I haven't tested it extensively yet, but it appears to
provide scsi device nodes that grub recognizes readily.
Why are there two GPL driver projects for this card, and what is the
difference? Is there something wrong with promise's driver, or
inherently superior in the kernel driver? How is one supposed to
choose? There is very little documentation for either driver, so it is
quite unclear which is appropriate for a given application.
-C-
Kallol Biswas wrote:
>How good is 2.6.6 carmel.c driver for sx8 adapters? Does it support
>the promise adapter? Why have you developed sx8.c?
>
>
>On Mon, 2005-05-23 at 15:55, Jeff Garzik wrote:
>
>
>>Chris Haumesser wrote:
>>
>>
>>>The sx8 driver does not use libata, and it is a separate block device,
>>>outside of the scsi and ata hierarchies. If I compile the driver into
>>>my kernel, I end up with /dev/sx8/0 and /dev/sx8/0p1, etc. However, no
>>>scsi disk devices are created, and grub does not recognize that
>>>/dev/sx8/ devices are disks. There's no indication in /proc/scsi/ that
>>>they are being registered with the scsi subsystem; this is clearly
>>>different from every other sata controller I've used. I've been
>>>googling this for days, with no real luck. I have found changelogs for
>>>grub that suggest that my version (0.95) should support booting from the
>>>sx8.
>>>
>>>
>>sx8 is a separate block driver, and has nothing whatsoever to do with scsi.
>>
>>
>>
>>
>>>So my question is, how does one use this driver for sata disks? Is my
>>>problem a grub problem, or does it have something to do with the fact
>>>
>>>
>>a grub problem
>>
>>
>>
>>
>>>What is the relationship between the promise driver and the one included
>>>in the kernel? Why does one work differently from the other? Is there
>>>
>>>
>>Promise SX8 provides neither an ATA nor SCSI interface to the developer,
>>so its not written as an ATA or SCSI driver.
>>
>> Jeff
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>
>
>
next prev parent reply other threads:[~2005-05-24 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 21:42 promise sx8 sata driver Chris Haumesser
2005-05-23 22:55 ` Jeff Garzik
2005-05-24 6:16 ` Kallol Biswas
2005-05-24 18:00 ` Chris Haumesser [this message]
2005-05-24 18:20 ` 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=42936BB8.3070903@mail-test.us \
--to=chris@mail-test.us \
--cc=jgarzik@pobox.com \
--cc=kallol@nucleodyne.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox