I meet same message as below today in my system.
(B
(BTango:/usr/local/bin# ./vidcat -b -s 320x240 -f ppm
(Bov511.c: Forcing packet size to 769
(Bvid 1
(Bvid 2
(Bvid 3 get_image
(Bget 1
(Bget 3
(Bbstat =a hp->itl0_len=780
(B
(Bbstat =a hp->itl0_len=780
(Bbstat =8 hp->itl0_len=780
(B
(
David Brownell wrote:
On Saturday 28 August 2004 1:23 pm, Darren Marshall wrote:
This suggests a chip bug to me; there were others in
AMD-756 OHCI. Does it work if you disable CONFIG_PM?
Disabling CONFIG_PM improved things slightly, I can
now do 4 or 5 "cats" before a hang occurs
> 2.6.9-rc1 before anything else.
Ok - now things work a little bit better: The
Sep 2 22:47:26 tequila kernel: usb 1-1.3: new full speed USB device using
address 9
Sep 2 22:47:26 tequila kernel: usb 1-1.3: device not accepting address 9,
uerror -71
Sep 2 22:47:26 tequila kernel: usb 1-1.3:
Hi Steve,
> I don't want to spam the list with this large sample file. It was captured
> at work with a Catalyst SBAE 3 analyzer. It contains the complete
> enumeration of my mouse (ie low speed) on my XP Home laptop. It has a lot
> of data and this text export file is hard to read, but it should
I have exactly the same problem with my Motorola V220 and a friend who have
the Motorola C650 have another problem : the kernel don't recognize the
cellphone as an USB driver : he doesn't have these lines in the logs !!!
I think USB mechanisms on Motorola cellphones are bugged and we should devel
Messages like this, devoted to programming issues, generally belong on the
linux-usb-devel mailing list. Relatively few developers follow
linux-usb-users.
Alan Stern
P.S.: Have you checked to see whether this problem has already been
resolved in 2.6.9-rc1?
-- Forwarded message -
On Sat, 4 Sep 2004, Laurent Pinchart wrote:
> Thanks a lot for the capture file. Windows XP seems to enumerate low speed
> devices by performing the following requests in sequence:
>
> GET_DESCRIPTOR(DEVICE, 18 bytes)
> SET_ADDRESS
> GET_DESCRIPTOR(DEVICE, 18 bytes)
> GET_DESCRIPTOR(CONFIGURATIO
Hi Alan,
> That's not right -- at least, it's not right for the first copy of the
> trace that Steve sent out. (I didn't look at the second copy so maybe
> it's different.) In the trace I saw, the first Get-Device-Descriptor asks
> for 64 bytes, not 18. Also, note that there's a port reset in b
On Sat, 4 Sep 2004, Laurent Pinchart wrote:
> Hi Alan,
>
> > That's not right -- at least, it's not right for the first copy of the
> > trace that Steve sent out. (I didn't look at the second copy so maybe
> > it's different.) In the trace I saw, the first Get-Device-Descriptor asks
> > for 64
> Maybe we're talking about different traces. I'm referring to the trace
> for the Zoom modem (a low-speed device according to Steve), as attached to
Yes we are. The Zoom modem is a USB 1.0 device according to Steve, but he
didn't mention if it is a low-speed or high-speed device (well if he did
Merhaba,
MULTI-GSM KARTLARLA TEK TELEFONDA "AYNI ANDA 4 HAT AKTiF"
Tek cep telefonu uzerinde "ayni anda 4 hat aktif" olabilir.
Dilediginiz hattan cagri alabilir, yine dilediginiz hattan cikis yaparak
baskalarini arayabilirsiniz. Uygulama fiyati: 50 EURO + KDV'dir.
AYCELL, ARIA, AVEA VE TURKCELL
[EMAIL PROTECTED] wrote:
Yes, but for reading/writing they should be the same.
But it's definitely different behavior. With ACM I was able to
establish a connection (data loss, due to no flow control, but that's expected),
and I could send both ways. Without ACM, I _never_ saw this. The gadget->hos
On Saturday 04 September 2004 9:00 am, Alan Stern wrote:
> Messages like this, devoted to programming issues, generally belong on the
> linux-usb-devel mailing list. Relatively few developers follow
> linux-usb-users.
>
> Alan Stern
>
> P.S.: Have you checked to see whether this problem has al
The usb-storage driver 'fixes up' the INQUIRY data returned by a device so
that it reads SCSI rev 2 by intercepting the data in-flight. This was done
to make various SCSI drivers (sd, sr, etc.) work with the device.
However, this technique also has the unfortunate side-effect that nobody
can see
On Sat, 4 Sep 2004, Laurent Pinchart wrote:
> > Maybe we're talking about different traces. I'm referring to the trace
> > for the Zoom modem (a low-speed device according to Steve), as attached to
>
> Yes we are. The Zoom modem is a USB 1.0 device according to Steve, but he
> didn't mention if
Hi Alan and Laurent,
It really is unfair of me to be sending traces from entirely different
analyzers. But I have to deal with the equipment I have at any one site. So
here I will send you two kitty traces of the mouse and the zoom modem
enumerations. I edited the html to try and get them small
Hi Laurent,
And then to keep things interesting, I mistakenly edited too much out of the
the zoom modem trace.
the following would have happened somewhere after frame 1540. It is a get
device descriptor setup packet.
f=12001 sync 13030 SOF(xa5) frame 962 crc5 0x7 f=0
f=05123 sync 13038 SETUP(x2
17 matches
Mail list logo
