>From: Patrick Ohly <[EMAIL PROTECTED]>
>> >From: [EMAIL PROTECTED]
>>
>> >> As you see the March 99 version if sg.c implemented
>> SG_SET_RESERVED_SIZE as NO-OP.
>>
>> >I don't know which sg version this file corresponds to. I only have the
>>
>> I told you: the march 99 version!
>As I haven't followed the complete history (especially including
>publishing dates) I am not able to directly relate this date to
>a interface definition.
It seems that you forgot what your original question has been.
It was similar to:
"Why did not libscg support this earlier"
.... Well it is irrelevant how the Author calls a version.
Important is that in March 99 I had 3 months of fruitless discussion
with the new SG maintainer and I decided that it would not make sense
to try to extend this undertake.
The version from March 99 _is_ not usable for libscg; this is the important
comclusion. The interface from March 99 would force me to send a command
with a high DMA count to the target to check if it would work.
Libscg is intended to be a generalised SCSI transport lib. I cannot
send unpredictable commands to targets just to check for SCSI transport
code properties.
So a short answer to your question could be:
If the sg maintainer would have been interested in a cooperation - yes.
>> >> You may use this feature if you open a SCSI * handle for scanning.
>> >> This is done by using a NULL pointer for char *scsidev.
>> >> An empty string should work too.
>>
>> >At the moment I call scsi_open() with only bus, target and lun (i.e.
>> >NULL scsidev) even if I only want to use one drive, because that's the
>> >only information I have. The Amiga scsi.device identifies drives this
>> >way, so I obtain a list of available drives and their bus/target/lun
>> >each time the emulator is started.
>>
>> >Do I have to build a scsidev string that repeats the bus/target/lun
>> >values like in the cdrecord "dev=" argument, or wouldn't it be better
>> >to accept the tuple "scsidev NULL, bus/target/lun != -1" as another way
>> >to open a SCSI handle for just one drive?
>>
>> It looks as if you are using inofficial interfaces that are not allowed
>> to be used by endusers. The scsi_open() interface may be changed every
>> day, open_scsi() is the public interface.
>Then it was a typo when you said "The drive(s) that have been specified
>by scsi_open()" above and it should have been "open_scsi()"?
>How can I distinguish inofficial and official interfaces? Both
>open_scsi() and scsi_open() are defined in scsitransp.h without
>comments. Again, I think this shows the need for more documentation.
Well you already asked for this last year and I answered this question
on 13. Apr. 1999. You decided to ignore my hint that you are
not using the official interface for the mainstream code.
>I'll use open_scsi() with a NULL scsidev to do a bus scan.
>How can I build a scsidev string to open another SCSI pointer to
>access just one drive in a portable way?
Read the cdrecord man page. It has a paragraph about the dev= parameter.
J�rg
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
