On Tue, Feb 13, 2007 at 08:40:41AM +0100, Oliver Neukum wrote:
>
> > Oliver, this looks like it's in the area that you "fixed up" to prevent
> > stuff like this from happening. :)
> >
> > Care to take a look at it?
>
> Sure.
>
> Andi, which kernel version is this? Plain 2.6.20 or something late
> Oliver, this looks like it's in the area that you "fixed up" to prevent
> stuff like this from happening. :)
>
> Care to take a look at it?
Sure.
Andi, which kernel version is this? Plain 2.6.20 or something later?
Regards
Oliver
--
SUSE LINUX Products GmbH, GF: Mark
On Mon, Feb 12, 2007 at 10:10:07PM -0500, Jon Smirl wrote:
> On 2/12/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Sun, Feb 11, 2007 at 03:20:20PM -0500, Jon Smirl wrote:
> >> Most drivers for USB IR remote controls are out of tree. They are
> >located here:
> >> http://www.lirc.org/
> >>
> >> Why
On Tue, Feb 13, 2007 at 03:28:48PM +1100, ronnie sahlberg wrote:
> Please let me try again:
>
> Assume very exotic USB device X exists.
> Assume it would be desireable to be able to use this device with Linux.
> Assume that unfortunately there exists no documentation on how to
> initialize or driv
On Tue, 2007-02-13 at 15:28 +1100, ronnie sahlberg wrote:
> On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Tue, Feb 13, 2007 at 12:02:57PM +1100, ronnie sahlberg wrote:
> > > On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > > >On Mon, Feb 12, 2007 at 11:59:46PM +, Phil Endecott wrote:
On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 13, 2007 at 12:02:57PM +1100, ronnie sahlberg wrote:
> > On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > >On Mon, Feb 12, 2007 at 11:59:46PM +, Phil Endecott wrote:
> > >> > Would it be helpful for linux usb device driver developer
On Tue, Feb 13, 2007 at 12:02:57PM +1100, ronnie sahlberg wrote:
> On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Mon, Feb 12, 2007 at 11:59:46PM +, Phil Endecott wrote:
> >> > Would it be helpful for linux usb device driver developers to have a
> >> > wireshark dissector that could captu
On 2/12/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Sun, Feb 11, 2007 at 03:20:20PM -0500, Jon Smirl wrote:
> > Most drivers for USB IR remote controls are out of tree. They are located
> > here:
> > http://www.lirc.org/
> >
> > Why aren't these in-tree?
>
> Because the lirc developers do not have
> On Thu, 11 Jan 2007, Jon Smirl wrote:
>
[...]
>
> Here we see a resume that failed. The key indicator is the 0x1000 bit in
> the portsc value; it means the port is still suspended even after it was
> supposed to have resumed. This is the Intel hardware-resume bug I
> described earlier. I have
On 2/13/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 12, 2007 at 11:59:46PM +, Phil Endecott wrote:
> > > Would it be helpful for linux usb device driver developers to have a
> > > wireshark dissector that could capture and show the USB
> > > data passed between one such windows client
On Thu, Feb 08, 2007 at 09:05:15AM -0500, Edwin Olson wrote:
>
> > I'll look at it in a few minutes, but first, what do you want to do that
> > libusb can't do?
> >
> Perhaps I'm out of date, but the documentation for libusb seems to
> indicate that the API is synchronous, which would limit th
On Sun, Feb 11, 2007 at 03:20:20PM -0500, Jon Smirl wrote:
> On 2/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Sun, 11 Feb 2007, Guenther Sohler wrote:
> >
> > > Dear Users,
> > >
> > > On ebay I got a usb remote control. This is a ir receiver having a usb
> > > plug and an ir remote contro
On Mon, Feb 12, 2007 at 11:59:46PM +, Phil Endecott wrote:
> > Would it be helpful for linux usb device driver developers to have a
> > wireshark dissector that could capture and show the USB
> > data passed between one such windows client and a windows server for
> > USB over IP?
What devices
Wireshark does not support any USB/IP protocol yet.
Hi,
Wireshark does support RAW usb frames when captured on a linux usb
interface using recent tcpdump/libpcap cvs versions.
Linux USB/IP :
If you can provide me
1, some sample captures for Linux USB over IP (taken with tcpdump or wireshark)
2,
On Tue, Feb 13, 2007 at 12:51:57AM +0100, Andi Kleen wrote:
> On Mon, Feb 12, 2007 at 03:29:00PM -0800, Greg KH wrote:
> > On Tue, Feb 13, 2007 at 12:23:41AM +0100, Andi Kleen wrote:
> > > On Mon, Feb 12, 2007 at 03:20:23PM -0800, Greg KH wrote:
> > > > On Tue, Feb 13, 2007 at 12:09:53AM +0100, And
> Would it be helpful for linux usb device driver developers to have a
> wireshark dissector that could capture and show the USB
> data passed between one such windows client and a windows server for
> USB over IP?
Hi Ronnie,
I'm only vaguely involved with Linux USB but I have spent some time
ex
Hi Antoine,
A few comments:
> +#include
Why are you including the old header? Probably you are using some
obsolete stuff. You should instead include videodev2.h, removing the old
style from kernel 2.4 times.
> +static struct usb_device_id device_table[] = {
>
>
+/* devices supported by this d
On Mon, Feb 12, 2007 at 03:29:00PM -0800, Greg KH wrote:
> On Tue, Feb 13, 2007 at 12:23:41AM +0100, Andi Kleen wrote:
> > On Mon, Feb 12, 2007 at 03:20:23PM -0800, Greg KH wrote:
> > > On Tue, Feb 13, 2007 at 12:09:53AM +0100, Andi Kleen wrote:
> > > >
> > > > Got this while playing around with a
On Tue, Feb 13, 2007 at 12:23:41AM +0100, Andi Kleen wrote:
> On Mon, Feb 12, 2007 at 03:20:23PM -0800, Greg KH wrote:
> > On Tue, Feb 13, 2007 at 12:09:53AM +0100, Andi Kleen wrote:
> > >
> > > Got this while playing around with a toy.
> > >
> > > I have multiple usb serial devices of different
List,
Hope this is the correct mailinglist.
My name is Ronnie Sahlberg, one of the core developers of wireshark.
There are many "exotic" USB devices that only come with windows drivers.
For Windows there are many different USBoverIP clients and servers available.
Wireshark supports (limited) dis
On Mon, Feb 12, 2007 at 03:20:23PM -0800, Greg KH wrote:
> On Tue, Feb 13, 2007 at 12:09:53AM +0100, Andi Kleen wrote:
> >
> > Got this while playing around with a toy.
> >
> > I have multiple usb serial devices of different types.
>
> Did you yank one of them out? Was a program accessing it at
On Tue, Feb 13, 2007 at 12:09:53AM +0100, Andi Kleen wrote:
>
> Got this while playing around with a toy.
>
> I have multiple usb serial devices of different types.
Did you yank one of them out? Was a program accessing it at the same
time?
And which device was this, a pl2303 device?
thanks,
Got this while playing around with a toy.
I have multiple usb serial devices of different types.
-Andi
usb 5-2: USB disconnect, address 4
Unable to handle kernel NULL pointer dereference at 0020 RIP:
[] klist_del+0xa/0x46
PGD 79cb4067 PUD 79cb7067 PMD 0
Oops: [1] SMP
CPU 0
On 2/12/07, Jeremy Roberson <[EMAIL PROTECTED]> wrote:
> Here is the status so far. The digitizer is recognized by the USB
> Subsystem but, there are no input handlers registered for it i.e. mouse
> or event. I'm not sure how to get an input event handler registered on
> the device. Below is th
Hi Jeremy,
On 2/10/07, Roberson, Jeremy <[EMAIL PROTECTED]> wrote:
> Here is my concern. If the HID layer is fixed to support Digitizers
> which means we would no longer need separate drivers, then how are
> we(Digitizer manufacturers) supposed to get the digitizer input before
> the X Mouse driv
On Monday 12 February 2007 1:05 pm, Alan Stern wrote:
> On Mon, 12 Feb 2007, Matt Reimer wrote:
>
> > Attached is a patch against 2.6.20 to implement suspend/resume support
> > for ohci-s3c2410, based on the suspend/resume support in ohci-pxa27x.c
> > and ohci-omap.c.
> >
> > A question though: i
On Monday 12 February 2007 12:53 pm, Matt Reimer wrote:
> Attached is a patch against 2.6.20 to implement suspend/resume support
> for ohci-s3c2410, based on the suspend/resume support in ohci-pxa27x.c
> and ohci-omap.c.
I can't translate that description into behavior.
Is this basically turning
Here is the status so far. The digitizer is recognized by the USB
Subsystem but, there are no input handlers registered for it i.e. mouse
or event. I'm not sure how to get an input event handler registered on
the device. Below is the output of lsusb.
Bus 001 Device 008: ID 078c:0401
Device D
Am Montag, 12. Februar 2007 19:22 schrieb Alan Stern:
> driver.c:usb_unbind_interface(), which calls usb_autoresume_device().
> That would force it to wait until usb_suspend_interface() finished.
I had overlooked that. Thanks.
> The other way is to call usb_driver_release_interface(). I assume
On Mon, 12 Feb 2007, Matt Reimer wrote:
> Attached is a patch against 2.6.20 to implement suspend/resume support
> for ohci-s3c2410, based on the suspend/resume support in ohci-pxa27x.c
> and ohci-omap.c.
>
> A question though: is the call to usb_hcd_resume_root_hub() in those
> drivers necessary
Attached is a patch against 2.6.20 to implement suspend/resume support
for ohci-s3c2410, based on the suspend/resume support in ohci-pxa27x.c
and ohci-omap.c.
A question though: is the call to usb_hcd_resume_root_hub() in those
drivers necessary? My ohci-s3c2410.c patch seems to work fine without
On Mon, 12 Feb 2007, Oliver Neukum wrote:
> Hi Alan, list,
>
> I am having trouble using the usb_autopm_get/put_interface.
> To wake a device on demand I need to use usb_autopm_get_interface().
> However the driver needs to hold a lock while calling
> usb_autopm_put_interface(). The driver's susp
On Mon, Feb 12, 2007 at 01:16:59AM -0500, Jeff Garzik wrote:
> On Sun, Feb 11, 2007 at 10:47:27AM -0800, Greg KH wrote:
> > It's in my queue and is on track to get in before 2.6.21-rc1 is out.
>
> It breaks the build for everyone, please fast-forward the merging of
> this.
It's now in Linus's tre
On Mon, 12 Feb 2007, Oliver Neukum wrote:
> Hi,
>
> concerning this code from usb_suspend_interface(), what keeps "driver"
> valid? I can see pm_lock protecting against usb_claim_interface(), but
> what about driver (un)registration?
>
> driver = to_usb_driver(intf->dev.driver);
>
>
On Mon, 12 Feb 2007, Sergei Organov wrote:
> The fact remains that even GCC extensions to C can't deal with
> endianness. I'd like to have such an extension though.
It would be nice. And useful. It would also be nice if the compiler
could deal with unaligned data automatically.
Bear in mind t
Hello!
I've been a little longer, but I could recompiled my kernel with the
debug USB support.
This is the end of /var/log/message after retrying to get on the dongle:
Feb 12 17:16:24 localhost kernel: [ 198.596000] usb 1-1: new full speed
USB device using uhci_hcd and address 2
Feb 12 17:16:
Hi,
concerning this code from usb_suspend_interface(), what keeps "driver"
valid? I can see pm_lock protecting against usb_claim_interface(), but
what about driver (un)registration?
driver = to_usb_driver(intf->dev.driver);
if (driver->suspend && driver->resume) {
Hi Alan, list,
I am having trouble using the usb_autopm_get/put_interface.
To wake a device on demand I need to use usb_autopm_get_interface().
However the driver needs to hold a lock while calling
usb_autopm_put_interface(). The driver's suspend method in turn
needs to take a lock to wait for ong
Hi !
I'm trying to use a dongle for ndiswrapper, but it fails because a
problem of usb. Note that the problem appear when ndiswrapper is fully
uninstalled (and others packages as ndiswrapper-utils, with modprobe -r,
etc...).
So, when I get on the first time the dongle, a lsusb get :
Bus 001 D
Hi !
I'm trying to use a dongle for ndiswrapper, but it fails because a
problem of usb. Note that the problem appear when ndiswrapper is fully
uninstalled (and others packages as ndiswrapper-utils, with modprobe -r,
etc...).
So ; when I get on the first time the dongle, a lsusb give :
Bus 001
Dear Alan,
Thank you for your valuable reply.
> You don't have to unload usbhid in order to unbind it. cd to the
> /sys/bus/usb/drivers/usbhid directory and find the filename corresponding
> to your device. Let's say it is 1-4:1.0 -- then you can do (as root):
>
> echo -n 1-4:1.0 >unbi
Alan Stern <[EMAIL PROTECTED]> writes:
> On Fri, 9 Feb 2007, Sergei Organov wrote:
>
>> Alan Stern <[EMAIL PROTECTED]> writes:
>>
>> > On Thu, 8 Feb 2007, Sergei Organov wrote:
>> >
>> >> IMHO aligned(N) should be used in portable code only to *increase*
>> >> alignment (this effectively excludes
42 matches
Mail list logo
