On Sun, Mar 04, 2001 at 12:03:47AM -0600, [EMAIL PROTECTED] wrote:
> On Sat, Mar 03, 2001 at 06:59:52PM -0800, Matthew Dharm wrote:
> > You're basically right. The good news is that all devices so far which
> > need fake inquiry data are all direct-access devices.
> >
> > And fill_inquiry_respon
On Sat, Mar 03, 2001 at 08:54:48PM -0600, [EMAIL PROTECTED] wrote:
> On Sat, Mar 03, 2001 at 06:01:20PM -0800, Matthew Dharm wrote:
> > We have the strings in the unusual device structure for just this reason.
> > A better fix would be to have a scsiglue.c function which could turn these
> > strin
On Sat, Mar 03, 2001 at 06:01:20PM -0800, Matthew Dharm wrote:
> On Sat, Mar 03, 2001 at 06:03:49PM -0600, [EMAIL PROTECTED] wrote:
> > There was some discussion on this digital camera a few months back, but
> > I haven't seen anything since. The last message was from Steve Kann and
> > included
This is an automated response.
There were problems with the email commands you sent to Mailman via
the administrative address
<[EMAIL PROTECTED]>.
To obtain instructions on valid Mailman email commands, send email to
<[EMAIL PROTECTED]> with the word "help"
in the subject line or in the body of
This is _way_ to device specific.
We have the strings in the unusual device structure for just this reason.
A better fix would be to have a scsiglue.c function which could turn these
strings into an INQUIRY response, based on a flag set in the flag field.
Matt
On Sat, Mar 03, 2001 at 06:03:49PM
Hi All,
Don't know who didn't receive a posting because of this, but
thought you should know...
regards,
Stephen.
--
/--+-=-=-=-=-+--
There was some discussion on this digital camera a few months back, but
I haven't seen anything since. The last message was from Steve Kann and
included some instructions on the fix he proposed. Thanks Steve, the
first part works. Here is my implementation, it's not great, but it
works.
Here
