=02(comm.) Sub=02 Prot=01 Driver=cdc_acm
E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=128ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> -Original Message-
> From: Greg Lee [
> This configuration descriptor is meaningless. It looks like
> the device didn't send the data at all. What do you see in
> /proc/bus/usb/devices?
>
> Alan Stern
The output from /proc/bus/usb/devices is:
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=02(
> I don't know what's going on with 2.4, but I can answer your
> first question. USB_CONFIG_ATT_WAKEUP means that the
> configuration supports Remote Wakeup requests: The device can
> be set to issue a wakeup request if something interesting
> happens while it is suspended.
>
> (Note that the
What is the significance of the bmAttributes USB_CONFIG_ATT_WAKEUP bit? I
recently received a firmware update to one of the devices I use and now it
does not work with my 2.4.19 and 2.4.31 based embedded targets, however, it
does work on a 2.6.12 based PC system.
The symptom that I am seeing on m
> >900 K bits/sec or 900 K bytes/sec?
> >
> >Greg
> >
> That would be bytes :)
>
> /Brian
Thanks. 900 K bits/sec === bad, 900 K bytes/sec === good!
Greg
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22
> I wrote my own user space driver which has achieved write
> speeds of 900k/s.
900 K bits/sec or 900 K bytes/sec?
Greg
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Dev
> > Currently I've made a preliminary firmware for implementing the
> > CDC-ACM interface, however as Pavel kindly pointed out for me,
> > currently only 64Kbyte/sec is achieveable with this driver. I've read
> > the archives and from the discussions, I suspect that this is
> > connected to th
> Uh-oh. I sense a user of 2.4 kernel here.
>
> On 2.4, you still can match I/O ports and find which
> controller is where on the PCI bus, by reading /proc/ioports
> and /proc/bus/usb/devices.
> But it's icky. Why don't you just migrate to 2.6 and get /sys?
Your senses are well tuned (Linux ver
> > Is there an ioctl that I can call on a file handle that will allow me
> > to map from the device to the underlying hardware type?
> > Any other suggestions?
>
> I'm sure there's a way to get this information just by
> looking at paths and symlinks in /sys
I assume you mean /proc/sys? I
> > Is there an ioctl that I can call on a file handle that will allow me
> > to map from the device to the underlying hardware type? Any other
suggestions?
>
> I'm sure there's a way to get this information just by looking at paths
and symlinks in /sys
I assume you mean /proc/sys? I have looke
.
Greg Lee
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http
OTECTED]; [EMAIL PROTECTED]
> Cc: linux-usb-devel@lists.sourceforge.net
> Subject: Usb serial with power ON/OFF problem
>
>
>
> Hi Greg/Lee,
>
> On this problem one more scenario, we tried to do switch off
> mobile manually without AT+CFUN=0, with this we are not
> g
> What oops do you get? On a recent 2.6 kernel?
The kernel is 2.6.11.7. It's not a full kernel Oops, rather a NULL pointer
dereference in the kernel. The phone is recognized as an ACM device under
2.6 kernels (not usbserial). I have a copy of all of the console output
from boot to the error if
> And yes, if a device goes away with a open file descriptor,
> on 2.6, you will get a new usb device node for when the
> device shows back up. It will not reconnect to the same open
> file descriptor, sorry.
That is not a problem, we re-open anyways. But if we write on the old file
descripto
to reopen the port.
While I do have a workaround, occasionally my software is not able to
account for this case and I do end up with kernel OPPS which are caught by
the system watchdog. It "would be nice" if I did not have to account for
this problem. I have seen a couple of others on t
15 matches
Mail list logo
