Aurelien,
Thank you very much for the patch. It fixes the recognition problem
with my Canon Lide30 scanner and SANE/scanimage -L which I reported to
the list earlier. Now the -rc and -mm kernels again work perfectly with
SANE.
Cheers,
Mark
--
Mark McPherson <[EMAIL PROTECTED]>
-
You are correct, the patch is valid, nice catch. Linus, please apply.
I have just tested kernel version 2.6.11-rc5 and noticed it is not
possible to do an USB transfer by submitting an URB to an output
endpoint. This breaks newest versions of libusb and thus SANE,
gphoto2, and a l
Hi all,
I have just tested kernel version 2.6.11-rc5 and noticed it is not
possible to do an USB transfer by submitting an URB to an output
endpoint. This breaks newest versions of libusb and thus SANE,
gphoto2, and a lot of software.
The bug has been introduced in version 2.6.11-rc1 and is due
Hi all
First thanks for merging it I was waiting since a long time for it ;)
Just a detail there :
+#ifdef CONFIG_STB03xxx
+#define OHCI_BE_FRAME_NO_SHIFT 16
+#else
+#define OHCI_BE_FRAME_NO_SHIFT 0
+#endif
+static inline u16 ohci_frame_no(const struct ohci_hcd *ohci)
+{
+ u32 tmp;
+ if (big_endian
On Friday 25 February 2005 21.54, Olav Kongas wrote:
> Always great to get success reports, thanks :) Yet bugs get
> fixed only if people report them.
Yeah sure, but I really thought the problem came from the hardware
only and I was trying to better understand it before reporting
hypothetical b
On Fri, 25 Feb 2005, Robin Farine wrote:
> > I noticed that the sceduling of urbs is performed
> > incorrectly in some circumstances. The following patch makes
> > 2 changes to that. First, it cuts the large urbs down to
> > multiples of MaxPacketSize. Second, it eliminates possible
> > starving
On Sat, 19 Feb 2005, David Brownell wrote:
> Re timer polling -- yes, that's a mess, and I seem to recall you were
> looking at a way to let HCDs (like OHCI and EHCI) say they don't need
> a root hub timer. (Hmm, maybe just add a hc_driver.flags bit to say if
> the HCD wants the timer, and some w
On Friday 25 February 2005 10:11 am, Danilo Halla wrote:
> Hi all,
>
> I'm trying to get an USB mouse working on OMAP Innovator, but the
> kernel (2.6.11-rc5-omap1) is not detecting any device at all.
Odd. Presumably earlier kernels worked for you; you should
find out when it stopped working. I
On Fri, Feb 25, 2005 at 02:09:55PM +, Paulo Marques wrote:
> Greg KH wrote:
> >[...]
> >+if (cf->string)
> >+kfree(cf->string);
>
> [minor nitpick]
>
> This test isn't needed, is it?
>
> Unless you want to make sure that noone will use the string after
> free
Hi,
It looks as if I somehow contrived to send a blank email yesterday, sorry about
that.
> > Mmm, spoke a bit too soon. Trying to find the sweet spot between 5 and 10
> > millisecs, I'm currently at .. 20 milliseconds. I had done some testing
> > yesterday, copying 5-6MB files to and from c
On Fri, Feb 25, 2005 at 01:00:14PM -0500, Alan Stern wrote:
> On Thu, 24 Feb 2005, Greg KH wrote:
>
> > diff -Nru a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
> > --- a/drivers/usb/storage/scsiglue.c2005-02-24 11:14:55 -08:00
> > +++ b/drivers/usb/storage/scsiglue.c
Hi all,
I'm trying to get an USB mouse working on OMAP Innovator, but the
kernel (2.6.11-rc5-omap1) is not detecting any device at all.
I read on some threads that Innovator had some problems in it's wiring
and because of that USB host was not working. Does anyone know
anything about this?
Is th
On Thu, 24 Feb 2005, Greg KH wrote:
> diff -Nru a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
> --- a/drivers/usb/storage/scsiglue.c 2005-02-24 11:14:55 -08:00
> +++ b/drivers/usb/storage/scsiglue.c 2005-02-24 11:14:55 -08:00
> @@ -356,9 +356,22 @@
> SPRINTF(" Host sc
On Fri, Feb 25, 2005 at 10:46:50AM -0500, Alan Stern wrote:
> On Thu, 24 Feb 2005, Greg KH wrote:
>
> > Ok, here's 3 patches that read the strings from the device at insertion
> > time, and cache them. It makes the sysfs and /proc/bus/usb/devices file
> > use these string values to prevent bus ac
On Fri, Feb 25, 2005 at 10:46:50AM -0500, Alan Stern wrote:
> On Thu, 24 Feb 2005, Greg KH wrote:
>
> > Ok, here's 3 patches that read the strings from the device at insertion
> > time, and cache them. It makes the sysfs and /proc/bus/usb/devices file
> > use these string values to prevent bus ac
On Thursday 24 February 2005 2:20 pm, Glenn Maynard wrote:
> > The exception is that some (self-powered) root hubs have limits on the
> > amount of power they put out. For example, they might not be able to
> > put more than 250 mA out on their single port, or they might have two
> > ports each l
On Thu, 24 Feb 2005, Greg KH wrote:
> Ok, here's 3 patches that read the strings from the device at insertion
> time, and cache them. It makes the sysfs and /proc/bus/usb/devices file
> use these string values to prevent bus accesses from happening at
> inopportune times.
> I've added these thre
Hi Ian,
On Fri, 25 Feb 2005, Ian Campbell wrote:
> Using the files you attached makes the dongle work! It gets an IP
> address via DHCP and pings out quite nicely. I've not done a whole lot
> of stress testing but it is looking pretty good!
>
> It also seems to have fixed my bluetooth dongle, at l
Hello,
On Friday 25 February 2005 14.08, Olav Kongas wrote:
[...]
> I noticed that the sceduling of urbs is performed
> incorrectly in some circumstances. The following patch makes
> 2 changes to that. First, it cuts the large urbs down to
> multiples of MaxPacketSize. Second, it eliminates poss
On Thu, 24 Feb 2005, Glenn Maynard wrote:
> > It's probably not a good idea to prefer the lower-power configuration by
> > default. A better heuristic might be to prefer the highest-power
> > configuration that fits within the parent hub's power budget.
>
> A quick look suggests that doing this
Description: USBLP_WRITE_TIMEOUT was not updated with the the other
constants related to converting the final parameter of usb_{control,bulk}_msg()
to milliseconds.
Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
--- 2.6.11-rc4-mm1-v/drivers/usb/class/usblp.c 2005-02-23 18:59:22.
On Wed, 23 Feb 2005, David Hollis wrote:
> On Wed, 2005-02-23 at 14:41 -0600, [EMAIL PROTECTED] wrote:
> > Could someone give me a hint how to trouble shoot this.
> > About all I can say is it doesn't work. When I plug it in the usb
> > subsystem recognises the device and creates ethX. It just d
On Thursday 24 February 2005 11:45 am, Glenn Maynard wrote:
>
> Also, reading /proc/bus/usb/devices or lsusb -v will (currently) query
> string descriptors, even if I don't want them at all (and usb/devices
> will do so for all devices, not just the ones I'm interested in).
Feel free to submit a
Ok, here's 3 patches that read the strings from the device at insertion
time, and cache them. It makes the sysfs and /proc/bus/usb/devices file
use these string values to prevent bus accesses from happening at
inopportune times.
It's based on a patch that has been in the SuSE kernel for a long ti
Greg KH wrote:
[...]
+ if (cf->string)
+ kfree(cf->string);
[minor nitpick]
This test isn't needed, is it?
Unless you want to make sure that noone will use the string after
freeing in which case this should be:
if (cf->string) {
kfree(cf
On Fri, 2005-02-25 at 15:08 +0200, Olav Kongas wrote:
> Also, you can try the latest version of the driver. I don't
> want to put is up to the web page as it needs some more
> work, but I attach the files isp116x-hcd.c and isp116x.h
> here and you can just copy them to drivers/usb/host
> directory
On Thu, Feb 24, 2005 at 01:50:59PM -0800, David Brownell wrote:
> Feel free to submit a patch against lsusb (CVS), maybe adding/documenting
> a new flag that says not to do no more than read /proc/bus/usb/BBB/DDD
> files. There's already a way to say "just look at device BBB/DDD",
> you may have m
On Fri, Feb 18, 2005 at 09:35:25PM +0100, Jeroen Vreeken wrote:
> Oliver Neukum wrote:
>
> >+urb->status = 0;
> >+urb->dev = zd->usb;
> >+if(usb_submit_urb(urb, GFP_ATOMIC))
> >+free = 1;
> >
> >Aren't you missing a wake_up in the error case?
> >
> >+unsigned int gfp_ma
On Thu, Feb 24, 2005 at 09:04:51PM +0100, Olaf Hering wrote:
> On Thu, Feb 24, Greg KH wrote:
>
> > On Thu, Feb 24, 2005 at 08:53:57PM +0100, Olaf Hering wrote:
> > > On Thu, Feb 24, Greg KH wrote:
> > >
> > > > I've changed my mind.
> > >
> > > Thanks Greg. Did you catch all usb_string() user
Description: WDR_TIMEOUT was not updated with the the other constants
related to converting the final parameter of usb_{control,bulk}_msg() to
milliseconds.
Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
--- 2.6.11-rc4-mm1-v/drivers/usb/serial/ftdi_sio.c 2005-02-23
18:59:22.000
On Thu, Feb 24, Greg KH wrote:
> I've changed my mind.
Thanks Greg. Did you catch all usb_string() users for sysfs attributes?
There were a few more than vendor, product and release from my patch.
I wanted to fix it soon, but I was to lazy.
libsysfs seems to read all files, so we are back to squ
On Thu, Feb 24, 2005 at 09:43:44AM -0800, Nishanth Aravamudan wrote:
> Hi Greg,
>
> Just wanted to let you know that I checked all of the callers of
> usb_{control,bulk}_msg() in 2.6.11-rc4-mm1 and with the just-sent two
> patches, everything looks good.
Thanks for doing this, I've applied your t
Here's a patch for 2.6.11-rc5 that a lot of cdc-acm driver users are
clammering for.
There's a bug introduced in a cleanup which will lead
to a race making reopenings fail. This fix is by Alexander Lykanov.
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAI
On Thursday 24 February 2005 8:16 am, Randy.Dunlap wrote:
> Steve Calfee wrote:
> >
> > IIRC, one reason this was tried (and dropped) is that some devices
> > load new firmware which alters all/most/some of the device
> > descriptors, so the kernel cache is incorrect... unless they are
> > re-read
On Thu, Feb 24, 2005 at 02:04:38PM -0800, David Brownell wrote:
>
> That works for EZ-USB ... someone once told me that scheme is
> patented, which would explain why DFU uses a less robust scheme!
Yes, the EZ-USB scheme is patented, and yes, that is why the DFU spec
does not use that scheme.
tha
On Monday 21 February 2005 2:24 pm, Chris Clayton wrote:
> On Sun, 20 Feb 2005 08:39:51 +
> Chris Clayton <[EMAIL PROTECTED]> wrote:
>
> > Hi again.
> >
> > My word, I've put some hours into this, but I now have a 2.6.10 kernel with
> > which the built-in USB port on my Compaq Armada 7400 wo
Hi Torsten,
On Wed, 23 Feb 2005 [EMAIL PROTECTED] wrote:
> > --- linux-2.6.10-isp/drivers/usb/host/isp116x.h.buggy 2005-02-23
> > 18:45:55.0 +0200
> > +++ linux-2.6.10-isp/drivers/usb/host/isp116x.h 2005-02-23
> > 18:49:17.0 +0200
> > @@ -529,7 +529,7 @@ static inline v
Hi Olav, thanks for your response.
(my personal email account with NTL (*spits*), which is where I am
subscribed to linux-usb-devel, seems to be down today, so I'm only
getting the responses that are CC'd to my work email... please continue
to CC me, cheers!)
On Thu, 2005-02-24 at 02:04 +0200, Ol
Hi Ian,
On Thu, 24 Feb 2005, Ian Campbell wrote:
> The driver queues an URB with length PEGASUS_MTU + 8. PEGASUS_MTU is
> 1536, I guess the extra 8 is a status header added by the dongle, this
> gives an URB that is large enough to contain the largest packet that
> could arrive.
>
> 72 is 64 + 8,
On Wed, 23 Feb 2005, Randy.Dunlap wrote:
> IIRC, one reason this was tried (and dropped) is that some devices
> load new firmware which alters all/most/some of the device
> descriptors, so the kernel cache is incorrect... unless they are
> re-read after a firmware download.
>
> Anybody else recal
Subject: Mail Delivery failed: returning to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients.
The following address(es) failed:
smcc.demon.nl [212.238.157.128]:
RSET
250 flushed
MAIL FROM:
250 ok
On Thu, Feb 24, 2005 at 10:36:31AM -0500, Dan Streetman wrote:
>
> On Thu, 24 Feb 2005, Vojtech Pavlik wrote:
>
> >This will break setups where someone is using a non-calibrated
> >touchscreen with the current driver, right? I don't think I can merge it
> >at least until there is a way to set the
Hello all,
I'm experiencing a little difficulty with a Canon Lide30 usb scanner.
It works flawlessly with libusb and kernels up through 2.6.10 and
2.6.10-ac12, but...
Beginning with 2.6.11-rc1, and up to and including 2.6.11-rc5, the
scanner can't be found with scanimage -L. although it is attach
43 matches
Mail list logo
