Thomas Sailer wrote:
>
> Dan Streetman schrieb:
>
> > The URB is not automatically resubmitted by the HCD.
>
> BTW, what is the difference between such a nonresubmitted
> interrupt and a bulk transfer? Unless I'm missing something
> they look exactly the same on the wire, so why add another
> r
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
for code samples you can look up the uhci and ohci code in the linux source.
it is in the directory /usr/src/linux/driver
Dan Streetman schrieb:
> The URB is not automatically resubmitted by the HCD.
BTW, what is the difference between such a nonresubmitted
interrupt and a bulk transfer? Unless I'm missing something
they look exactly the same on the wire, so why add another
redundant interface?
Tom
__
Dan Streetman schrieb:
> Ok, here is a patch that adds interrupts (via interrupt URBs, instead of bulk
> URBs) to usbdevfs. This takes a different approach than the last
> (usbdevfs-interrupt) patch. It allows using interrupt-type URBs via usbdevfs,
> and maintains the correct polling interval
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 the
[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
On 16 May 2001 20:28:18 -0700, David Brownell wrote:
> > 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 t
> 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 t
> >> 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...?
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,
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. Howeve
Greg,
I didn't mean to personally offend you or any of the other usb-uhci authors with
my opinion. I was only saying that, for both uhci and usb-uhci, I tried to
follow the flow of a URB (from submit to completion), and I thought that uhci
was easier to follow. It had less conditionals, differ
Hmm, seems like it didn't go out with the patch ... :)
- Original Message -
From: "David Brownell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 16, 2001 8:12 AM
Subject: PATCH -- usb/printer.c, oops + misc
> Here's an updated version of the printer patch I sent by e
This is just an FYI ... we don't yet have a good stack trace
for the oops (say, with an AC kernel, KDB, and all debug
support features enabled).
- Original Message -
From: "Frank de Lange" <[EMAIL PROTECTED]>
To: "David Brownell" <[EMAIL PROTECTED]>
Sent: Monday, May 14, 2001 8:00 AM
Sub
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. I
Ok, here is a patch that adds interrupts (via interrupt URBs, instead of bulk
URBs) to usbdevfs. This takes a different approach than the last
(usbdevfs-interrupt) patch. It allows using interrupt-type URBs via usbdevfs,
and maintains the correct polling interval based on the endpoint's bInterv
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***
>
> 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 PRO
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,
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 lock
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
Tim wrote:
>
> I have a Assabet of intel sa1100 development board.I have download zImage in
>it.When I use ifconfig in the Assabet,example:
> I can't ping Assbet,the same I can't ping PC from Assbet.
> my PC os is redhat7.1
I think you need to install a recent 2.4.X-ac kernel on the PC side. T
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 u
23 matches
Mail list logo
