[8535] in linux-scsi channel archive
Re: SCSI_IOCTL_GET_IDLUN changes in lk 2.3/2.4
daemon@ATHENA.MIT.EDU (schilling@fokus.gmd.de)
Tue Apr 4 11:30:00 2000
Date: Tue, 4 Apr 2000 17:08:05 +0200 (MEST)
Message-Id: <200004041508.RAA01611@burner.fokus.gmd.de>
From: schilling@fokus.gmd.de
To: dgilbert@interlog.com, linux-scsi@vger.rutgers.edu
Cc: dhinds@csb.stanford.edu, schilling@fokus.gmd.de
>From dgilbert@interlog.com Sat Apr 1 18:14:22 2000
>A recent posting on the SANE newsgroup reported the "scsi_info"
>program failing. A cause for this failure on a recent 2.3 series
>kernel is that the SCSI_IOCTL_GET_IDLUN ioctl made available
>by the SCSI mid-level code (and hence to all scsi device
>file descriptors) has changed. The cdrecord application is
>also effected by this change.
>> "four_in_one" is made up as follows:
>> (scsi_device_id | (lun << 8) | (channel << 16) | (host_no << 24))
>> These 4 components are assumed (or masked) to be 1 byte each.
>>
>> The 'host_no' element is a change in lk 2.3/2.4 kernels. [In the lk 2.2
>> series and prior it was 'low_inode & 0xff' of the /proc pseudo file system
>> entry corresponding to the adapter/host.] This change makes the use of the
>> SCSI_IOCTL_GET_BUS_NUMBER ioctl superfluous.
As cdrecord only uses this number to have one more criteria to do the mapping,
I would assume that cdrecord will work as before.
Did you definitely observe problems?
Jörg
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
