Stephen Williams wrote:
I'm writing an application that works with a USB device. The device
itself is expected to be plugged and unplugged during the lifetime
of the application, so I'm looking for a way to follow the state of
the device. It's a GTK application, I have no problem with using
Hello everyone,
Lately I have been receiving reports of severe image corruption from
ov511 users. The images don't look like they have any added noise, but
instead look as if parts of the data are missing. All so far involve an
OHCI, so I am guessing that something in usb-ohci broke.
I tried to
Greg, these look good. Not common cases, but they should
get fixed. Johannes, could you send these to Linus?
- Dave
- Original Message -
From: Greg KH [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, May 15, 2001 9:48 PM
Subject: [PATCH] small locking bug
Here's an updated version of the printer patch I sent by earlier this week.
- semaphore guards chardev access to USB device (from earlier)
- adds omitted return retval in modified usblp_ioctl()
- fixes unplug while open cleanup in usblp_release()
- removes devfs-related noise,
I'm writing an application that works with a USB device. The device
itself is expected to be plugged and unplugged during the lifetime
of the application, so I'm looking for a way to follow the state of
the device. It's a GTK application, I have no problem with using
timers.
[EMAIL
On Wed, May 16, 2001 at 02:10:00AM -0700, Mark McClelland wrote:
Hello everyone,
[snip]
#4:
2.4.4 PPC + ohci-0508 patch, with 1.39 driver
OHCI: USB Controller: Apple Computer Inc.: Unknown device 0019
(prog-if 10 [OHCI])
***It worked with 2.4.4-pre7***
On Tue, May 15, 2001 at 02:00:04PM -0400, Dan Streetman wrote:
...
uhci.c and usb-ohci.c were easy to follow; I'm pretty confident they are ok.
usb-uhci.c was rather difficult to follow, and has many complicated paths
depending on certain states of the URB. I think I got it right tho. If
Besides my other reply, I have a couple comments:
On Wed, 16 May 2001, Georg Acher wrote:
On Tue, May 15, 2001 at 02:00:04PM -0400, Dan Streetman wrote:
Note that usb-ohci.c was not treating 0-interval interrupts as one-shot; I
changed it to treat 0-interval interrupts as 1-shot. However
hi, i am trying to debug the situation of an hp officejet g55
connected to one of the onboard usb ports in my spakin' new
asus a7v133. the printer is recognized but there is no way
to print or scan from it (connecting it at the parallel port
works fine both for
i have updated to the latest bios,
Note that usb-ohci.c was not treating 0-interval interrupts as one-shot; I
changed it to treat 0-interval interrupts as 1-shot. However the documentation
(URB.txt) doesn't mention 0-interval/one-shot interrupts at all! So either the
uhci HCDs or the documentation is wrong...?
As far
I certainly did not mean to imply that it is bad; I only was trying to say, if
the time comes that for whatever reason one of the UHCI drivers goes away, I
recommend the one that's easier to follow, because more people will be able to
understand exactly what it's doing.
Or maybe the one that
[embarrased]
the printer had (somehow) shut down at some point in the afternoon,
thus it was not listed, as pete z. pointed out.
now, after restarting it, it does in fact seem like the
printer is indeed now detected by the printer module:
bash# lsmod | egrep usb|printer|Module|uhci
Module
Hi all,
I am novice in USB area and have to develop HCD and
USBD on VxWorks platform(I know this is a Linux forum).
Can u suggest any book, site, code samples
Any input is welcome.
Thanx and rgds,
Vish
___
[EMAIL PROTECTED]
To unsubscribe, use
13 matches
Mail list logo
