On Fri, 2001-11-02 at 14:23, kevin wrote:
> I have a webcam module driver working fairly well, with the exception
> that if the driver is loaded before the camera is plugged in, the camera
> frequently does not initialize correctly. It seems to work nearly always
> if the camera is already p
I have a webcam module driver working fairly well, with the exception
that if the driver is loaded before the camera is plugged in, the camera
frequently does not initialize correctly. It seems to work nearly always
if the camera is already plugged in when the driver is loaded; the
camera
Quoting Randy.Dunlap <[EMAIL PROTECTED]>:
> Dmitri wrote:
> >
> > Quoting Pete Zaitcev <[EMAIL PROTECTED]>:
> >
> > > Guys,
> > >
> > > I noticed a funny thing... When drivers ask for a pipe to be
> > > made up, they often pass an endpoint address with 0x80 bit set.
> > > This makes for a pipe
> > - return (dev->devnum << 8) | (endpoint << 15) |
> > + return (dev->devnum << 8) | ((endpoint & 0xf) << 15) |
> > ((dev->speed == USB_SPEED_LOW) << 26);
>
> Total 16 endpoints? Did you mean 0x7f?
In usb.h:
/*
* Calling this entity a "pipe" is glorifying it. A USB pipe
* is
Dmitri wrote:
>
> Quoting Pete Zaitcev <[EMAIL PROTECTED]>:
>
> > Guys,
> >
> > I noticed a funny thing... When drivers ask for a pipe to be
> > made up, they often pass an endpoint address with 0x80 bit set.
> > This makes for a pipe with 0x0040 bit set, which is in the
> > reserved area. I
Quoting Pete Zaitcev <[EMAIL PROTECTED]>:
> Guys,
>
> I noticed a funny thing... When drivers ask for a pipe to be
> made up, they often pass an endpoint address with 0x80 bit set.
> This makes for a pipe with 0x0040 bit set, which is in the
> reserved area. It appears not to harm anything,
Guys,
I noticed a funny thing... When drivers ask for a pipe to be
made up, they often pass an endpoint address with 0x80 bit set.
This makes for a pipe with 0x0040 bit set, which is in the
reserved area. It appears not to harm anything, but is annoying
in printouts. How about this:
--- linu
> > Why would that be different from read or write ?
>
> What do you mean? If you mean: "of course the ioctl callback
> can be called during disconnect, just like for other reads and
> writes", well I agree. I didn't write the driver, I'm trying to fix
> it so it works with SMP; this looks like
cc please, I am not on this list.
I get an intermittent usb failure at boot time.
kernel 2.4.14-pre6+xfs+kdb.
gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-81)
Compaq laptop, armada 1598DT
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 8
model name
