On Sun, 1 Jun 2003 [EMAIL PROTECTED] wrote:
Hello,
I have problems connecting the Pontis SP600 mp3-player (with inserted 256MB
Compact
Flash Card) with my PC through USB. The SP600 caused kernel panic with
2.4.19 and 2.4.20 on Debian testing.
As you've seen, 2.4.21-recent is more reliable.
On Sun, 1 Jun 2003, David Brownell wrote:
The device timed out a control or bulk message ... which
could be real, but I also don't trust that particular code
(since it can/does give the raced timeout messages with
quick EHCI turnaround, as well as just looking dubious).
Are you sure
Hello,
Does anyone have any pointers about where I can look up information on
how the Linux USB stack (in the 2.4 kernels) initializes and assigns a
new device? I'm doing some debugging on a USB device that we have built
using the OpenCores USB1.1 controller
On Fri, May 30, 2003 at 09:35:35PM +0200, Daniele Bellucci wrote:
On Fri 30 May 2003 19:31, Greg KH wrote:
Can you re-diff this for 2.5.70, this patch doesn't apply there, due to
some changes in the same area.
why not.
Applied, thanks,
greg k-h
On Mon, 2 Jun 2003, Oliver Neukum wrote:
OK, yes I see. You're right. Nevertheless I'd like a version that does
a full reset with enumeration for error recovery.
Do you mean recovery from errors encountered by the core while trying to
re-establish the configuration and altsettings that
Alan Stern wrote:
Some significant changes to the error recovery code were just accepted
into Greg K-H's kernel tree. They will probably show up in the main
distribution in 2.5.71, or you can get them right now by BitKeeper from
bk://linuxusb.bkbits.net/usb-2.5. With these changes, the
Hi,
kernel.bkbits.net is refusing connections. Thus I'm unable to get
to the kernel.bkbits.net/~david-b/ USB Gadget pages. Now that the
gadget stuff is in 2.5 could someone maybe put the API docs, etc.
on http://www.linux-usb.org/ ?
Cheers,
Frank.
--
Frank Becker - Intrinsyc Software, Inc. -
On Mon, 2 Jun 2003, Evan Jones wrote:
Hello,
Does anyone have any pointers about where I can look up information on
how the Linux USB stack (in the 2.4 kernels) initializes and assigns a
new device? I'm doing some debugging on a USB device that we have built
using the OpenCores USB1.1
On Mon, 2 Jun 2003, David Brownell wrote:
Alan Stern wrote:
Some significant changes to the error recovery code were just accepted
into Greg K-H's kernel tree. They will probably show up in the main
distribution in 2.5.71, or you can get them right now by BitKeeper from
Hi,
as promised - here is the patch for 2.5.70:
Added support for KAAN SIM in kobil_sct.
Greg, please apply.
Best regards
Thomas
--
-
Thomas Wahrenbruch
Hardware Development
KOBIL Systems GmbH
Pfortenring 11 D-67547
Evan Jones wrote:
Hello,
Does anyone have any pointers about where I can look up information on
how the Linux USB stack (in the 2.4 kernels) initializes and assigns a
new device?
The source code is the best reference, but you seem to
need interpretation instead ...
I'm doing some debugging
On Mon, Jun 02, 2003 at 06:58:48PM +0200, Thomas Wahrenbruch wrote:
Hi,
as promised - here is the patch for 2.5.70:
Added support for KAAN SIM in kobil_sct.
Greg, please apply.
Applied, thanks.
greg k-h
---
This SF.net email is
Frank Becker wrote:
Hi,
kernel.bkbits.net is refusing connections. Thus I'm unable to get
to the kernel.bkbits.net/~david-b/ USB Gadget pages. Now that the
gadget stuff is in 2.5 could someone maybe put the API docs, etc.
on http://www.linux-usb.org/ ?
Some version of that web page will move to
Hi,
Here are some more USB changes and fixes for 2.5.70. Some usb-storage
changes, a BKL removal, a compile fix, and some security root_plug
cleanups (the USB portion of that file.)
Please pull from: bk://kernel.bkbits.net/gregkh/linux/linus-2.5
Patches will be posted to linux-usb-devel as a
ChangeSet 1.1254.1.79, 2003/06/01 23:06:14-07:00, [EMAIL PROTECTED]
[PATCH] USB: return errors when disabling a port
this allows us to learn about a port that cannot be disabled. It's needed
for a superrobust usb_reset_device().
drivers/usb/core/hub.c |4 +++-
1 files changed, 3
ChangeSet 1.1254.1.81, 2003/06/02 10:38:03-07:00, [EMAIL PROTECTED]
[PATCH] USB: add usb_find_device() function to USB core.
drivers/usb/core/usb.c | 65 +
include/linux/usb.h|2 +
2 files changed, 67 insertions(+)
diff -Nru
ChangeSet 1.1254.1.76, 2003/06/01 22:59:36-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: timeouts and aborts
This patch adds timeouts to usb_stor_control_msg(). Now we will no longer
have to use the usb_control_msg() routine in the usb core, so all our
control messages can be interrupted
ChangeSet 1.1254.1.75, 2003/06/01 22:59:08-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: fix typo
Typo fix. We need bitwise-OR here.
drivers/usb/storage/usb.h |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/drivers/usb/storage/usb.h b/drivers/usb/storage/usb.h
ChangeSet 1.1254.1.83, 2003/06/02 10:46:42-07:00, [EMAIL PROTECTED]
[PATCH] USB: kobil_sct.c added support for KAAN SIM Reader
as promised - here is the patch for 2.5.70:
Added support for KAAN SIM in kobil_sct.
drivers/usb/serial/Kconfig |1
drivers/usb/serial/kobil_sct.c | 52
ChangeSet 1.1254.1.74, 2003/06/01 22:38:42-07:00, [EMAIL PROTECTED]
Cset exclude: [EMAIL PROTECTED]|ChangeSet|20030529215347|05329
drivers/usb/Makefile |3 ---
1 files changed, 3 deletions(-)
diff -Nru a/drivers/usb/Makefile b/drivers/usb/Makefile
--- a/drivers/usb/Makefile Mon Jun
ChangeSet 1.1254.1.80, 2003/06/02 09:39:52-07:00, [EMAIL PROTECTED]
[PATCH] SECURITY_ROOTPLUG must depend on USB
The following patch lets SECURITY_ROOTPLUG depend on USB (otherwise
there are link errors since Root Plug Support needs
usb_bus_list{,_lock}):
security/Kconfig |2 +-
1 files
ChangeSet 1.1254.1.77, 2003/06/01 23:00:01-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: usb_stor_control_msg() and stuff
This patch replaces usb_control_msg() with usb_stor_control_msg() everywhere,
which allows better abort/disconnect processing.
Some comments are fixed-up.
The
ChangeSet 1.1254.1.84, 2003/06/02 10:48:25-07:00, [EMAIL PROTECTED]
[PATCH] USB: added .owner to kobil_sct driver
drivers/usb/serial/kobil_sct.c |1 +
1 files changed, 1 insertion(+)
diff -Nru a/drivers/usb/serial/kobil_sct.c b/drivers/usb/serial/kobil_sct.c
---
ChangeSet 1.1254.8.1, 2003/05/30 12:58:33-07:00, [EMAIL PROTECTED]
[PATCH] USB: replaced BKL in rio500.c
drivers/usb/misc/rio500.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff -Nru a/drivers/usb/misc/rio500.c b/drivers/usb/misc/rio500.c
---
ChangeSet 1.1254.1.82, 2003/06/02 10:38:23-07:00, [EMAIL PROTECTED]
[PATCH] Root plug: remove USB bus walking functions, now use usb_find_device().
Also fixed compiler warnings about the dbg() function.
security/root_plug.c | 69 +++
1 files
ChangeSet 1.1254.1.78, 2003/06/01 23:00:22-07:00, [EMAIL PROTECTED]
[PATCH] USB: usb-storage: change result codes
This patch changes to SAM_STAT_ result codes, which is (a) preferred,
according to the code comments, and (b) removes some odd-looking
bit-shifting.
drivers/usb/storage/datafab.c
Here's the non-inlined doc for the gadget API.
Please merge to Linus' tree.
- Dave
Title: USB Gadget API for Linux
--- a/Documentation/DocBook/Makefile Mon Jun 2 11:30:16 2003
+++ b/Documentation/DocBook/Makefile Mon Jun 2 11:30:16 2003
@@ -11,7 +11,8 @@
kernel-locking.sgml
Ok, here are the debugging messages:
Jun 2 23:31:25 debian kernel: hub.c: port 1, portstatus 101, change 1, 12
Mb/s
Jun 2 23:31:25 debian kernel: hub.c: port 1 connection change
Jun 2 23:31:25 debian kernel: hub.c: port 1, portstatus 101, change 1, 12
Mb/s
Jun 2 23:31:25 debian kernel: hub.c:
My company is writing an application for a WinCE USB driver for an existing
camera with an existing Linux driver--and there may be others down the line.
I can handle the WinCE USB part of the driver, but I know nothing about the
chipset this camera uses, or Linux drivers. I thought someone on
Oliver Neukum wrote:
And now for the additional things.
1. Reset currently puts the burden of disconnecting the other interfaces
on the driver. This is wrong. Usbcore should do it with proper locking.
Certainly.
2. Reset should not mean disconnecting the other interfaces. The properties
Alan Stern wrote:
As discussed earlier, we need a way for a driver to inform the core that a
device's descriptors have changed (following a firmware download, for
example). Let's call this new function usb_device_altered(). It will
queue a request to be handled in another thread ...
I'm not
Alan Stern wrote:
At this point, it's not clear to me that there's any real error
happening except in the recovery code. I'm not saying there
isn't a second problem -- only that there's only evidence of that
one problem (in fault recovery) just now. And having the fault
recovery work right will
Hello, Alex.
We're using it on a PXA-255 board.
Details and sources are available at
http://boundarydevices.com/usbpatch.shtml.
I'm not sure how much is arm-specific, although a lot of his
efforts concerned getting DMA to work on a PXA-255 and
deal with some weirdness with isochronous and ATL
Alan Stern wrote:
So the question is this: If disabling a port fails, should we reset the
entire hub (and thereby reset all the other devices attached to it), or
should we power down just that one port (which will make it useless until
the entire hub is reset)?
Just power down that one port --
The original message was received at Tue, 3 Jun 2003 05:45:11 +0200 (CEST)
from [220.120.168.70]
- The following addresses had permanent fatal errors -
[EMAIL PROTECTED]
(reason: 550 5.1.1 [EMAIL PROTECTED]... User unknown)
- Transcript of session follows -
... while
I've started looking into what it will take to port the ax8817x driver
to 2.5 and the largest issue appears to be with subtle API changes that
are easily resolved. However, is there any preferred manner to write it
in 'portable' manner so that maintaining a 2.4 version and 2.5 version
isn't a
36 matches
Mail list logo
