[linux-usb-devel] [PATCH] Add Sierra Wireless MC5720 ID to airprime.c

2006-05-31 Thread Jeremy Fitzhardinge
-serial.c in order to get good throughput with these devices; there's a patch floating around to do this. Is this a reasonable thing to do? (I guess I'll post my variation of the patch and see what discussion comes up...) J -- Recognize the Sierra Wireless MC5720. Signed-off-

[linux-usb-devel] [PATCH RFC] maxSize option for usb-serial to increase max endpoint buffer size

2006-05-31 Thread Jeremy Fitzhardinge
ds a third module parameter so you can specify what you think the inbound endpoint maximum packet size should be. If the parameter is not set at module loading time, it defaults to 0 and the maximum packet size detected by the usb core will be used. Signed-off-by: Jeremy Fitzhardinge <[EMAIL

[linux-usb-devel] Re: [PATCH RFC] maxSize option for usb-serial to increase max endpoint buffer size

2006-05-31 Thread Jeremy Fitzhardinge
Greg KH wrote: Not correct or needed at all. What needs to happen is the airprime driver should be changed to handle bigger buffer sizes in it, not to mess with the usb-serial core. Yes, that sounds much more sensible. I've been working with Ken on getting this driver to work better (meani

Re: [linux-usb-devel] [PATCH RFC] maxSize option for usb-serial to increase max endpoint buffer size

2006-06-12 Thread Jeremy Fitzhardinge
Greg KH wrote: > I've been working with Ken on getting this driver to work better > (meaning faster). Here's the latest version (without your new device id > added). Care to test it out and let me know if it works or not? > I've been exercising this fairly heavily for the last few hours, and i

Re: [linux-usb-devel] [GIT PATCH] USB patches for 2.6.17

2006-06-22 Thread Jeremy Fitzhardinge
Greg KH wrote: > I saw this once when debugging the usb code, but could never reproduce > it, so I attributed it to an incomplete build at the time, as a reboot > fixed it. > > Is this easy to trigger for you? > This is the same oops as I posted yesterday: "2.6.17-mm1: oops in Bluetooth stuff,

Re: [linux-usb-devel] USB driver for Sierra Wireless EM5625/MC5720 1xEVDO modules

2006-06-28 Thread Jeremy Fitzhardinge
Andy Gay wrote: > - these modules present 3 bulk EPs, the 2nd & 3rd can be used for > control & status monitoring while data transfer is in progress on the > 1st EP. This is useful (and necessary for my application) so we need to > increase the port count. > Ooh, can you share the details of tho

Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers

2006-07-03 Thread Jeremy Fitzhardinge
Andy Gay wrote: > BTW - Jeremy suggested that the number of EPs to configure should be > determined from the device ID. Makes sense to me, but then many users > may have no use for the additional EPs. Alternatively, Greg suggested > that maybe this should split into 2 drivers. Any preferences, anyo

Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers

2006-07-03 Thread Jeremy Fitzhardinge
Andy Gay wrote: >> I think if the hardware has the EPs, they should be exposed by the >> driver. You can tweak usermode as to whether they get device nodes, >> what they're called, etc. >> > I tend to agree. I'm thinking for now I should leave it as is, so it > defaults to configuring 3 EPs

Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers

2006-07-03 Thread Jeremy Fitzhardinge
Andy Gay wrote: > Aha, good news. So this patch is already obsolete, for the Sierra stuff > anyway. And as I only have Sierra kit to work with, I reckon I should > drop out of this now. > I did make some changes to the last patch to do the cleanup stuff in the > open function, do you want to see th

Re: [linux-usb-devel] 2.6.21-rc4: NULL pointer dereference oops when unplugging sierra device

2007-03-21 Thread Jeremy Fitzhardinge
Greg KH wrote: > Hm, do the two patches attached below fix this problem for you? > > The second one might not be needed, but it is there for "correctness" :) > Thanks. I'll try it out when I next boot that kernel. J

[linux-usb-devel] 2.6.22+: BUG: sleeping function called from invalid context at /home/jeremy/hg/xen/paravirt/linux/drivers/usb/core/urb.c:524, in_atomic():1, irqs_disabled():0

2007-07-23 Thread Jeremy Fitzhardinge
I get this when suspending. The kernel is 2.6.22+recent git (just before -rc1). usb 2-1: USB disconnect, address 3 BUG: sleeping function called from invalid context at /home/jeremy/hg/xen/paravirt/linux/drivers/usb/core/urb.c:524 in_atomic():1, irqs_disabled():0 1 lock held by khubd/207: #0:

Re: [linux-usb-devel] [3/3] 2.6.23-rc2: known regressions

2007-08-05 Thread Jeremy Fitzhardinge
Michal Piotrowski wrote: > Virtualization > > Subject : drivers/net/xen-netfront.c: bogus code > References : http://lkml.org/lkml/2007/7/22/256 > Last known good : ? > Submitter : Adrian Bunk <[EMAIL PROTECTED]> > Caused-By : ? > Handled

[linux-usb-devel] 2.6.12-rc1-mm3: still having USB resume problems

2005-03-25 Thread Jeremy Fitzhardinge
Though it looks a lot better; no more streams of messages. Now when I resume, I get: PCI: Enabling device :00:1d.7 ( -> 0002) <1>Unable to handle kernel NULL pointer dereference a second or so after resume. It is completely locked up at this point; magic-sysreq gets no response. lspci

Re: [linux-usb-devel] 2.6.12-rc1-mm3: still having USB resume problems

2005-03-26 Thread Jeremy Fitzhardinge
Alan Stern wrote: On Fri, 25 Mar 2005, Jeremy Fitzhardinge wrote: Though it looks a lot better; no more streams of messages. Now when I resume, I get: PCI: Enabling device :00:1d.7 ( -> 0002) <1>Unable to handle kernel NULL pointer dereference a second or so after resum

Re: [linux-usb-devel] 2.6.12-rc1-mm3: still having USB resume problems

2005-03-26 Thread Jeremy Fitzhardinge
David Brownell wrote: >On Saturday 26 March 2005 10:08 am, Jeremy Fitzhardinge wrote: > > >>Alan Stern wrote: >> >> >> >>>On Fri, 25 Mar 2005, Jeremy Fitzhardinge wrote: >>> >>> >>> >>> >>>>PC