This seems to work well enough, we do not need the printout anymore.
--- linux-2.6.0-test5/drivers/usb/core/hub.c2003-08-24 14:24:54.0 -0700
+++ linux-2.6.0-test5-ka/drivers/usb/core/hub.c 2003-09-13 18:09:50.0 -0700
@@ -859,8 +859,7 @@
}
}
- /*
On Sat, 13 Sep 2003, Matthew Dharm wrote:
> On Thu, Sep 11, 2003 at 02:18:11PM -0400, Alan Stern wrote:
> > This looks like it's the manufacturer's fault. If they changed the
> > product enough so that it has different endpoints, they should have
> > changed the serial number as well.
>
> You
Olaf Hering wrote:
On Sat, Sep 13, David Brownell wrote:
+static char *
+dump_comm_descriptor(int fd, unsigned char *buf, char *indent, u_int16_t lang)
+ if (buf[3] & 0x01)
+ printf( "%scall management\n");
+ if (buf[3] & 0x02)
+
BÝZÝMLE ÇALIÞMAK ÝSTERMÝSÝNÝZ ?
DALTONS KÝMDÝR;
1996 yýlýnda Galatasaray Lisesi'nde okurken, gençlere yönelik organizasyon
sektöründeki arzýn talebi karþýlamadýðýný farkýna varan 4 genç giriþimcinin
yarattýklarý oluþum, ilk olarak kendi çevrelerindeki gençler için düzenledikleri
Uludað ve
Hi,
I'm back again.
the good news first: with usb-uhci this ooops doesn't appear.
But using uhci it still is there and happens like that.
Start the system with hotplug
switch on zaurus in the craddle
configure usb0 witha valid IP
take Zaurus out of the craddle
wait some time until it surely has e
On Sat, Sep 13, 2003 at 06:08:59PM +0200, Luca Risolia wrote:
> The patch is too long to be posted in a mailing list (SubmittingPatches, chapter 7)
>
> It is available at:
> http://go.lamarinapunto.com/downloads/patch
Again, if you want me to apply it, you are going to have to send it to
me throu
On Thu, Sep 11, 2003 at 02:18:11PM -0400, Alan Stern wrote:
> This looks like it's the manufacturer's fault. If they changed the
> product enough so that it has different endpoints, they should have
> changed the serial number as well.
You mean the revision number, not the serial number.
Matt
On Sat, Sep 13, David Brownell wrote:
> +static char *
> +dump_comm_descriptor(int fd, unsigned char *buf, char *indent, u_int16_t lang)
> + if (buf[3] & 0x01)
> + printf( "%scall management\n");
> + if (buf[3] & 0x02)
> + print
This is a patch that Thomas Sailer has already integrated into
his "usbutils" CVS tree (somewhere at tum.de I guess). I'm
forwarding it since the location of that tree is not widely
known, and since anyone using "lsusb" will benefit from at
least the control timeout and string read fixes. So it'd
The patch is too long to be posted in a mailing list (SubmittingPatches, chapter 7)
It is available at:
http://go.lamarinapunto.com/downloads/patch
Thanks.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://think
Alan Stern wrote:
On Sat, 13 Sep 2003, James Courtier-Dutton wrote:
I have a USB device with descriptor type 7. The current lsusb only
handles up to 5, So it just prints: -
unknown descriptor type: 07 21 07 88 13 ff 03
I have looked through all the usb docs I can find on the web, but no luck.
C
James Courtier-Dutton wrote:
I have a USB device with descriptor type 7. The current lsusb only
handles up to 5, So it just prints: -
unknown descriptor type: 07 21 07 88 13 ff 03
Descriptor type 0x21, length 0x07 ... :)
I'd guess that's a class-specific device descriptor.
See the spec for that c
Hi Stefan,
> Somebody at the Bluetooth Mailing List has made the interresting
> suggestion that the usb-hid mapper could do a fine job for the
> hci hid devices out there.
>
> He suggested to split off the hid stuff from the bus it's connecting.
>
> hid.o
> hid-usb.o
> hid-hci.o
>
>
> So befor
Hello List!
My experience with 2.6.0 is a nearly success story but I'm stuck with
printer fault.
I've installed lexmark drivers for Z35 - everything works with 2.4.20
kernel. But with 2.6.0 printer is strangely behaving - when I start
print job the printer powers on, gets paper, and starts t
On Sat, 13 Sep 2003, Tomita, Haruo wrote:
> Alan> This makes it look like the device isn't probed again after
> Alan> usbdevfs does the port reset.
>
> Is it that a problem is in a device?
No, it's a problem in Linux. The port-reset code is not fully developed.
> Alan> Yet another thing to w
On Sat, 13 Sep 2003, James Courtier-Dutton wrote:
> I have a USB device with descriptor type 7. The current lsusb only
> handles up to 5, So it just prints: -
> unknown descriptor type: 07 21 07 88 13 ff 03
>
> I have looked through all the usb docs I can find on the web, but no luck.
> Can anyo
I have a USB device with descriptor type 7. The current lsusb only
handles up to 5, So it just prints: -
unknown descriptor type: 07 21 07 88 13 ff 03
I have looked through all the usb docs I can find on the web, but no luck.
Can anyone point me to a document that enumerates the descriptor types,
Andries Brouwer wrote:
On Thu, Sep 11, 2003 at 11:41:31AM -0700, Greg KH wrote:
On Thu, Sep 11, 2003 at 05:33:25PM +0200, Ubaldi Fabio wrote:
Hi all,
I'm looking for a USB sniffer for linux; but i found in google only sniffer
USB for Windows (as usbsnoopy).
Does anybody know any USB sniffer sofw
On Friday 12 September 2003 18:35, Oliver Neukum wrote:
> > > No, I will not take a patch that adds any new BUG* calls to the usb
> > > code. I know you already have some in this driver, and that really is
> > > unacceptable. Device drivers should not shut down a system if they can
> > > help it
I am trying to make a logitech 4000 webcama work with my linux-box (
Debian testing and my own 2.4.21 kernel). I have a k7s5a motherboard
with two working EHCI ports, but I also have a Sitecom USB 1.1 / 2.0
card with a four port (OHCI and EHCI).
If I try to use the webcam with OHCI, then I can ge
This patch forward-ports manufacturer specific GPIO toggling from the
2.4 AX8817x code for usbnet. Some adapters need this toggling before
any any traffic can be sent.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
h
Hi all,
sorry that I botherd you with my bugreport yesterday.
Today I can not reprodice the ooops anymore. I tried for more then an hour
now.
What I did is to make a mrpropper kernel and now it works :-((
So I still don't know what the error was. MAybe it was one of the few "DON'T
DO"s in linux.
On Thu, 11 Sep 2003, Doug Maxey wrote:
> Alan,
>
> thanks. see below.
> Yet at some level, one is good, and the other not. Here are the
> relevant strings from /proc/bus/usb/devices
> # head -20 fd-*
> ==> fd-first <==
> T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh
LEFKE AVRUPA ÜNİVERSİTESİ
(KIBRIS BİLİM VAKFI)
YÖK tarafından tanınan, Avrupa ve Amerika'da geçerli diplomaya en kaliteli
ve en uygun harçlarla sahip olma olanağı ...
ÖSS Sınavından 185 ve üzeri ham puan almış öğrenciler 4 yıllık lisans
programlarına, 160 ve üzer
24 matches
Mail list logo
