I am creating an application which should communicate with the different
HBAs.

*Keith

Thanks for your valuable suggestions !!

*
I am getting problem with the adaptec HBA. I tried today to use uscsi for
communicating with adaptec HBA but not succeeded.

I would highly apprciate if I get answers to my questions.

1. which directory/file is being used for scsi devices list. I tried
/dev/cfg, dev/dsk, dev/rdsk but getting error as " No such file or
directory".
2. I am getting an error "inappropriate ioctl for device" or "Inappropriate
argument" when trying to communicate with HBA. can I get the root cause
behind this?
3. In Linux there is sg driver resonsible for SCSI ioctls. On solaris is
there any kind of driver is available?
4. Is there any congiguration to be doe before using uscsi  functionality.
5. Besides uscsi is there any different way to communicate with HBAs on SCSI
ioctls.

As these might be question to be raised by new persons next to me, kindly
give solution if anyone have, as it will be useful to all solaris system
Learners otherwise I might have to stuck with the Windows OS.



Regards,

Prakash Bedge


On Mon, Feb 25, 2008 at 12:59 AM, Keith M Wesolowski <
[EMAIL PROTECTED]> wrote:

> On Sun, Feb 24, 2008 at 08:31:18PM +0530, aakash berde wrote:
>
> > I am trying to communicate with adaptec SCSI HBA on solaris 10 OS.
> > But I am not able to properly use the scsi/uscsi ioctls comands.
>
> You can find HBA nodes in /dev/cfg/.  At least in general; I assume
> they're there for Adaptec HBAs but I don't know for sure as I never
> use those parts.
>
> However, uscsi(7I) is for sending commands to SCSI targets, not HBAs.
> The interface with HBAs tends to be proprietary and specific to the
> HBA; raidctl(1M) uses some of those interfaces, which are generally
> undocumented.  The uscsi(7I) interface is fairly well-documented and
> is not that hard to use if you are sufficiently familiar with the SPC
> and SAM documents available at t10.org.  You can use it to, for
> example, enumerate and control elements exposed by an SES process or
> control a tape changer or optical jukebox.  Using it for I/O as
> typically provided by sd(7D) is unlikely to be a good idea.
>
> What are you trying to accomplish?
>
> --
> Keith M Wesolowski              "Sir, we're surrounded!"
> Fishworks                       "Excellent; we can attack in any
> direction!"
>
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to