On 10/03/05 10:26, David Lang wrote:
> in this case wouldn't it be trivial to write a 'null transport' driver
> that just passed things down to the card to let the firmware deal with it?
> (reformatting the data if needed)
Hi David,
I think it is trivial.
Your LLDD would define the host template and register it
with SCSI Core. This way you _bypass_ the Transport Layer.
(This is what you call null driver -- as is traditionally done
in SCSI Core due to the legacy LLDDs (to which MPT caters
for 100% backward software compatibility))
Else if your LLDD is just an inteface to the interconnect:
i.e. it only implements Execute SCSI RPC and TMFs, then
you'd register with the Transport Layer (SBP or USB or SAS)
which will do all Transport related tasks, and then that
Transport Layer (USB, SBP or SAS) would register a scsi host
with SCSI Core.
Luben
> having a null driver for a layer for some hardware, and a much more
> complex driver for the same layer for other hardware is fairly common in
> Linux. I believe ti was Linus that said in an interview that Linux is now
> largely designed for an ideal abstracted CPU, with code put in on the
> architectures that don't have a feature to simulate that feature in
> software.
>
> David Lang
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
