Hi Andreas,
On Mon, 21 Jul 2003, Major A wrote:
Ok, here we go. Attached the EZ-USB firmware release providing own
descriptors, EP0 standard requests and bulk sink/source support. Ready for
AN213x and FX - but not (yet) FX2. Successfully tested with ehci-hcd
and usbtest - as shown in
Martin,
Hi Andreas,
(Just nitpicking, my name is Andras, as in Andr\'as (TeX syntax).)
As you discovered it, would you mind to explain? My understanding was the
DISCON pin would float pretty long at H (maybe due to some similar
soft-pullup like they have on the ports) so it is required
I've search through the list archives and the web but still haven't been
able to find a suitable example for what I need to do. Douglas Roberts had
sort of the same problem as myself last year but never seemed to get it
sorted either. All the examples I've seen so far only write input_event
Hi Andras,
On Mon, 21 Jul 2003, Major A wrote:
Hi Andreas,
(Just nitpicking, my name is Andras, as in Andr\'as (TeX syntax).)
Oops, seems I mixed it up with the german forename due to visual
similarity - Sorry!
As you discovered it, would you mind to explain? My understanding was the
As wanted in dmesg I send you the messages. If you need further
info, tell me.
I'm not on the list!
-Marc
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 44
usb-storage: -- associate_dev
usb-storage: Vendor: Sandisk
usb-storage: Product: ImageMate
English version |
http://www.mail15.com.
:
1) 15 ;
2) ;
3) (POP,IMAP,SMTP);
4) ;
5);
6);
7) .
, mailto:[EMAIL PROTECTED]
*
We are glad to invite you at new free mail service http://www.mail15.com. The
advantages of this service
Ah, OK. I used the 1.5k resistor, no external transistor. I don't know
what the actual cause was, but it looks like the DISCON pin never went
floating or didn't have sufficient impedance for a USB disconnect to
occur. The guys at Cypress recommended setting both DISCON and DISCOE
to 1,
On Sun, Jul 20, 2003 at 11:48:25PM +0200, Oliver Neukum wrote:
Hi,
this piece of code from bluetooth_ctrl_msg
snip
Yup, my fault, sorry.
I'll rewrite it to not use a pool at all, like visor.c works to fix this
problem (and make it go faster...)
thanks,
greg k-h
On Mon, 21 Jul 2003, Marc Schiffbauer wrote:
As wanted in dmesg I send you the messages. If you need further
info, tell me.
I'm not on the list!
-Marc
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 44
usb-storage: -- associate_dev
David:
I'm going to send all the changes I made over the weekend to you, since
they fall under your bailiwick. You'll probably want to alter some of
them, maybe even reject one of them entirely.
This patch for usbtest fixes three problems with test 10. (I didn't look
at any of the other
Hello!
Linux 2.6.0-test1 oopses every time when pilot-link finished upload. I'm
using the Visor driver and devfs. Linux .config and the exact oops output
can be found here: http://www.red-bean.com/~proski/visor/
destroy_serial() in drivers/usb/serial/usb-serial.c checks if port-tty
and tried
David:
The recent change you made to the irq handling in hcd_endpoint_disable()
caused a problem. The statement
local_irq_save (flags);
needs to be outside the rescan loop. Otherwise, on loop iterations after
the first, flags is always set to indicate that interrupts are disabled.
On Mon, Jul 21, 2003 at 09:47:34AM -0400, Pavel Roskin wrote:
Hello!
Linux 2.6.0-test1 oopses every time when pilot-link finished upload. I'm
using the Visor driver and devfs. Linux .config and the exact oops output
can be found here: http://www.red-bean.com/~proski/visor/
This patch is
What does this error mean? I'm attempting to plug in a USB keyboard I've got
and it gives me the messages
hub 1-0:0: new USB device on port 1, assigned address 3
input: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-:00:11.2-1
drivers/usb/input/hid-core.c: ctrl urb status -75
Hi,
I need to implement the usb HID and mass-storage client on Intel PXA2xx
running
Linux 2.4.19-rmk2-pxa2. Looks to me that the kernel configuration supports
only the usb host-controller, but not the client. I hope I am wrong...
Could someone please provide any guidance on where I should
Is there a reason why this function has not been implemented?
McGiv
---
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual
David:
In my testing, the system entered a peculiar state in which the HC was
repeatedly enabled and disabled, over and over. I had seen this before,
but was never able to generate it reproducibly until now.
It turned out to be caused by the khubd thread hanging. One of the bugs I
fixed in
Sorry, my original posting had a missing '}'. Here's the corrected
version.
Alan Stern
= hub.c 1.112 vs edited =
--- 1.112/drivers/usb/core/hub.cFri Jun 20 13:12:57 2003
+++ edited/drivers/usb/core/hub.c Mon Jul 21 11:35:07 2003
@@ -876,13 +876,6 @@
unsigned int
Robert, I am sorry for asking this, but... David who? Where can I download
the softwaredocumentation from?
Thank you,
-- Toly
-Original Message-
From: Robert Schwebel [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 12:00 PM
To: Toly Kotlarsky
Cc: '[EMAIL PROTECTED]'
Subject:
Hello,
I need to write a new driver for a Philips ISP1122A USB hub.
My USB Host controller is a SL811HS Root Hub and I have connected the
ISP1122A to it.
I'd like to know the main guidelined about how to create this USB driver,
maybe an existing driver in the kernel I can use as skeleton or
Toly Kotlarsky wrote:
Hi,
I need to implement the usb HID and mass-storage client on Intel PXA2xx
running
Linux 2.4.19-rmk2-pxa2. Looks to me that the kernel configuration supports
only the usb host-controller, but not the client. I hope I am wrong...
See http://www.linux-usb.org/gadget/
...
Thank you, Dave,
I'll look into it.
-- Toly
-Original Message-
From: David Brownell [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 12:34 PM
To: Toly Kotlarsky
Cc: '[EMAIL PROTECTED]'
Subject: Re: [linux-usb-devel] usb client
Toly Kotlarsky wrote:
Hi,
I need to implement
Martin Diehl wrote:
On Sat, 19 Jul 2003, David Brownell wrote:
I'll try a bit more and post the firmware tomorrow regardless!
Great!
Ok, here we go. Attached the EZ-USB firmware release providing own
descriptors, EP0 standard requests and bulk sink/source support. Ready for
AN213x and FX -
David:
My last patch for usbcore concerns usb_device_remove() in usb.c. The most
annoying things about it is its name. The routine doesn't remove USB
devices; it disconnects drivers from interfaces. So I renamed it
usb_remove_driver(). Luckily it's not used in many places.
The real problem is
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
David:
My last patch for usbcore concerns usb_device_remove() in usb.c. The most
annoying things about it is its name. The routine doesn't remove USB
devices; it disconnects drivers from interfaces. So I renamed it
usb_remove_driver().
Oliver Neukum wrote:
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
devices; it disconnects drivers from interfaces. So I renamed it
usb_remove_driver(). Luckily it's not used in many places.
Quite misleading as well :-)
It doesn't remove a driver, as the driver stays loaded.
I suggest
On Mon, Jul 21, 2003 at 10:27:30PM +0200, Oliver Neukum wrote:
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
David:
My last patch for usbcore concerns usb_device_remove() in usb.c. The most
annoying things about it is its name. The routine doesn't remove USB
devices; it
Alan Stern wrote:
This patch for usbtest fixes three problems with test 10. (I didn't look
at any of the other tests.)
This looks fine to me, suitable for Greg to merge. The first two
wouldn't show up except after some existing error, which likely
explains why I never noticed those problems.
On Mon, 21 Jul 2003, David Brownell wrote:
Oliver Neukum wrote:
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
devices; it disconnects drivers from interfaces. So I renamed it
usb_remove_driver(). Luckily it's not used in many places.
Quite misleading as well :-)
It doesn't
Am Montag, 21. Juli 2003 22:44 schrieb Matthew Dharm:
On Mon, Jul 21, 2003 at 10:27:30PM +0200, Oliver Neukum wrote:
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
David:
My last patch for usbcore concerns usb_device_remove() in usb.c. The most
annoying things about it is its
On Mon, 21 Jul 2003, Oliver Neukum wrote:
Am Montag, 21. Juli 2003 20:02 schrieb Alan Stern:
David:
My last patch for usbcore concerns usb_device_remove() in usb.c. The most
annoying things about it is its name. The routine doesn't remove USB
devices; it disconnects drivers from
As far as names go, maybe we can all agree on
usb_unbind_driver_interface().
Of course, there's always the potential for confusion with
usb_driver_release_interface(). Nothing's perfect.
Alan Stern
---
This SF.net email is sponsored by:
Alan Stern wrote:
David:
The recent change you made to the irq handling in hcd_endpoint_disable()
caused a problem. The statement
local_irq_save (flags);
needs to be outside the rescan loop. Otherwise, on loop iterations after
the first, flags is always set to indicate that interrupts are
Alan Stern wrote:
David:
In my testing, the system entered a peculiar state in which the HC was
repeatedly enabled and disabled, over and over. I had seen this before,
but was never able to generate it reproducibly until now.
It turned out to be caused by the khubd thread hanging. One of the
Alan Stern wrote:
As far as names go, maybe we can all agree on
usb_unbind_driver_interface().
How about drop the driver, since nothing else gets unbound?
And the usb_ prefix, since it's internal to usbcore?
So: unbind_interface().
Of course, there's always the potential for confusion with
Am Montag, 21. Juli 2003 23:26 schrieb David Brownell:
Alan Stern wrote:
As far as names go, maybe we can all agree on
usb_unbind_driver_interface().
How about drop the driver, since nothing else gets unbound?
And the usb_ prefix, since it's internal to usbcore?
So: unbind_interface().
Hi. I'm pretty new to USB, so bear with me if I seem confused.
I have a new device I'm writing a driver for. 2.6.0-test1 detects the device
and puts it in the USB tree. My driver's probe function is being called.
However, the user space utility lsusb cannot always see the device properly.
I
Of course, as soon as I sent the mail, the calls to usb_get_string began
returning protocol errors.
sigh computers hate me.
-mark
---
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single
On Monday, July 21, 2003, at 07:03 PM, Mark Frazer wrote:
idVendor 0x0525 Netchip Technology Inc.
idProduct 0xdead
bcdDevice2.02
iManufacturer 1
iProduct2
iSerial 3
bNumConfigurations 1
cannot get config
Oliver Neukum wrote:
Am Montag, 21. Juli 2003 23:26 schrieb David Brownell:
Alan Stern wrote:
As far as names go, maybe we can all agree on
usb_unbind_driver_interface().
How about drop the driver, since nothing else gets unbound?
And the usb_ prefix, since it's internal to usbcore?
So:
Dr Saka Mohammed
Africa Development Bank (ADB),
Cotonou, Benin Republic
Dear ,
First, I must solicit your confidence in this transaction, this is by virtue of its
nature as being utterly confidential. Though I know that a transaction of this
magnitude will make any one apprehensive and
On Mon, 21 Jul 2003, Greg KH wrote:
This patch is already in Linus's tree -bk tree and will show up in
2.6.0-test2 (or whatever the next kernel release is called...)
Confirmed. 2.6.0-test1-bk2 is OK. Thank you!
--
Regards,
Pavel Roskin
please reply to [EMAIL PROTECTED]
thank you.
THE UNCERTAINTY PRINCIPLE IS UNTENABLE
By re-analysing Heisenberg's Gamma-Ray Microscope experiment and the ideal experiment
from which the uncertainty principle is derived, it is actually found that the
uncertainty principle can not be obtained
43 matches
Mail list logo
