> Targets "speak" the same transport protocol as the HBA.
> This cannot necessarily be said about logical units.
> Bridges are being proposed between SAS and SPI in which
> U160/U320 disks on a SPI bus appear as luns on a single
> SAS target (i.e. the bridge device). If the initiator
> wants to spe
[EMAIL PROTECTED] wrote:
the idea behind this is fine, I just don't like the interface.
Really a target device is nothing more than a container to SCSI. We
already do the transport add/remove calls for targets, I don't see we
need other calls duplicating this. So, I think the
implementation woul
Searched and didn't find anything on archives for this, but I probably just
missed it.
Upgraded from 2.6.8.1 today to 2.6.10, and using my external firewire DVD-RW I
get oopsed. I patched to 2.6.11-rc3 and it's still there, I can't speak for
2.6.9 at this point, I can try later if I have to nar
> the idea behind this is fine, I just don't like the interface.
>
> Really a target device is nothing more than a container to SCSI. We
> already do the transport add/remove calls for targets, I don't see we
> need other calls duplicating this. So, I think the
> implementation would
> look a
> On Sat, 2005-01-29 at 09:03 -0500, [EMAIL PROTECTED] wrote:
> > Updates the recent transport container patch for :
> > - allow device driver-specific attributes to be added to
> class objects
> > - exposes classdev to transport via setup function
>
> I'm not very keen on this for two reas
5 matches
Mail list logo
