Hello,
On Thursday 24 June 2004 15:40, you wrote:
> Hi,
>
> there seem to be duplicate entries for 0x8116 in the file,
> (if the "else if" were implemented with a switch statement
> the compiler would have warned)
>
>
>
> + else if (vendor_id == 0x06be) {
> + switch(product_id) {
>
SUMMARY
===
ftdi_sio never reasserts modem control lines once the baud has been set to
B0.
DESCRIPTION
===
Setting the baud to B0 (hangup) drops DTR. When the baud is raised again,
DTR is not raised. This can cause a modem to ignore any commands sent to it
until the device is closed
usb-storage: This device (05ab,0060,1106 S 06 P 50) has unneededSubClass
and Protocol entries in unusual_devs.h
signature.asc
Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
On Fri, 25 Jun 2004, David Brownell wrote:
> > Did those devices work okay with Windows?
>
> I don't know; I'd guess they did.
Sounds like it's not worth going to the effort of finding out how (maybe
not even possible).
> > Do you remember what the failure modes were, or can you find out?
>
On Fri, 25 Jun 2004, David Brownell wrote:
> > This patch (as316b) should do a better job. It retains the strategy of
> > adjusting io->count when something strange happens -- but now it does so
> > whenever _anything_ strange happens, rather than only when a submission
> > fails.
>
> Erm, it sh
Alan Stern wrote:
On Fri, 25 Jun 2004, David Brownell wrote:
The only thing that sticks in my memory is that some devices
had bugs that prevented the "read all bytes at once" sort
of strategy from working properly.
Did those devices work okay with Windows?
I don't know; I'd guess they did.
Proba
On Fri, 25 Jun 2004, David Brownell wrote:
> The only thing that sticks in my memory is that some devices
> had bugs that prevented the "read all bytes at once" sort
> of strategy from working properly.
Did those devices work okay with Windows?
> Probably the most compatible approach would be to
[EMAIL PROTECTED] wrote:
On Wed, 23 Jun 2004, David Brownell wrote:
The interrupt transfer should normally poll each interrupt endpoint
just once per period ... so there should be at most one NAK per period.
Are you sure your driver is scheduling an interrupt transfer? Sounds
like it's trying to
Alan Stern wrote:
Sorry, that patch had a mistake. It didn't take into account the
possibility that the first URB might complete before the second could be
submitted, causing io->count to reach 0 prematurely.
Yeah, such "fault can happen at any time" logic is easy to get wrong.
And that particul
Ullrich Sigwanz wrote:
Knowing that I am neither in the group, nor qualified enough to give any
statements that go beyond my opinion on this issue; Is it possible to change
the strategy on the fly by writing to a kernel pseudo-device at /proc ? This
would keep the fallback solution available withou
¹ÚÈ£»ó wrote:
/proc/bus/usb/001/002 test 13,3.363831 secs
/proc/bus/usb/001/002 test 14 --> 22 (error 22)
---
You can see that the last test is error.
Anyone who knows what test 14 performs tell me it in detail.
As Martin said, use the source code
¹ÚÈ£»ó wrote:
Hello.
I used ¡®Gadget Driver¡¯ to test my USB RDK.
However, I have a question.
In Gadget Driver, how read() and write() are operated ?
The read() and write() system calls are from user mode,
so to make them work you'd write a gadget driver that
hooks up to userspace through a file de
¹ÚÈ£»ó wrote:
What is the serial over USB?
And how can I get the information about serial over USB?
Any information (reference or web pageand so on) is OK.
See http://www.linux-usb.org/gadget for really basic info
about how to set it up, and anything about "usb-serial"
(particularly its "generi
On Fri, Jun 25, 2004 at 05:40:39PM +0200, David Zeuthen wrote:
>
> Hi,
>
> I have a few questions regarding the usb-storage module.
>
> First, I have a external enclosure for an ATA disk, and I'd like to
> obtain the unique serial number. If this disk were connected to a ATA
> controller, I wou
Knowing that I am neither in the group, nor qualified enough to give any
statements that go beyond my opinion on this issue; Is it possible to change
the strategy on the fly by writing to a kernel pseudo-device at /proc ? This
would keep the fallback solution available without recompiling the kerne
Serial over USB generally refers to those RS232 to USB dongles (for
adding a com port to a laptop without legacy ports, etc. - like this
thing: http://www.buy.com/retail/product.asp?sku=10262122&loc=101&sp=1)
or for generic USB to UART-like-interface chips used to update a legacy
RS232-capable boar
Alan Stern wrote:
usb_string() is moved up in the file to right after usb_get_string(),
putting it together with all the other descriptor-reading utilities.
More importantly, it no longer tries to read a string's length before
transferring the string. In this respect it's more like it used to be
Hi,
I have a few questions regarding the usb-storage module.
First, I have a external enclosure for an ATA disk, and I'd like to
obtain the unique serial number. If this disk were connected to a ATA
controller, I would have used hdparm, but since usb-storage exposes the
device as a SCSI device
Greg and others:
This patch changes usb_string() and usb_get_string(), the two utility
routines responsible for fetching string descriptors from devices.
usb_get_string() now works just like usb_get_descriptor(): retrying up to
3 times in the face of -EPIPE or 0-length results.
usb_string() i
Hello,
I sent you an email a few days ago, because you now qualify for a new mortgage.
You could get $300,000 for as little as $700 a month!
Bad credit is no problem, you can pull cash out or refinance.
Please click on this link:
http://onlinerefi.biz/a1/ke.php?bks=71
Best Regards,
Steve Morris
Alan Stern wrote:
David:
Have you had a chance to go over this patch:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=108739543030415&w=2
I was going to OK the first version but then you revised it
and I thought I should spend more time reviewing it ... which
made it fall off the top of my queue,
On Fri, 25 Jun 2004, Daniel Drake wrote:
> Hi,
>
> Alan Stern wrote:
> > From things I've seen in the past, I'll guess that the device reports "No
> > medium present" until it finishes initializing, which might require a few
> > seconds. Since the usb-storage and other drivers try probing the
Hi,
[ Continuing an older discussion because I'm seeing the same problem ]
John H. wrote:
> how do i figure out which #3 is?
In my case, it's a 7-port hub. If the four devices that I have on my desk
(mouse, keyboard, media drive, and Bluetooth) are all plugged in when I
boot, the USB subsystem
On Fri, 25 Jun 2004, Tommy Faasen wrote:
> I increased the delay to 100 milliseconds but unfortunatly without any
> luck, the output again below
> If it's not to much trouble could you or anybody explain what goes wrong
> in the following excerpt
>
> uhci_hcd :00:07.2: uhci_result_control:
Material - anexo.
Att.
Tereza
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networki
sting sting wrote:
Hello,
I had submitted recently a question regarding 'USB Host Controller And
a Web Cam'
Mark McClelland answered a few days ago in this Forum that
"Any isochronous-based camera controller with alternate settings for MxPS
< 180 should work. This includes OV511+, OV518, OV518+ a
Hi,
Alan Stern wrote:
From things I've seen in the past, I'll guess that the device reports "No
medium present" until it finishes initializing, which might require a few
seconds. Since the usb-storage and other drivers try probing the device
right away, they are forced to assume that there are
27 matches
Mail list logo
