What you're seeing there is SAF-TE, not SES. X'ing out the vendor is amusing-
given the ID it's set at: it looks like the 2nd GEM chip on a Sun D1000.

Yes- I have a driver *almost* ready for this (It's a copy of one I did for
Solaris a few years back that) and have also now released into OpenBSD,
FreeBSD (and NetBSD). It supports both SAF-TE and SES. Actually, it maps
SAF-TE into SES (SAF-TE is almost a perfect subset).

It's not a HBA driver- it's a target driver much like sd or st.

The problem which I haven't resolved is how to link this up with the other
environmental protocols- lm78, etc. There's a lot of question as to how this
should be reported, i.e., what the management framework. This is a lot of work
to do this right. The stuff I did for Sun (&& FreeBSD) uses an ioctl framework
that is actually pretty good, but that makes it problematic in terms of using
either a /proc or a sysctl interface with plays well with other frameworks.
I estimated it was a solid week or so of work to get this done, and as this
has no customer for me, it's been falling to the bottom of the list for a
while.

If there's any interest here in this, I'll finish the ioctl version and put it
out there for you to play with. I did some toy management tools for reporting
this information- it's in the FreeBSD 4.0 release in /usr/share/examples.

On Wed, 5 Apr 2000 [EMAIL PROTECTED] wrote:

> 
> 
> 
> Do any of the main stream Linux SCSI drivers (Adaptec, NCR/Symbios, Qlogic,
> etc.) out there support SCSI Enclosure Services (SES or SAF-TE) devices?
> 
> My aic7xxx /proc/scsi/scsi contains a
> Host: scsi0 Channel: 00 Id: 14 Lun: 00
>   Vendor: xxx      Model: SAF-TE           Rev: 2
>   Type:   Processor                        ANSI SCSI revision: 02
> but I don't see that mapped to anything in /dev
> 
> Or is Linux currently unable to fully support SES/SAF-TE capable SCSI
> boxes?
> 
> If SES is currently supported, where do the "my fan quit" messages go?
> 
> Thanks,
> Steve
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to