On Wednesday 13 October 2004 5:10 am, Brian Murphy wrote:
> I have found out the problem is that the usb_parse_configuration
> routine does not take account of descriptors which lie after the last
> interface descriptor so the extralen parameters are set to 0 even though
> there *is* extra informa
Am Mittwoch, 13. Oktober 2004 23:17 schrieb Brian Murphy:
> >That is a common (mis)reading. Therefore a fix is in the pipeline and
> >hopefully in 2.6.9.
> >
> >
> >
> If you really believe this to be a misreading where in the standards do
> they give
> *any* indication of the order of descript
Am Mittwoch, 13. Oktober 2004 22:23 schrieb David Brownell:
> > Is it then a good thing to rely on the existance
> > of a union descriptor to signal the validity of a CDC device?
>
> For devices that allegedly implement a class specification,
> there need to be limits on how much nonconformance a
Oliver Neukum wrote:
OK but in 2.6.8.1 the endpoint extra info is not searched for class
specific descriptors.
It seems perfectly reasonable to me to put these descriptors after the
endpoint
descriptors.
That is a common (mis)reading. Therefore a fix is in the pipeline and
hopefully in 2.6.9
> OK but in 2.6.8.1 the endpoint extra info is not searched for class
> specific descriptors.
> It seems perfectly reasonable to me to put these descriptors after the
> endpoint
> descriptors.
That is a common (mis)reading. Therefore a fix is in the pipeline and
hopefully in 2.6.9.
> You find
On Wednesday 13 October 2004 11:11 am, Brian Murphy wrote:
> OK. But I have a Lasat modem which is ~6 years old which puts all the
> class specific descriptors at the end after the *normal* descriptors
> and which has worked up to 2.6.7.
That's probably when the CDC descriptor parsing was added;
David Brownell wrote:
On Wednesday 13 October 2004 5:10 am, Brian Murphy wrote:
I have found out the problem is that the usb_parse_configuration
routine does not take account of descriptors which lie after the last
interface descriptor so the extralen parameters are set to 0 even though
there *
Am Mittwoch, 13. Oktober 2004 14:10 schrieb Brian Murphy:
> Hi,
> Because of the new method of looking for a union descriptor to detect an ACM
> device detection of several modems I have fails.
>
> I have found out the problem is that the usb_parse_configuration
> routine does not take account of
Hi,
Because of the new method of looking for a union descriptor to detect an ACM
device detection of several modems I have fails.
I have found out the problem is that the usb_parse_configuration
routine does not take account of descriptors which lie after the last
interface descriptor so the extral
