hello
On Sun, 2008-02-17 at 14:13 -0800, Pete Zaitcev wrote:
> On Fri, 15 Feb 2008 09:38:14 +0100, "Paolo Abeni" wrote:
>
> > I'm again playing with usbmon and I think it would be useful, at least
> > for testing purpose, being able to compile the usbmon device code as an
> > external module. []
--- Alan Stern :
> On Fri, 15 Feb 2008, tike64 wrote:
>
> > I can't understand what is going on with yahoo. My reply seemed
> > perfectly normal before sending. Hopefully this comes through a
> > little prettier ...
>
> Sorry, yes, this is much better.
I had to edit the text first in text editor
Konstantin Kletschke wrote:
> Hi!
>
> The Nikon D80 got a new Firmware version 1.10 and still needs the fixup
> in unusual_devs.h (I suspect they will never fix this :-))
>
> Kind Regards, Konsti
>
>
This looks fine to me. For form's sake, can I get we copy of
/proc/bus/usb/devices with the de
stream->free_list is either empty or contains ITD(s).
Spare an "if (!itd)" and only do another after dma_pool_alloc().
Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]>
---
drivers/usb/host/ehci-sched.c | 15 ++-
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers
On Thu, 14 Feb 2008 00:27:34 +0100, Mariusz Kozlowski wrote:
> Of course there is a typo in the subject :)
>
> 2.5.25-rc1 -> 2.6.25-rc1
>
> > Hello,
> >
> > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a
> > problem.
> > Linux boots but with huge delay due to some iss
Hi all,
after we attach a usb device we get a hub_port_connect event which
call usb_new_device. But after that, which function is called to
create device nodes and configure the device so we can use it ?
sorry, if it's a stupid question but I couldn't find such method
tracing the function call :-
On Sun, 2008-02-17 at 12:33 -0500, Alan Stern wrote:
> On Sun, 17 Feb 2008, Richard Kennedy wrote:
>
> > Sorry if this a dumb question but I've been trying to figure out how to
> > use usb_anchor_urb by looking at usb_skeleton.c.
> >
> > skel_write calls usb_anchor_urb, but how does usb_unanchor
Hi,
On Feb 18, 2008 5:02 PM, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Feb 2008, Felipe Balbi wrote:
>
> > Hi all,
> >
> > after we attach a usb device we get a hub_port_connect event which
> > call usb_new_device. But after that, which function is called to
> > create device nodes and co
On Mon, 18 Feb 2008, Felipe Balbi wrote:
> Thanks Alan for the quick reply :-)
> what I really wanna know is when we match/bind drivers to usb_interfaces.
That's in message.c:usb_set_configuration(). It occurs near the end of
that routine, in the call to device_add().
Alan Stern
-
To unsubscri
Hello,
Le samedi 16 février 2008 à 12:54 -0800, Matthew Dharm a écrit :
> On Thu, Feb 14, 2008 at 06:19:46PM +0100, René Rebe wrote:
> > As I do not know the underlying protocols off-hand, is that a driver /
> > sub-system limitation or not possible to get thru this USB mass
> > storage protocol?
On Mon, 18 Feb 2008, Felipe Balbi wrote:
> Hi all,
>
> after we attach a usb device we get a hub_port_connect event which
> call usb_new_device. But after that, which function is called to
> create device nodes and configure the device so we can use it ?
>
> sorry, if it's a stupid question but
On Mon, 18 Feb 2008, Richard Kennedy wrote:
> Alan,
> Thanks for the pointer.
> I wonder if it's worth adding a note to the documentation for
> usb_anchor_urb just to say that they are automatically unlinked on
> completion ?
That sounds like a good idea. Care to submit a patch?
Alan Stern
-
T
Congratulations!!Your email id was selected and you have therefore been
awarded the sum of £750,000GBP by the Microsoft Promotions.
contact this email for further instructions:
[EMAIL PROTECTED]
Thank you
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messa
On Mon, 18 Feb 2008, Alan Stern wrote:
> On Mon, 18 Feb 2008, Michael SCHINDLER wrote:
>
> > I have recompiled the kernel with USB debugging, and now I see
> > explicitly that EHCI hands over the device to its companion driver
> > OHCI (see below).
> >
> > However, I do not yet know why this hap
On Mon, 18 Feb 2008, Michael SCHINDLER wrote:
> I have recompiled the kernel with USB debugging, and now I see
> explicitly that EHCI hands over the device to its companion driver
> OHCI (see below).
>
> However, I do not yet know why this happens and how I can avoid it and
> have the device hand
Dear Alan,
On 13.02.08, Alan Stern wrote:
> On Wed, 13 Feb 2008 [EMAIL PROTECTED] wrote:
> > I have problems with a usb device (mp3 player) which is handled by the
> > kernel modules in a wrong way. It is a usb 2.0 device (which behaves
> > as such on e.g. Mac OS X), but with the linux kernel (2.6
Hi Dave,
After the stress test and backport gadget code from
2.6.24 to my current 2.6.20 version, the problem
remains .
It always reports error when responding to the
following setup request:
SETUP 80.06 v0300 i l00ff
usb.c always fails at replying to this request, it
reports:
write string
Hello Alan,
thanks for the quick response.
On 18.02.08, Alan Stern wrote:
> On Mon, 18 Feb 2008, Alan Stern wrote:
> > On Mon, 18 Feb 2008, Michael SCHINDLER wrote:
> >
> > > I have recompiled the kernel with USB debugging, and now I see
> > > explicitly that EHCI hands over the device to its co
On Mon, 18 Feb 2008, Michael SCHINDLER wrote:
> > > Judging from your log, the reason the handover occurs is because your
> > > device doesn't support high-speed operation. To confirm this, let's
> > > see what "lsusb -v" has to say about the device.
>
> The output from lsusb -v for the device
Am 2008-02-18 03:09 -0800 schrieb Phil Dibowitz:
> This looks fine to me. For form's sake, can I get we copy of
> /proc/bus/usb/devices with the device plugged in?
You mean this?
T: Bus=02 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64
The semaphore cp->mutex is used as mutex, convert it to the mutex API
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/usb/misc/auerswald.c
===
--- linux-2.6.orig/drivers/usb/misc/auerswald.c 2008-02-18 1
The semaphore ccp->mutex is used as mutex, convert it to the mutex API
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/usb/misc/auerswald.c
===
--- linux-2.6.orig/drivers/usb/misc/auerswald.c 2008-02-18
USB Auerswald ISDN driver: The semaphores cp->mutex, ccp->readmutex and
ccp->mutex are used as mutexes, convert them to the muxex API
--
Matthias Kaehlcke
Linux System Developer
Barcelona
We build too many walls and not enough bridges
(Isaac Newton)
The semaphore ccp->readmutex is used as mutex, convert it to the mutex API
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/usb/misc/auerswald.c
===
--- linux-2.6.orig/drivers/usb/misc/auerswald.c 2008-02
On Monday 18 February 2008, Alan Stern wrote:
> I don't know what's going on with your Mac OSX test; however the lsusb
> output indicates plainly that the Samsung device does not run at high
> speed. The key point is lack of a Device Qualifier descriptor -- it
> is mandatory for high-speed devices
On Monday 18 February 2008, hui zhuu wrote:
> Hi Dave,
>
> After the stress test and backport gadget code from
> 2.6.24 to my current 2.6.20 version, the problem
> remains .
Suggesting more strongly that it's the "d12" driver
which is making trouble.
> It always reports error when responding to
Konstantin Kletschke wrote:
> Am 2008-02-18 03:09 -0800 schrieb Phil Dibowitz:
>
>> This looks fine to me. For form's sake, can I get we copy of
>> /proc/bus/usb/devices with the device plugged in?
>
> You mean this?
Yup. Thanks.
I just noticed your patch is missing a "Signed-off-by" line, can
Hi all,
I have 1 more USB which is not gettingdetected. Following is the
information and my analysis on it
Error:
usb 2-1: device not accepting address 3, error -71
usb 2-1: device not accepting address 4, error -71
In hub.c i tried both the old scheme and the new scheme but still it
doesnt work
On Monday 18 February 2008, Karsten Wiese wrote:
>
> stream->free_list is either empty or contains ITD(s).
> Spare an "if (!itd)" and only do another after dma_pool_alloc().
>
> Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]>
Can you update this to do the same for sitd_urb_transaction()?
> --
On Feb 18, 2008 5:15 PM, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Feb 2008, Felipe Balbi wrote:
>
> > Thanks Alan for the quick reply :-)
> > what I really wanna know is when we match/bind drivers to usb_interfaces.
>
> That's in message.c:usb_set_configuration(). It occurs near the end
30 matches
Mail list logo
