On Sun, Feb 10, 2008 at 10:55:14PM -0500, Alan Stern wrote:
> On Sun, 10 Feb 2008, Peter Rasmussen wrote:
>
> > I mean, I do have trouble decoding these lines:
> >
> > usb-storage: Command INQUIRY (6 bytes)
> > usb-storage: 12 00 00 00 24 00
> > usb-storage: Bulk Command S 0x43425355 T 0x1 L 36
On Sun, 10 Feb 2008, Peter Rasmussen wrote:
> Hi Alan,
>
> Yes, I realize that a flaky cable definitely is a possibility.
>
> However, as I always saw the first part in syslog (this particular
> example is from now, when it started working) like the following:
>
>
> It looked like the HW was
On Sun, 10 Feb 2008, Alan Stern wrote:
> On Sun, 10 Feb 2008, Mike Isely wrote:
>
[...]
>
> While it's clear that your patch didn't cause this, nevertheless the
> fact remains that one should never do DMA to addresses on the stack.
> While it works okay on x86, there are other architectur
On Sun, 10 Feb 2008, David Brownell wrote:
> On Sunday 10 February 2008, Alan Stern wrote:
> >
> > In view of all the problems we've been seeing with IAA implementations,
> > should the driver be changed to rely more on the watchdog timer? Maybe
> > even avoid IAA altogether?
>
> We can't avo
On Sun, 10 Feb 2008, Mike Isely wrote:
> cypress_m8: Feature buffer fixes
>
> From: Mike Isely <[EMAIL PROTECTED]>
>
> Don't hardcode the feature buffer size; use sizeof() instead. That
> way we can easily specify the size in a single spot. Speaking of the
> feature buffer size, the Cypress ap
cypress_m8: Don't issue GET_CONFIG for certain devices
From: Mike Isely <[EMAIL PROTECTED]>
Earthmate LT-20 devices (both "old" and "new" versions) can't tolerate
a GET_CONFIG command. The original Earthmate has no trouble with
this. Presumably other non-Earthmate devices are still OK as well.
cypress_m8: Limit baud rate to <=4800 for USB low speed devices
From: Mike Isely <[EMAIL PROTECTED]>
The cypress app note for the M8 states that for the USB low speed
version of the part, throughput is effectively limited to 800
bytes/sec. So if we were to try a faster baud rate in such cases t
cypress_m8: Get rid of pointless NULL check
From: Mike Isely <[EMAIL PROTECTED]>
Remove a NULL check in cypress_m8; the check is useless in this
context because it is referenced earlier in the same code path thus
the kernel would be oops'ed before reaching this point anyway. (And
it's really po
cypress_m8: Packet format is separate from characteristic size
From: Mike Isely <[EMAIL PROTECTED]>
The Cypress app note states that when using an 8 byte packet buffer
size that the packet format is modified (to be more compact). However
I have since discovered that newer DeLorme Earthmate LT-2
cypress_m8: Feature buffer fixes
From: Mike Isely <[EMAIL PROTECTED]>
Don't hardcode the feature buffer size; use sizeof() instead. That
way we can easily specify the size in a single spot. Speaking of the
feature buffer size, the Cypress app note (and further testing with a
DeLorme Earthmate)
On Sun, Feb 10, 2008 at 11:00:33PM +0100, Peter Rasmussen wrote:
> Is it possible to distinguish such a failure from a bad implementation
> of a device's USB stack?
> If it is, it would be great to also be told in some way that doesn't
> require me to know USB so intimately.
Not really. You can
On Sunday 10 February 2008, tony_gibbs wrote:
> However, if a device is using a maxPacketSize that is too big when it is
> being a Full speed device, then would a fix similar to the EHCI patch be
> need for the UHCI_HCD driver as well?
I'm not sure such a patch is possible. There are hardware lim
Hi Alan,
Yes, I realize that a flaky cable definitely is a possibility.
However, as I always saw the first part in syslog (this particular
example is from now, when it started working) like the following:
usb 1-1: new high speed USB device using ehci_hcd and address 17
usb 1-1: configuration
On Sunday 10 February 2008, Alan Stern wrote:
>
> In view of all the problems we've been seeing with IAA implementations,
> should the driver be changed to rely more on the watchdog timer? Maybe
> even avoid IAA altogether?
We can't avoid the IAAD/IIA mechanism, since that's the only way to
un
On Sun, 10 Feb 2008, Peter Rasmussen wrote:
> Could it be that the HW is flaky? It isn't a new disk.
There could be flaky cable connections.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at ht
On Sat, 9 Feb 2008, David Brownell wrote:
> Work around for an evident bug in one EHCI controller: IAA didn't get
> set when IAAD was cleared. Evidently writing the status register can
> prevent setting IAA; someone's VHDL (or whatever) code was wrong.
> This workaround catches that specific bug
Hi Dave,
Thanks for your reply. I will try the EHCI patch you mention, and try and
post the lsusb -v output tomorrow.
I agree that Belkin devices are usually very good.
However, if a device is using a maxPacketSize that is too big when it is
being a Full speed device, then would a fix similar to
There's a new PM-related change notice for the USB 2.0 specification
called "Link Power Management" (LPM). It defines a new "L1 Suspend"
state which resembles the current (L2) suspend state, except that it
can be entered and exited much more quickly. It should thus be more
useful for runtime PM,
Hi Pavel,
> Oh, I see. You're right - this race is possible... I'll fix that up
> if this patch works.
it seems to work fine. Thanks again for doing this!
Best wishes,
Duncan.
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
M
On Sun, Feb 10, 2008 at 06:34:33PM +0100, Christian Schoenebeck wrote:
> Es geschah am Sunday, 10. February 2008 18:10 als Greg KH schrieb:
> > On Sun, Feb 10, 2008 at 02:05:50PM +, Christian Schoenebeck wrote:
> > > Am Donnerstag, 7. Februar 2008 23:29:20 schrieb Sarah Sharp:
> > > > The usbfs
Hi Matt,
Thanks for your reply!
I then tried to 'reset' the disk a few times by turning it off/on and
finally it seemed to help. I haven't transferred any data yet, though.
I got the following at the end of the dmesg:
usb-storage: *** thread sleeping.
sd 1:0:0:0: [sda] Write Protect is off
s
Es geschah am Sunday, 10. February 2008 18:10 als Greg KH schrieb:
> On Sun, Feb 10, 2008 at 02:05:50PM +, Christian Schoenebeck wrote:
> > Am Donnerstag, 7. Februar 2008 23:29:20 schrieb Sarah Sharp:
> > > The usbfs2 code is in the file drivers/usb/core/endpoint_fops.c. It
> > > currently doe
On Sat, Feb 09, 2008 at 10:55:17PM -0800, Andrew Morton wrote:
> On Sat, 9 Feb 2008 18:08:14 -0800 (PST) [EMAIL PROTECTED] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9925
> >
> >Summary: PROBLEM: Card Reader Detected but won't connect to
> > system
>
On Sun, Feb 10, 2008 at 02:35:50PM +0100, Peter Rasmussen wrote:
> The following output is taken from dmesg with a 2.6.24 kernel with the
> mass storage debug flag set.
>
> This is my first attempt at using an external USB-HD, and for whatever
> reason my kernel won't give me a device to mount.
On Sun, Feb 10, 2008 at 02:50:02PM -0500, Felipe Balbi wrote:
> On Sat, Feb 09, 2008 at 10:55:17PM -0800, Andrew Morton wrote:
> > On Sat, 9 Feb 2008 18:08:14 -0800 (PST) [EMAIL PROTECTED] wrote:
> >
> > > /dev
> > > root # ls -al ub*
> > > brw-rw 1 root video 180, 0 2008-02-09 15:21 "uba"
>
On Sun, Feb 10, 2008 at 02:05:50PM +, Christian Schoenebeck wrote:
> Am Donnerstag, 7. Februar 2008 23:29:20 schrieb Sarah Sharp:
> > The usbfs2 code is in the file drivers/usb/core/endpoint_fops.c. It
> > currently doesn't support interrupt endpoints, but feel free to support and
> > send me
David Newall wrote on 03-02-08 16:07:
Greg KH wrote:
It comes down to the simple fact, if you wish to use Linux, abide by the
license it comes under. To do otherwise is both disenginous and
illegal[1].
I think you're being dishonest. This isn't really about Linux and it
being licensed under
The following output is taken from dmesg with a 2.6.24 kernel with the
mass storage debug flag set.
This is my first attempt at using an external USB-HD, and for whatever
reason my kernel won't give me a device to mount.
I have borrowed the device from a friend that runs Windows, and the
for
On 10/02/2008, Daniel Hazelton <[EMAIL PROTECTED]> wrote:
>
> Yes, of course, and I'll never argue otherwise. However, what I was saying is
> that it is the claim of the FSF that, in no uncertain terms, a C program that
> uses the standard C library interface and is linked to glibc instead of, say,
On Sunday 10 February 2008 06:20:45 Alan Cox wrote:
> > Why? Because the pre-processor is what is including any GPL'd code in my
> > application and expanding any macros. That is a purely mechanical process
> > and
>
> And its not pirating Windows because Norton Ghost put Microsoft copyright
> mate
Am Donnerstag, 7. Februar 2008 23:29:20 schrieb Sarah Sharp:
> The usbfs2 code is in the file drivers/usb/core/endpoint_fops.c. It
> currently doesn't support interrupt endpoints, but feel free to support and
> send me a patch.
For now I solved the problem by extending my (kernel space) driver wi
On Sat, Feb 09, 2008 at 10:55:17PM -0800, Andrew Morton wrote:
> On Sat, 9 Feb 2008 18:08:14 -0800 (PST) [EMAIL PROTECTED] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9925
> >
> >Summary: PROBLEM: Card Reader Detected but won't connect to
> > system
>
> Why? Because the pre-processor is what is including any GPL'd code in my
> application and expanding any macros. That is a purely mechanical process and
And its not pirating Windows because Norton Ghost put Microsoft copyright
material in your hard disk either - thats a mechanical process too.
33 matches
Mail list logo
