Hi Daivd,
After sending the IRQ stats to you, I decided to do the same for the NEC
USB 2.0 card that I have running on the VT8235. It appears that the NEC
2.0 card is more unstable on the VT8235 than VT8235's EHCI controller
itself (the NEC USB 2.0 controller is otherwise rock solid stable on othe
Hi David,
> > ***Mar 6 11:59:27 Webdesktop kernel: PCI: 00:10.3 PCI cache line size
> > set incorrectly (32 bytes) by BIOS/FW.
> > ***Mar 6 11:59:27 Webdesktop kernel: PCI: 00:10.3 cache line size too
> > large - expecting 16.
>
> Odd -- what kind of CPU does that have?
An AthlonXP 1600+ (Pa
Mar 6 11:59:27 Webdesktop kernel: ehci-hcd 00:10.3: VIA Technologies,
Inc. USB 2.0
Mar 6 11:59:27 Webdesktop kernel: ehci-hcd 00:10.3: irq 12, pci mem
d28c4d00
Mar 6 11:59:27 Webdesktop kernel: usb.c: new USB bus registered, assigned
bus number 4
Mar 6 11:59:27 Webdesktop kernel: ehci-hcd 00:10
Hi David,
I applied your most recent patch to the 2.4.21-pre5 Kernel and found that
I can write as much as I like to the EHCI, but reading is still an issue
(although I can read more before it hangs - something that was introduced
with the usb-storage patch).
I was going through the Kernel logs a
Sorry to bug you about it and waste some of your time, i just wanted to
make sure it hadn't gotten lost someplace =)
Thanks for applying it, I know you've probably got better things to be
merging...
--
/jbm, but you can call me Josh. Really, you can!
"What's a metaphor?" "For sheep to graze in"
7
Updated version attached, includes a new pseudostate NOTATTACHED
as well as comments about the four different SUSPENDED states.
This should apply to 2.5.64 just fine.
- Dave
David Brownell wrote:
Hi,
This patch merges the USB state definitions from the ARM Linux
code (inside the sa1100 driver) an
But the host side can't track SUSPENDED reasonably anyway, and does
not need to. It's the other states that are interesting. I agree
that if we wanted to do anything with SUSPENDED it'd need thought.
Hm, I thought that if you suspend a device, that the host knows about
it. But it's been a lon
On Mon, Mar 03, 2003 at 12:18:13PM -0800, David Brownell wrote:
> This patch syncs the 2.4 version with the latest from 2.5 ...
> to make it easier for folk to use this before the "host"
> directory rename, I decided not to depend on that patch yet.
>
> VIA users will see the most benefit from thi
On Mon, Mar 03, 2003 at 11:39:09AM -0800, David Brownell wrote:
> Hi,
>
> Could you "bk mv drivers/usb/hcd drivers/usb/host" and then apply
> this patch? That will let most 2.5 host controller driver patches
> apply directly to 2.4 ... helping both releases, since 2.5 has more
> fixes while 2.4 h
On Mon, Mar 03, 2003 at 11:53:06AM -0800, David Brownell wrote:
> Hi,
>
> This is the 2.4 version of a fix that's been in 2.4 for some
> time now: when an HCD dies a premature death, its cleanup
> needs to be done in a task context. The most likely case for
> that would be physical cardbus eject
On Mon, Mar 03, 2003 at 03:47:50PM +0100, Clemens Ladisch wrote:
> Clemens Ladisch wrote:
> > OK, here are further changes for 2.4.
>
> ... and now, hopefully, with correct formatting.
Applied, thanks.
greg k-h
---
This SF.net email is sponso
On Fri, Feb 28, 2003 at 12:42:27PM -0500, Josh Myer wrote:
> Attached is the updated patch against 2.4.21-pre5
Applied, thanks.
greg k-h
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debuggi
On Wed, Mar 05, 2003 at 01:01:27PM -0800, David Brownell wrote:
> Greg KH wrote:
> >On Fri, Feb 28, 2003 at 02:46:45PM -0800, David Brownell wrote:
> >
> >>
> >>+/* the chapter 9 device states */
> >>+
> >>+enum usb_device_state {
> >>+ USB_STATE_ATTACHED = 0, /* "only" attached *
Greg:
This patch fixes an oversight in usb-storage whereby the command length
and command buffer for an automatically-generated REQUEST-SENSE command
would not be initialized properly.
Please apply both the 2.4 and 2.5 versions.
Alan Stern
-- Forwarded message --
Date: Wed, 5 Ma
Greg KH wrote:
On Fri, Feb 28, 2003 at 02:46:45PM -0800, David Brownell wrote:
+/* the chapter 9 device states */
+
+enum usb_device_state {
+ USB_STATE_ATTACHED = 0, /* "only" attached */
+ USB_STATE_POWERED,
+ USB_STATE_DEFAULT, /* limited f
P.S. to David: I want to look into writing a replacement for the
usb_bulk_msg() family of routines along the lines you described (probably
following the usb_sg_xxx calls as a model). It seems clear that a
prerequisite is a version of wait_for_completion() that also takes a
timeout. I vaguely
On Wed, 5 Mar 2003, David Brownell wrote:
> Alan Stern wrote:
> > Here is a slightly updated patch for usb-skeleton.c. It has been tested
> > minimally with real hardware, but David Brownell would like to see some
> > more tests using "gadget zero".
>
> I just did, to a 2.5.62ish system running
On Fri, Feb 28, 2003 at 02:46:45PM -0800, David Brownell wrote:
>
> +/* the chapter 9 device states */
> +
> +enum usb_device_state {
> + USB_STATE_ATTACHED = 0, /* "only" attached */
> + USB_STATE_POWERED,
> + USB_STATE_DEFAULT, /* limited functio
On Mon, Mar 03, 2003 at 03:39:22PM +0100, Clemens Ladisch wrote:
> Greg KH wrote:
> > On Thu, Feb 27, 2003 at 06:55:56PM +0100, Clemens Ladisch wrote:
> > > Greg KH wrote:
> > > > Can you also make up a 2.5 patch for this?
> > >
> > > sync with Nagano's version:
> > > - protect vendors ids against
Alan Stern wrote:
Here is a slightly updated patch for usb-skeleton.c. It has been tested
minimally with real hardware, but David Brownell would like to see some
more tests using "gadget zero".
I just did, to a 2.5.62ish system running gadget zero on real hardware.
It seemed to behave, though ther
Alan Stern wrote:
On Tue, 4 Mar 2003, David Brownell wrote:
Alan Stern wrote:
I think it's probably okay to apply this patch. More testing would be
good, but I don't have any suitable hardware. And I think a
software-loopback sort of test wouldn't address many of my changes very
well.
Ah, but
On Tue, 4 Mar 2003, David Brownell wrote:
> Alan Stern wrote:
> >
> > I think it's probably okay to apply this patch. More testing would be
> > good, but I don't have any suitable hardware. And I think a
> > software-loopback sort of test wouldn't address many of my changes very
> > well.
>
>
On Wed, Mar 05, 2003 at 11:50:52PM +1300, Bill Ryder wrote:
> Greg KH requested more frequent and smaller patches so here is the
> current working driver.
>
> (I've been holding back to give a big update and breaking the 'release
> frequently' rule - sorry about that)
>
> Following patches wil
Hi,
Bluetooth has adopted the HID concept from USB specifications.
In the present scenario, Linux kernel has HCI Class Driver which is
tightly coupled with the USB Stack.
So, it is very difficult to reuse the HCI Class driver componet for
any other technology which has adop
> > Anyway, In the setup you describe do you use "ehci" ?
> Well, "ehci-hcd". Get the latest driver, it getting closer
> to stable (and the 2.4 version is due for an update). I'd
> say to use a NEC (or Philips) add-in PCI card for now, they're
> least likely to trip over driver issues.
Ok, I've
On Thu, 2003-03-06 at 01:28, satish wrote:
> Hi,
>
> I intend to handshake with the device connected to USB port. At present i
> have connected MouseMan Wheel Logitech at the USB port of my PC. What
> will be the name of the device file created
>
> I have Red Hat Linux 7.1 2.96-98 (gcc ver
Hi,
I intend to handshake with the device connected to USB port. At present i
have connected MouseMan Wheel Logitech at the USB port of my PC. What
will be the name of the device file created
I have Red Hat Linux 7.1 2.96-98 (gcc version 2.96 2731) Linux Kernel
2.4.7-10. The file /etc
Greg KH requested more frequent and smaller patches so here is the
current working driver.
(I've been holding back to give a big update and breaking the 'release
frequently' rule - sorry about that)
Following patches will be smaller.
THis patch adds support for CrystalFontz and MatrixOrb LCD
28 matches
Mail list logo
