I support the idea of the 2 bit. The EATA protocol requires to specify
either DATA_IN or DATA_OUT or DATA_NONE. The data_out table by itself
is not enough.
-db
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 13, 2001 10:42 AM
To: Oliver Neukum; Daniel Eisenbud; [EMAIL PROTECTED]
Subject: Re: [PATCH] consolidating data direction tables
On Feb 13, 10:24am, Oliver Neukum wrote:
>
> > We currently support a RAID which uses vendor unique commands to do
> > device management. We need special versions of drivers that understand
> > the implied direction of the vendor unique commands. Under Irix, the
> > ds interface explicitly specifies a direction, so no driver code need
> > be changed to support this device.
>
> That's the problem. You'd break the interface.
> Nevertheless, it should be done in 2.5.
What if two bits were used:
0 = direction implied
1 = read from device
2 = write to device
3 = reserved/bidirectional
Then you could maintain compatibility as long as older programs zero
out the unused flags bits.
jeremy
-
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]
