On Mon, Apr 26, 2004 at 02:49:59PM -0400, Alan Stern wrote:
> The USB core is changing the way interfaces and altsettings are stored.
> They are no longer required to be in numerical order, and as a result,
> simply indexing the interface and altsetting arrays won't work as
> expected.
>
> Thi
On Thu, Apr 29, 2004 at 07:32:30PM +0200, Sepp Wijnands wrote:
> Hi,
>
> The Alcatel TD10 USB to Serial converter cable (for use with a Alcatel
> OT 535 or 735(i) mobile phone) seems to be a repackaged Alcatel
> version of the Prolific 2303 adapter.
>
> And as such, simply adding its product/ve
On Thu, Apr 29, 2004 at 01:28:54PM -0700, David Brownell wrote:
> This patch rejects URB submissions to suspended devices, so
> that they don't get hardware-specific fault reports. Instead,
> they get the same code (-EHOSTUNREACH) for all HCDs.
>
> It also fixes a minor problem with colliding dec
On Fri, Apr 30, 2004 at 11:43:44PM +0200, Juergen Stuber wrote:
> Hi,
>
> here is the latest version 0.95 of the LEGO USB Tower driver against 2.6.6-rc3
> which corrects a lot of problems in the version currently in the kernel,
> most notably sleeping in interrupt context and improper locking.
> P
On Thu, Apr 29, 2004 at 01:24:50PM -0700, David Brownell wrote:
> This patch lets gadget zero be more useful in testing usb suspend
> and resume. It prints messages on suspend() and resume(), and
> supports an "autoresume=N" mode to wake the host after N seconds.
>
> Please merge
Applied, thanks
On Fri, 30 Apr 2004 23:09:31 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> It may be that we're making ->serialize do too much. For example, my
> recent change to devices.c uses it to prevent topology changes while
> traversing the tree, but that function could easily be served by something
On Fri, 30 Apr 2004, David Brownell wrote:
> Alan Stern wrote:
> >
> > I interpreted "children" to mean just usbdev->children[], not ports. If
> > you allow it to include the ports as well, you rule out the possibility of
> > manipulating different ports simultaneously. I admit that doesn't com
On Fri, 30 Apr 2004, David Brownell wrote:
> > You don't seem to realize the scope of this problem. Of course we need to
> > hold the semaphore. The problem is, for which device? When a driver is
> > registered, the driver model core automatically goes through all the
> > devices on the bus
2. (Found while testing your changes to usb_reset_device)
Although usbcore acquires usbdev->serialize before probing newly-attached
devices, it doesn't acquire the semaphore before probing newly-registered
drivers! I don't know how that should be fixed.
Erm, I think it's important to be con
On Fri, 30 Apr 2004 16:34:48 -0500
<[EMAIL PROTECTED]> wrote:
> Here's the patch (for 2.4) if you're curious.
Do you want me to include all relevant transport types, or you want
to do it yourself?
-- Pete
---
This SF.Net email is sponsored by
On Fri, 30 Apr 2004, David Brownell wrote:
> Alan Stern wrote:
>
> > 2. (Found while testing your changes to usb_reset_device)
> > Although usbcore acquires usbdev->serialize before probing newly-attached
> > devices, it doesn't acquire the semaphore before probing newly-registered
> > dr
Alan Stern wrote:
On Thu, 29 Apr 2004, David Brownell wrote:
This is the kind of thing I meant earlier, when I mentioned that
the basic policy for usbdev->serialize would be to own it when
manipulating children. ...
I interpreted "children" to mean just usbdev->children[], not ports. If
you al
On Fri, Apr 30, 2004 at 06:10:56PM +0200, Duncan Sands wrote:
> > Honestly, I don't see how some of these issues started showing up
> > between those two kernel releases. You can see the only changes made in
> > the USB section broken out by patch at:
> > kernel.org/pub/linux/kernel/people/gre
Alan Stern wrote:
1. (Not particularly related to anything else going on lately.
Maybe I've mentioned this to you before; I don't remember.) This code in
usb_sg_init() doesn't look good:
if (dma) {
...
} else {
/*
+/**
+ * usb_kill_urb cancel all data transfers designated by an URB
+ * @urb: pointer to urb describing a previously submitted request
Wouldn't better semantics be "kill and bury" ... that is,
even dropping the reference? An urb that's "killed" would
not ever be re-used ... simpler. Completio
Am Freitag, 30. April 2004 21:19 schrieb Alan Stern:
> Not at all. The core already contains the necessary locking, and I
> mentioned in passing that the check has to be done at the right place.
> This simple patch will do the job:
Doh. OK, right you are :-)
It seems to me that the approach sat
Hi,
here is the latest version 0.95 of the LEGO USB Tower driver against 2.6.6-rc3
which corrects a lot of problems in the version currently in the kernel,
most notably sleeping in interrupt context and improper locking.
Please apply.
It has been thoroughly tested with UHCI, OHCI and EHCI host co
Here's the patch (for 2.4) if you're curious.
2cdromfix2.patch
Description: 2cdromfix2.patch
Alan Stern wrote:
> On Fri, 30 Apr 2004 [EMAIL PROTECTED] wrote:
>
>> So, it looks like several things aren't working right: First, I
>> would *expect* the GET_DESCRIPTOR command to finish executing on
>> endpoint 0 even after the bulk in pipe stalls, but this doesn't
>> appear to be the case. It
David:
Just to make your day more miserable, here are a couple of problems I
found recently.
1. (Not particularly related to anything else going on lately.
Maybe I've mentioned this to you before; I don't remember.) This code in
usb_sg_init() doesn't look good:
if (d
On Fri, 30 Apr 2004 [EMAIL PROTECTED] wrote:
> So, it looks like several things aren't working right: First, I would
> *expect* the GET_DESCRIPTOR command to finish executing on endpoint 0
> even
> after the bulk in pipe stalls, but this doesn't appear to be the case.
> It
> looks like a stall
Pete Zaitcev wrote:
> On Wed, 28 Apr 2004 15:09:39 -0400 (EDT) Alan Stern
> <[EMAIL PROTECTED]> wrote:
>
>>> Perhaps I could keep the proc_ioctls from running until the device
>>> isn't being used by usb-storage,
>>
>> That sounds feasible.
>
> It is feasible, but it runs into difficulties with
On Wed, 17 Mar 2004 11:44:11 -0800
Aaron Lehmann <[EMAIL PROTECTED]> wrote:
> +++ kernel-source-2.4.21/drivers/usb/printer.c2003-08-24 22:41:39 +0400
> +/* Gets the device ID string; either from the device directly (for good
> + * devices) or from the cache (for buggy printers which can l
On Fri, 16 Apr 2004 00:35:16 +0100
Martin Habets <[EMAIL PROTECTED]> wrote:
> There is a problem in the GET_DEVICE_ID ioctl() implementation. The patch below
> (against 2.6 current) fixes the code to be according to the official usb printer
> spec.
Marin, you seem to have dropped the ball on thi
Alan Stern wrote:
> On Fri, 30 Apr 2004, Juergen Stuber wrote:
> >
> > Seems like
> > ftp://ftp.kernel.org/pub/linux/kernel/people/gregkh/usb/2.6/2.6.5-rc1/usb-core-01-2.6.5-rc1.patch
> > causes it, when I apply it to linux-2.6.5-rc1-bk1 I get the crash.
>
> Is it possible that the change you pin
On Fri, 30 Apr 2004, Oliver Neukum wrote:
> Am Freitag, 30. April 2004 20:01 schrieb Alan Stern:
> > Well, in your patch you've got it changing urb->phase. And that's at a
> > time when usbcore doesn't own the URB.
>
> It is a private field and we still own a reference count.
I accept the "priv
On Fri, 30 Apr 2004, Juergen Stuber wrote:
> Stupid me, I needed to look under people/gregkh.
>
> Seems like
> ftp://ftp.kernel.org/pub/linux/kernel/people/gregkh/usb/2.6/2.6.5-rc1/usb-core-01-2.6.5-rc1.patch
> causes it, when I apply it to linux-2.6.5-rc1-bk1 I get the crash.
I see in your earl
Am Freitag, 30. April 2004 20:01 schrieb Alan Stern:
> Well, in your patch you've got it changing urb->phase. And that's at a
> time when usbcore doesn't own the URB.
It is a private field and we still own a reference count.
> Furthermore, the issue isn't how giveback_urb knows when the handler
On Wed, 28 Apr 2004 15:09:39 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> > Perhaps I could keep the proc_ioctls from running until the device isn't
> > being used by usb-storage,
>
> That sounds feasible.
It is feasible, but it runs into difficulties with locking order.
I tried to fiddle
On Fri, 30 Apr 2004, Oliver Neukum wrote:
> Am Freitag, 30. April 2004 16:12 schrieb Alan Stern:
> > On Fri, 30 Apr 2004, Oliver Neukum wrote:
> > > Very, very tempting. Elegant and simple. But I have a problem with it.
> > > It's entirely legal for a driver to call usb_get_urb() twice. And then w
Juergen Stuber <[EMAIL PROTECTED]> writes:
> Alan Stern <[EMAIL PROTECTED]> writes:
>> On Thu, 29 Apr 2004, Juergen Stuber wrote:
>>
>>> beginning with 2.6.5-rc1-bk2 I'm seeing memory corruption and crash
>>> when I rip out a device in the middle of operation, as I do as
>>> part of routine testin
On Thu, 29 Apr 2004, David Brownell wrote:
> This is the kind of thing I meant earlier, when I mentioned that
> the basic policy for usbdev->serialize would be to own it when
> manipulating children. Follow that policy and those things WILL
> be safely serialized ... if they were being done with
Am Freitag, 30. April 2004 16:12 schrieb Alan Stern:
> On Fri, 30 Apr 2004, Oliver Neukum wrote:
> > Very, very tempting. Elegant and simple. But I have a problem with it.
> > It's entirely legal for a driver to call usb_get_urb() twice. And then we
> > have a problem. So I don't think that we shou
Michael Hunold wrote:
Hello David,
On 03/31/04 02:01, David Brownell wrote:
Oops, you forgot to grep:
CC [M] drivers/media/dvb/ttusb-dec/ttusb_dec.o
drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c: In function
`ttusb_setup_interfaces':
drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c:1011:
It's not a matter of serialization. The UHCI driver in 2.6 implements
queuing of URBs for all endpoints, whereas the 2.4 versions only allow
queuing for bulk endpoints
Thanks for clearing it for me. What about OHCI and EHCI?
I don't know. Maybe someone else can answer.
They should both handle
Alan Stern <[EMAIL PROTECTED]> writes:
> On Thu, 29 Apr 2004, Juergen Stuber wrote:
>
>> beginning with 2.6.5-rc1-bk2 I'm seeing memory corruption and crash
>> when I rip out a device in the middle of operation, as I do as
>> part of routine testing of the legousbtower driver I'm developing.
>> Thi
> Honestly, I don't see how some of these issues started showing up
> between those two kernel releases. You can see the only changes made in
> the USB section broken out by patch at:
> kernel.org/pub/linux/kernel/people/gregkh/2.6/2.6.6-rc2/
Hi Greg, I'm not sure when these problems starte
On Fri, Apr 30, 2004 at 09:52:00AM +0200, Duncan Sands wrote:
> (1) get Greg's latest bitkeeper tree (bk://kernel.bkbits.net/gregkh/linux/usb-2.6)
Or if you don't like using bitkeeper, use the latest -mm release. All
of the changes in my tree are in there.
Honestly, I don't see how some of these
On Thu, 29 Apr 2004, David Brownell wrote:
> Since December, gadget-2.6 has had that particular non-gadget change
> (address0_sem scope shrank the rest of the way) along with others.
> Until I added the suspend/resume stuff, last week "hub.c" had only
> reset changes.
You're right. I don't know
On Fri, 30 Apr 2004, Peep Pullerits wrote:
> Apr 30 17:39:23 entropy kernel: usb 1-1: new full speed USB device using address 2
> Apr 30 17:39:24 entropy kernel: usb-storage: This device (0a17,0006,0100 S 05 P 01)
> has unneeded SubClass and Protocol entries in unusual_devs.h
> Apr 30 17:39:24 en
On Thu, 29 Apr 2004, Juergen Stuber wrote:
> Hi,
>
> beginning with 2.6.5-rc1-bk2 I'm seeing memory corruption and crash
> when I rip out a device in the middle of operation, as I do as
> part of routine testing of the legousbtower driver I'm developing.
> This apparently causes memory corruption
Apr 30 17:39:23 entropy kernel: usb 1-1: new full speed USB device using address 2
Apr 30 17:39:24 entropy kernel: usb-storage: This device (0a17,0006,0100 S 05 P 01)
has unneeded SubClass and Protocol entries in unusual_devs.h
Apr 30 17:39:24 entropy kernel:Please send a copy of this message
My apologies--my bugzilla account doesn't have the right permissions.
It's not that I'm hiding...
I'm the one who made & submitted the patch, and I'm the one who posted
the message about Robert having found an easy way to reproduce the
issue.
--Stuart Hayes
[EMAIL PROTECTED]
-Original Mes
On Fri, 30 Apr 2004, Oliver Neukum wrote:
> Very, very tempting. Elegant and simple. But I have a problem with it.
> It's entirely legal for a driver to call usb_get_urb() twice. And then we
> have a problem. So I don't think that we should use the refcount.
Yes, it is legal for a driver to do th
On Thu, 29 Apr 2004, Pete Zaitcev wrote:
> On Thu, 29 Apr 2004 23:15:56 -0400 (EDT)
> Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > It's not a matter of serialization. The UHCI driver in 2.6 implements
> > queuing of URBs for all endpoints, whereas the 2.4 versions only allow
> > queuing for bulk
Hi. This is the qmail-send program at rabbit.tegami.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
I'm not goin
On Tuesday 27 April 2004 10:58, Oliver Neukum wrote:
> Am Dienstag, 27. April 2004 00:14 schrieb Greg KH:
> > On Mon, Apr 26, 2004 at 04:05:17PM +0200, Duncan Sands wrote:
> > > diff -Nru a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
> > > --- a/drivers/usb/core/devio.cMon Apr 26 13:48:
Hello list,
there seems to be a problem with the USB Reiner-SCT Cyberjack in the
2.6.6-rc3 Kernel.
The cyberjack module is created as a module in the kernel.
The following observations can be made:
1. after an APM resume, plugging in the reader results in:
ehci_hcd :00:1d.7: port 4 reset erro
Hello David,
On 03/31/04 02:01, David Brownell wrote:
Oops, you forgot to grep:
CC [M] drivers/media/dvb/ttusb-dec/ttusb_dec.o
drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c: In function
`ttusb_setup_interfaces':
drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c:1011: warning:
implicit decl
Hi Grzegorz,
> 1. modem_run for speedtouch stoped working somewhere between 2.6.6-rc2-bk3
> and 2.6.6-rc3-bk1. Here is the log:
>
> Apr 30 01:05:54 polb01 modem_run[9588]: [monitoring report] ADSL link went
> up
> Apr 30 01:06:11 polb01 modem_run[7828]: ADSL synchronization has been
> obtained
> A
Am Freitag, 30. April 2004 05:37 schrieb Alan Stern:
> Let's define a new field in struct urb. It could even be one of the bits
> in transfer_flags; call it URB_REJECT. The idea is that if the URB_REJECT
> flag is set then usb_submit_urb() will fail. What we want can be
> accomplished as simply
Hi,
right now I don't have the cam with me. I will check
this with this patch during weekends and tell you by Monday.
When I made changes it did work! I shall check with the patch
And I am indeed very happy about the not going back to M$.
Thanks
Rajesh
On Thu, 2004-04-29 at 20
On Wednesday 28 April 2004 13:27, Grzegorz Kulewski wrote:
> Is anybody going to look at it? It prevents my system from shuting down.
Sorry about my earlier email - the patches I was thinking about haven't
found their way into Linus's tree yet. They are in the following bitkeeper
tree: bk://kerne
On Wednesday 28 April 2004 13:27, Grzegorz Kulewski wrote:
> Is anybody going to look at it? It prevents my system from shuting down.
If you are lucky I already fixed it. Did you try the latest 2.6 kernel?
Ciao,
Duncan.
---
This SF.Net email
54 matches
Mail list logo
