> From: Wolfgang Mües <[EMAIL PROTECTED]>
> Date: Mon, 24 Dec 2001 15:40:04 +0100
> > p* can be removed (I don't like it either), but why the _t? It's a clear
> > marking that this is a defined type and it makes the code a tiny bit more
> > readable. And usb.h is not the only one using that style
> > The absolutely worst happens when someone attempts to re-type
> > a _t over a large body of existing code, for instance inexpirienced
> > coders keep proposing to change kdev_t into a pointer.
>
> I'd hardly call Andries inexperienced, and in fact he did precisely that
> a long time ago but t
> Here's a patch against 2.5.2-pre7 that allows the USB core to control
> the module usage count of the USB driver modules.
Looks good, but one question - was it oopsable before?
-- Pete
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at
> Here is part of the stack trace from the oops/panic in my first
> message about this problem:
>
> >>EIP; c012ad65<=
> Trace; c4817ee4 <[usbcore]usb_destroy_configuration+104/210>
> Trace; c48171e2 <[usbcore]usb_free_dev+22/50>
> Trace; c48288b5 <[usb-uhci
> From: "victor saldarriaga" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Date: Wed, 9 Jan 2002 13:10:09 -0500
> A manufacturer of ISDN terminal adapters needs a kernel developer for one of
> its usb TA's.
> The manufacturer would supply you with firmware and chipset specs, a unit,
> and win32
On Sun, Jan 13, 2002 at 10:24:55AM -0800, Greg KH wrote:
> On Sun, Jan 13, 2002 at 12:58:45PM +0100, Oliver Neukum wrote:
> > 2) skel_write checks for -EINPROGRESS. This is a race.
>
> Yes, but it's a race that _so_ many different drivers have that I don't
> consider it a driver problem. It sho
> From: Thomas Davis <[EMAIL PROTECTED]>
> To: linux-usb-devel <[EMAIL PROTECTED]>
> Date: Fri, 25 Jan 2002 10:11:28 -0800
> PCI: Found IRQ 10 for device 00:1f.2
> IRQ routing conflict for 00:1f.2, have irq 9, want irq 10
This is a material for Manfred Spraul.
Did you try to enable ACPI and see
Hello,
I've got a stupid question for Matt or someone with a SanDisk
reader: what is the model suffix for CF reader (as opposed
to MemorySpit, DumbMedia, etc.)? I have couple of SDDR-31
bugs assigned and I am trying to purchase the hardware.
Our preferred supplier carries only "SDDR-31-07", and I
> From: Lars Doelle <[EMAIL PROTECTED]>
> Date: Mon, 11 Feb 2002 01:08:29 +0100
>[...]
> There is some Linux support for IEEE 1284.4 underway, but until this is
> working and integrated, i think one should better disable accepting these
> protocols, as it would never work in the moment.
David
> From: Lars Doelle <[EMAIL PROTECTED]>
> Date: Tue, 12 Feb 2002 15:48:53 +0100
> So my suggestion is to go this way and put a vendor/product list into
> printer.c indicating when a 7/1/3 should really be picked and call the device
> then /dev/usb/hpoj, so that you can pick it up with your user
> From: Brad Hards <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>, "'Greg KH'" <[EMAIL PROTECTED]>
> Date: Thu, 14 Feb 2002 07:56:37 +1100
> > Yes, I'm referring to 7-29. I don't have the source handy and my
> > "information" is anecdotal. It might be a problem with a particular
> > implementati
> Date: Wed, 20 Feb 2002 00:36:14 +0100 (CET)
> From: Martin Diehl <[EMAIL PROTECTED]>
> Johannes, Pete - if it's ok for you I'd like to suggest this could go into
> early 2.4.19-pre series.
I do not mind. If I remember JE's argument right, he did not
like how long it takes to renumber a bus wit
> From: "Sean J Power" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Date: Fri, 8 Mar 2002 12:45:51 -0500
> I am having issues loading USB, the relevent excerpt of dmesg follows...
>
> PCI: Enabling device 02:0a.0 (0014 -> 0016)
> PCI: Found IRQ 5 for device 02:0a.0
> PCI: Sharing IRQ 5 with 0
> From: David Brownell <[EMAIL PROTECTED]>
> Date: Fri, 08 Mar 2002 10:10:12 -0800
> You might try increasing the smm_timeout in hc_reset()
> in drivers/usb/usb-ohci.c to see if the BIOS/SMM code is
> just painfully slow. Or tweaking the BIOS settings to make
> it forget (or learn?) about USB.
Guys,
The patch came about as offshot of my anti-usbkbd crusade.
(Or shall I say Vojtech's anti-usbkbd policies? :)
This patch is truly a kludge, but it seems to work.
Some hardware by a certain company called "ATEN" crashes
if GET_REPORT is sent. I tried to modify our GET_REPORT, but
it seems t
> Date: Mon, 11 Mar 2002 09:51:14 -0800
> From: Greg KH <[EMAIL PROTECTED]>
> > it seems that nothing helps. So, I simply switched GET_REPORT off.
> > It works for the piece of junk that Red Hat bought for my testing,
> > and I got several "thank you" notes since we shipped the patch.
> A number
> From: [EMAIL PROTECTED]
> Date: Mon, 25 Mar 2002 12:19:47 -0800
> % cp /mnt/cf/dc265_01/*.jpg /tmp
> top kernel: usb_control/bulk_msg: timeout
> top kernel: usb-uhci.c: interrupt, status 3, frame# 571
>
> It had copied about 10MBs of data when the timeout occured.
Brian, I hear complaints abo
Hello,
would someone mind sparing a quick glance, and tell me if this looks
familiar. User uses pl2303, and after a while it hangs. If he
pulls USB cable, system oopses (2.4.9+).
pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.7
.. long time before hang
usb-uhci.c: ENXIO c04
> Why not? What's wrong with 2.5? In fact, that's where all new work
> should be going on right now, not the 2.4 tree.
The pressure to stay with stable kernels is simply too strong.
If you develop for unstable series, you must track a quickly
changing codebase, and this saps the time and effort
> From: Guest section DW <[EMAIL PROTECTED]>
> Date: Thu, 11 Apr 2002 02:57:14 +0200
> > This patch against the 2.5.8-pre3 kernel adds /proc/
>
> Totally unrelated, but this reminds me:
> The unreadable /proc/bus/usb always annoyed me, and I added a
> blank line, separating entries. Hope that no
was included on the list of recipients.
--
From: Linus Torvalds <[EMAIL PROTECTED]>
To: Pete Zaitcev <[EMAIL PROTECTED]>
cc: Johannes Erdfelt <[EMAIL PROTECTED]>
Subject: Re: About atomicity of set_bit
In-Reply-To: <[EMAIL PR
> From: "Ben Simkin" <[EMAIL PROTECTED]>
> Date: Mon, 20 May 2002 15:32:20 +1000
> I would like to ask if it were possible to setup TCP/IP over USB
> (without an ethernet USB chip, or whatever they use)...
>
> You see, I want to setup a 2-way satellite system, and AFAIK, the
> "modem" connects t
> From: [EMAIL PROTECTED]
> Date: Tue, 21 May 2002 18:37:08 +0200 (MEST)
> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=05e3 ProdID=000a Rev= 0.00
> C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr= 48mA
> I: If#= 0
Guys,
I've got a customer who complains about lockups with a new
version of Sony's MS controller. Unfortunately, he resists my
mind control powers when I try to type keys on his laptop
remotely. :) Did anyone hear of someone with this problem
who can get me stack snapshots to track the lockup?
-
> From: Oliver Neukum <[EMAIL PROTECTED]>
> Date: Mon, 10 Jun 2002 20:46:17 +0200
> > See my other post ... start of next structure is controlled by a
> > structure level alignment attribute (forcing extra padding at end),
> > while start of next _member_ is controlled by member level attributes.
Matt & Greg,
would you be so kind to take this:
--- linux-2.5.54/drivers/usb/storage/unusual_devs.h 2002-12-15 18:08:14.0
-0800
+++ linux-2.5.54-p3/drivers/usb/storage/unusual_devs.h 2003-01-24 14:50:25.0
+-0800
@@ -121,12 +121,11 @@
"LS-120 Camera",
> From: "Janne Pikkarainen" <[EMAIL PROTECTED]>
> Date: Wed, 29 Jan 2003 21:19:43 +0200 (EET)
> This is the first patch I ever try to submit, so please forgive me if I'm
> doing something terribly wrong. :-) Anyway, I have a 128 MB USB Memory Key
> by IBM, and without my patch it doesn't work at a
> From: Christopher Li <[EMAIL PROTECTED]>
> Date: Wed, 5 Feb 2003 07:26:45 -0800
> Any comment?
> /* min 8 byte setup packet, max arbitrary */
> - if (uurb.buffer_length < 8 || uurb.buffer_length > PAGE_SIZE)
> + if (uurb.buffer_length < 8 || (uurb.buffer_le
> From: Dmitri <[EMAIL PROTECTED]>
> Date: 14 Feb 2003 09:03:41 -0800
> > What do others think? Should we just remove this?
>
> How many developers have time for IRC in first place? It is too
> demanding on one's attention, IMO.
>
> Dmitri
Greg is on IRC often. It can be done, with proper tools
> From: Ian Molton <[EMAIL PROTECTED]>
> Date: Thu, 6 Mar 2003 18:14:56 +
> I need a cheap and cheerful ISA USB card.
Generally speaking, there is no such animal (this also explains
why PCMCIA USB adapters do not exist). Phillips makes a silicon
which potentially can be used (isp1601 or some
> From: Christopher Li <[EMAIL PROTECTED]>
> Date: Thu, 6 Mar 2003 11:37:21 -0800
> > Generally speaking, there is no such animal (this also explains
> > why PCMCIA USB adapters do not exist). Phillips makes a silicon
>
> I haven't see an ISA usb card. But there are tons of pcmcia
> usb card out
>[...]
> OHCI is a silicon which works with a high-speed, DMA master bus.
> Adaptations of the IP block to ARM exist, but primarily it is
> sold as a PCI master. How are you going to hook it to ISA?
BTW, I'm not saying it cannot be done. If you are willing
to do a little bit of design, you can use
> From: Oliver Neukum <[EMAIL PROTECTED]>
> Date: Wed, 19 Mar 2003 21:44:10 +0100
> +#define __wait_event_timeout(wq, condition, ret) \
> + if (condition) \
> + break;
> From: Oliver Neukum <[EMAIL PROTECTED]>
> Date: Wed, 19 Mar 2003 22:13:07 +0100
> > > From: Oliver Neukum <[EMAIL PROTECTED]>
> > > Date: Wed, 19 Mar 2003 21:44:10 +0100
> > >
> > > +#define __wait_event_timeout(wq, condition, ret) \
> > > + if (condition)
Speaking of Keyspan, one gentleman complains of serial stream
corruption with a 2.4.21-pre4 based kernel and 49W. RH bz#86590.
I have no idea what to do about it, perhaps I should buy
myself one of those things.
-- Pete
---
This SF.net email is
> From: David Brownell <[EMAIL PROTECTED]>
> Date: Wed, 02 Apr 2003 07:52:05 -0800
> I got a report of a problem with a high speed CD-ROM that
> could be reproduced by a simple loop:
>
>dd if=/dev/scd0 of=cdrom.iso
>cmp /dev/scd0 cdrom.iso
>
> The failure was reported on 2.4, so I wanted
> Date: Thu, 5 Jun 2003 02:15:06 -0400
> From: Johannes Erdfelt <[EMAIL PROTECTED]>
> I didn't see this on x86, but apparentely others have looking at the
> RedHat 9 kernel sources. (RedHat bugzilla #81091)
> Pete, could you give this patch a shot for the problem you found in that
> bug? I'm prett
Strangely, I didn't see this on the list, looked poorly? Anyway,
here's the deal:
kernel BUG at sched.c:999!
EIP is at schedule [kernel] 0x2aa (2.4.20-13.9)
eax: 0001 ebx: c3ad8c74 ecx: c0349d64 edx: c0349d5c
esi: c0348000 edi: c3ad8c7c ebp: c0349d54 esp: c0349d44
ds: 0068 es: 00
> From: "Christopher Hoover" <[EMAIL PROTECTED]>
> Date: Fri, 6 Jun 2003 10:58:50 -0700
> > So all I/O buffers _must_ be allocated using kmalloc()
>
> Use GFP_DMA flag on the kmalloc() call, too, whenever possible.
> This will help avoid bounce buffering on some systems.
Wrong!!! Where did yo
I hear this from people who do CONFIG_HID_INPUT=m:
: USB HID v1.10 Mouse [Logitech USB Mouse] on usb1:3.0
See that funny colon in the begining? I think this should be
the patch, but I'm not sure how to reproduce and test.
-- Pete
--- linux-2.4.21-rc2-ac2/drivers/usb/hid.h 2003-04-24 11:42:
> From: Jackson Chan <[EMAIL PROTECTED]>
> Date: Mon, 9 Jun 2003 11:57:36 -0600
> > I have been trying to solve this problem for a long time and any help
> > would be greatly appreciated.
In such case you would be well advised to stop being a jerk
and cross-post the same stupid question everywher
by Frode Isaksen and
> improved by Pete Zaitcev. Pete Zaitcev has applied this patch as an
> errata fix for the RedHat 9.0 kernel.
I only added when Alan looked and said he'd add it to -ac, he
just forgot the usb-uhci side. He has usb-ohci fix since -rc2-ac2.
It's n
> From: Tuukka Toivonen <[EMAIL PROTECTED]>
> Date: Mon, 23 Jun 2003 20:39:33 +0300 (EEST)
> If usb_disconnect() can happen while already executing in open(), and if
> the former frees the data structures used by the driver, then the latter
> call might continue working with already freed memory r
> Date: Mon, 23 Jun 2003 21:11:35 +0300 (EEST)
> From: Tuukka Toivonen <[EMAIL PROTECTED]>
> >> If usb_disconnect() can happen while already executing in open(), and if
> >> the former frees the data structures used by the driver, then the latter
> >> call might continue working with already freed
> From: Greg KH <[EMAIL PROTECTED]>
> Date: Mon, 23 Jun 2003 15:45:38 -0700
> What problem does this cause with these drivers (the lego and visor
> one.)?
The usb-uhci was an oops with a NULL pointer. In ohci case it wasn't
an oops, but something didn't work, I forgot the symptom.
https://bugzil
> From: David Brownell <[EMAIL PROTECTED]>
> Date: Thu, 17 Jul 2003 15:38:11 -0700
> >>A bug has turned up in the UHCI driver. Briefly, when an URB completes,
> >>uhci_transfer_result() doesn't store the status in urb->status but only in
> >>urbp->status. urb->status is set just before calling h
> Date: Thu, 17 Jul 2003 18:39:38 -0700
> From: David Brownell <[EMAIL PROTECTED]>
> > So the completion uses an extra field to indicate that
> > urb was released by HC driver to the uppper level.
> > It's not an explicit field, it's an extra field.
>
> This really makes no sense to me. There's
> Date: Thu, 17 Jul 2003 23:01:42 -0400 (EDT)
> From: Alan Stern <[EMAIL PROTECTED]>
> [...] But a properly-written driver won't
> touch the URB _at all_ once it has been submitted until the completion
> callback.
I said the same. It cannot look at the urb->status.
-- Pete
---
> Date: Thu, 5 Jun 2003 02:15:06 -0400
> From: Johannes Erdfelt <[EMAIL PROTECTED]>
> The fix is to just move setting hub->children to later in the
> enumeration process. This way usbdevfs_read_super won't see the device
> before it has been through the usbdevfs_add_device path.
>
> I didn't see
> From: Luke Hutchison <[EMAIL PROTECTED]>
> Date: 22 Jun 2002 14:54:09 -0600
> Here is some output from /var/log/messages from when the problem
Can you send me more of it, unedited? "some" sounds suspicious.
Personally, I suspect that hid races itself. Of course, it's
a check potshot at Vojtec
Petko:
The following check seems redundant:
static void * rtl8150_probe(struct usb_device *udev, unsigned int ifnum,
const struct usb_device_id *id)
{
..
if ((udev->descriptor.idVendor != VENDOR_ID_REALTEK) ||
(udev->descriptor.idProduct != PRO
> From: Petko Manolov <[EMAIL PROTECTED]>
> Date: Mon, 22 Jul 2002 21:51:39 -0700 (PDT)
> Do you by any chance know the vendor and device id of that Melco device?
The patch was attached to the bug report. This part was sane:
@@ -72,11 +72,15 @@
/* Define these values to match your device */
> From: "Randy.Dunlap" <[EMAIL PROTECTED]>
> Date: Fri, 27 Sep 2002 22:45:45 -0700
> --- ./drivers/usb/core/usb.c.2539 Fri Sep 27 14:49:55 2002
> +++ ./drivers/usb/core/usb.c Fri Sep 27 22:35:30 2002
> +int nousb; /* Disable USB when built into kernel image */
> +
> From: David Brownell <[EMAIL PROTECTED]>
> Date: Tue, 01 Oct 2002 17:20:02 -0700
> Yes, it looks like hub.c down()s a semaphore while holding
> its own spinlock... it doesn't always cause this message.
> The comment says it never blocks, but... shouldn't this change?
>
> - Dave
Crap, it's my
> From: Douglas Roberts <[EMAIL PROTECTED]>
> Date: Wed, 09 Oct 2002 10:58:04 -0600
> lilly:[~/radio/driver]% ./evtest /dev/input/event0
> evtest: No such device
Just to make it all clear, do "strace evtest /dev/input/event0",
please. I suspect it fails in open, but I do not know for sure.
-- P
> From: Chris Cheney <[EMAIL PROTECTED]>
> Date: Thu, 10 Oct 2002 22:33:31 -0500
> Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
It needs down() replaced with if (down_trylock()) BUG();
Posslibly fixed already in Greg's tree.
-- Pete
> Date: Wed, 23 Oct 2002 13:57:49 -0700
> From: David Brownell <[EMAIL PROTECTED]>
> > Out of the blue an ALi engineer contacted me and offered a fix for
> > lockups in IBM i-series laptops (RH Bugzilla #50225). I would
> > really appreciate if someone ran it on their _regular_ ohci
> > to ensure
> Haven't tried that patch yet, do you have a 2.5 version?
I am wondering if the 2.5 might work as it is on i1200/i1300.
It preserves the HCFS field.
I'll get back to it when Red Hat ships a 2.6 based release.
-- Pete
---
This sf.net email is
Out of the blue an ALi engineer contacted me and offered a fix for
lockups in IBM i-series laptops (RH Bugzilla #50225). I would
really appreciate if someone ran it on their _regular_ ohci
to ensure that it does not break non-ALi silicon. Both 2.4 and 2.5
are the same (approximately), the patch is
> From: Robert Love <[EMAIL PROTECTED]>
> Date: 05 Nov 2002 14:26:08 -0500
Just in case nobody else answers:
> I believe the Windows driver for both has the ability to read the
> battery strength. Greg said the information may be encoded in the HID
> information and maybe someone on this list ca
> From: Brad Hards <[EMAIL PROTECTED]>
> Date: Wed, 6 Nov 2002 16:48:08 +1100
> > 2. Ask logitech - I have a contact that might work.
> Logitech says:
>
> Yes, the battery status information comes from a vendor command.
>[...]
This is wonderful, however I am concerned that hiddev cannot be
used
> From: Michal Cihar <[EMAIL PROTECTED]>
> Date: Wed, 06 Nov 2002 09:59:55 +0100
> I was having problems with my usb device, that failed with "hub.c:
> connect-debounce failed, port N disabled". [...]
> Problems seems to be in clearing USB_PORT_STAT_CONNECTION flag after it
> is being read once
> Date: Wed, 6 Nov 2002 18:24:31 -0500
> From: Johannes Erdfelt <[EMAIL PROTECTED]>
> > Interestingly, JE was up in arms against a simple 400ms delay
> > in this place, which always worked before. Now, someone came
> > with the debonce routine and lo and behold: it always delays
> > for the same 4
> From: Todd Lyons <[EMAIL PROTECTED]>
> Date: Thu, 7 Nov 2002 14:38:51 -0800
> The only state I forsee is _slow_. A flat out balls to the wall copy
> from a local filesystem to a usb filesystem across a USB 1.1 bus
> proceeds at a rate of about 1 MB per minute.
That's about 50 times slower than
> From: Oliver Neukum <[EMAIL PROTECTED]>
> Date: Thu, 7 Nov 2002 23:42:34 +0100
> if we wrote some bytes we need to admit it even if we'd otherwise return
> -EAGAIN. Any news on Linus' printing problem incidentally?
> if (!usblp->wcomplete) {
> barrier();
>
> From: "Randy.Dunlap" <[EMAIL PROTECTED]>
> Date: Fri, 15 Nov 2002 08:40:36 -0800 (PST)
> | > Yes, I think you are right.
> | > To test your idea, I moved the initialization
> | >
> | > init_MUTEX(&usb_bus_list_lock);
> | >
> | > from usb_init() to just before the call to usb_scan_devices
> Date: Fri, 15 Nov 2002 14:38:05 -0500 (EST)
> From: Duncan Haldane <[EMAIL PROTECTED]>
> >| Also, the order in which cpia and usbcore are listed in the Makefile
> >| is significant, it determines the order in which do_initcalls
> >| calls them in case of them being 'y'.
> >
> > The case is both
> From: "Tvrtko A. Ursulin" <[EMAIL PROTECTED]>
> Date: Sat, 7 Dec 2002 17:27:52 +0100
> So I wonder, what this patch does? Should it be submitted to the main tree?
The patch you quoted defeats the whole purpose
of debouncing, shortcutting the loop. The loop is broken as
it is in 2.4.20, so killi
> Please try the attached patch, and also send me the output
> of your dmesg, taken after the test. There is a special printout
> there to diagnose the problem.
Sorry for answering my own post, I forgot one thing. I would like
several unrelated people to try the patch, not only Tvertko.
When you
Hi, Greg,
I was getting annoyed that nobody fixed the obviously broken
debounce loop, so I had to go ahead and fix that.
Please add it to 2.5.
-- Pete
--- linux-2.5.50/drivers/usb/core/hub.c 2002-11-17 20:29:45.0 -0800
+++ linux-2.5.50-sparc/drivers/usb/core/hub.c 2002-12-09 09:44:30.
> From: Oliver Neukum <[EMAIL PROTECTED]>
> Date: Wed, 18 Dec 2002 01:20:56 +0100
> unknown ioctls return -ENOTTY and nothing else.
> - return -ENOIOCTLCMD;
> + return -ENOTTY;
Does it pop to userland in that code? Alan says it can be used
under controlled conditions.
> A
> From: shino korah <[EMAIL PROTECTED]>
> Date: Thu, 19 Dec 2002 15:59:14 -0800 (PST)
> I have a USB device doing DMA.I'm using bulk read and
> write.If I need to write e.g. 200k bytes of data.
> Can I create the urb->transfer_buffer to 200k and put
> the data in there? Or Am I restricted to only
Do you guys think Dmitri had anything particular in mind when
he dropped this static?
--- linux-2.4.21-pre1/drivers/usb/ibmcam.c 2002-08-02 17:39:45.0 -0700
+++ linux-2.4.21-pre1-sparc/drivers/usb/ibmcam.c2002-12-19 19:43:28.0
+-0800
@@ -87,7 +87,7 @@
} ibmcam_t;
#d
Greg, would you mind adding this trivial patchlet, please.
IIRC, Dimitri approved, at least for 2.5.
--- linux-2.4.21-pre3-nip/drivers/usb/ibmcam.c 2003-01-06 17:36:50.0 -0800
+++ linux-2.4.21-pre3/drivers/usb/ibmcam.c 2003-01-06 17:25:15.0 -0800
@@ -87,7 +87,7 @@
} ibmcam_t
> | --- linux-2.4.21-pre3-nip/drivers/usb/ibmcam.c 2003-01-06 17:36:50.0
>-0800
> | +++ linux-2.4.21-pre3/drivers/usb/ibmcam.c 2003-01-06 17:25:15.0 -0800
> | -static struct usbvideo *cams = NULL;
> | +struct usbvideo *cams = NULL;
>
> That's going in the wrong/reverse direc
Add a couple of supported devices into the help message.
It's a long story... I promised this comment changed to a user long ago,
so I'd like to have that promise kept. In reality though, nobody is
likely to read this anyway.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
---
Remove the silly trailing backslash.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- linux-2.6.17-rc2/drivers/usb/serial/pl2303.c2006-04-23
21:06:18.0 -0700
+++ linux-2.6.17-rc2-lem/drivers/usb/serial/pl2303.c2006-05-22
21:31:15.0 -0700
@@ -599,7
Hi, Greg:
I looked at RMK's UART infrastructure and it seemed a little too
fine-grained to me. It does not seem like a good match for things
like edgeport and keyspan. So, my enthusiasm about "us" has diminished.
Also, remember what kind of pain in the butt was the coexistence
of usb-storage and
Wait for the scheduled work to finish before freeing memory, prevent oops.
http://bugzilla.kernel.org/show_bug.cgi?id=6596
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- linux-2.6.17-rc2/drivers/usb/serial/usb-serial.c2006-04-23
21:06:18.0 -0700
+++ linux-2.6.17-rc2-lem/d
On Wed, 24 May 2006 11:26:37 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> > Nup, here it sometimes takes 1min to get it going again.
>
> How can you tell? By watching an LED?
> The place you should modify is in drivers/usb/storage/transport.c. Near
> the end of the usb_stor_invoke_tran
On Wed, 24 May 2006 21:32:46 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> output, not very easy to interpret. But it shouldn't be hard to find the
> sections where the 29 timeouts and resets occur, just by searching for
> large jumps in the timestamps.
I suggest looking for -104 (unlink)
On Thu, 25 May 2006 02:15:37 -0500, Al Borchers <[EMAIL PROTECTED]> wrote:
> One minor thing, I would prefer "sizeof(string)" to "30", but
> it is not crucial.
Done in my tree. I'll either send a follow-up to Greg or resend, depending
on the acceptance.
-- Pete
Remove some silly messages and cast in stone "temporary" messages which
we keep around. Also, I am hesitant to remove the initialization retries
without having the hardware to test (anyone who was at KS04 has a spare?)
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- linux-2
e path of no return. With that fix in place, we do
not need to test GENHD_FL_UP.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
---
Greg, this is something to merge after 2.6.17, please. Not urgent.
--- linux-2.6.17-rc5-gregkh/drivers/block/ub.c 2006-05-25 18:45:10.0
-0700
+++ li
On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> usb 1-4.5.7: USB disconnect, address 79
> [ cut here ]
> kernel BUG at kernel/workqueue.c:110!
Please let me know if this helps:
--- linux-2.6.17-rc2/drivers/usb/serial/usb-serial.c2006-04
On Tue, 30 May 2006 19:48:21 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
+0100
> +++ linux-2.6.17-rc4.test/drivers/usb/serial/ipaq.c 2006-05-30
> 19:41:19.0 +0200
> @@ -692,6 +694,7 @@ static void ipaq_close(struct usb_serial
> struct ipaq_private *priv = usb_get_serial_po
On Fri, 02 Jun 2006 00:03:06 -0300, "Luiz Fernando N.Capitulino" <[EMAIL
PROTECTED]> wrote:
This looks interesting, although I do not know if it buys us much.
The code seems sane at first view. The private lock inside pl2303
saves you from the most obvious races.
> The tests I've done so far we
On Fri, 2 Jun 2006 11:39:05 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> Also it looks like either usbmon has dropped a lot of lines or you have
> edited them out of the log.
The '1t' pseudo file provides the counters, if anyone is interested.
Most of the time, the main reason for dropp
On Fri, 2 Jun 2006 13:50:14 -0700, Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 02, 2006 at 12:03:14AM -0300, Luiz Fernando N.Capitulino wrote:
> > 2. The new pl2303's set_termios() can (still) sleep. Serial Core's
> > documentation says that that method must not sleep, but I couldn't f
On Fri, 02 Jun 2006 11:03:29 +0100, David Woodhouse <[EMAIL PROTECTED]> wrote:
> On Thu, 2006-06-01 at 23:48 -0700, Pete Zaitcev wrote:
> >
> > > The tests I've done so far weren't anything serious: as the mobile
> > > supports a
> > > AT co
On Fri, 2 Jun 2006 15:25:39 -0700, "Vivek Dharmadhikari" <[EMAIL PROTECTED]>
wrote:
> >The '1t' pseudo file provides the counters, if anyone is interested
>
> What are these counters ?
> How different are these counters from the current format of usbmon log ?
> Do the file usbmon.txt contains i
On Sat, 03 Jun 2006 02:17:48 -0500, Paul Serice <[EMAIL PROTECTED]> wrote:
> The workaround in commit f7201c3dcd7799f2aa3d6ec427b194225360ecee
> broke. The work around requires memory for DMA transfers for some
> NVidia EHCI controllers to be below 2GB, but recent changes have
> caused the DMA me
On Sun, 4 Jun 2006 20:12:23 -0300, "Luiz Fernando N. Capitulino" <[EMAIL
PROTECTED]> wrote:
> | I understand. My intent was different, however. One of the bigger sticking
> | points for usb-serial was its interaction with line disciplines, which are
> | notorious for looping back and requesting w
Al Borchers suggested to do this in his review of my previous patch.
I guess that I skipped this initially because of my visceral dislike
of sizeof(data). But in this case it seems well localized.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- linux-2.6.17-rc6-gregkh/drivers/usb/
On Thu, 8 Jun 2006 12:21:14 +0200, Sven Moellers <[EMAIL PROTECTED]> wrote:
> I am suspecting another driver gets probed and claims the device [...]
Make sure your old usbfs based app wasn't running.
Other than this the source looks perfect, it must work.
Look at /proc/bus/usb/devices, it show
event buffers (certainly we can have a couple of pages)
- Add event counter
First touch upon usbmon for 2.6.18.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
---
I am far from done with performance issues, especially on loaded systems
where cat may be not scheduled for a few jiffies an
Implement the "error" event in usbmon.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
---
This has to go on top of the patch I sent earlier today.
I hoped I'd come with a clever way to have this combined with the submission
event, but nothing comes to mind which weren
The usbmon's documentation leaves me dissatisfied, it seems clumsy.
What do you native English speaker guys think about the below, is
it any improvement?
--- linux-2.6.17-rc5/Documentation/usb/usbmon.txt 2005-09-13
01:05:37.0 -0700
+++ linux-2.6.17-rc5-lem/Documentation/usb/usbmon.t
On Mon, 12 Jun 2006 16:29:45 -0300, "Luiz Fernando N. Capitulino" <[EMAIL
PROTECTED]> wrote:
> The problem is that ftdi_sio calls usb_control_msg() in ftdi_tiocmget()
> to get the modem status from the device, but ftdi_get_mctrl() (Serial
> Core version) cannot sleep because it's called with a s
Fix up the documentation. Apparently, I left unedited copy-paste results
in examples. Also, Alan helped me to improve the most confusing parts.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- linux-2.6.17-rc5/Documentation/usb/usbmon.txt 2005-09-13
01:05:37.0 -0700
+++
1 - 100 of 1230 matches
Mail list logo
