Alan Stern wrote:
On Fri, 30 May 2003, Brad Hards wrote:
On Fri, 30 May 2003 10:07 am, Hervé Pagès wrote:
Shouln't there be a "drivers" file too as mentioned in
linux-2.5.70/Documentation/usb/proc_usb_info.txt?
There should be, but there never will be. It dropped out of usbfs, and went to
sysfs
On Thu, May 22, 2003 at 09:12:41PM +0200, Hartmut Wahl wrote:
> Hello!
>
> On Wed, May 21, 2003 at 09:39:51AM -0700, Greg KH wrote:
> > The 2.4.21-rc2 and 2.5 kernels do not need the START_STOP flag. Can you
> > take that out and see if it still works for you on the latest kernels?
> >
> > If so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 30 May 2003 10:07 am, Hervé Pagès wrote:
> Hi,
>
> I'm using kernel 2.5.70 and I have configured
> it with CONFIG_USB_DEVICEFS=y
>
> Now if I do a :
>
># ls /proc/bus/usb/
>
> I only get :
>
> 001 002 devices
>
> Shouln't there be a "driv
Hi,
I'm using kernel 2.5.70 and I have configured
it with CONFIG_USB_DEVICEFS=y
Now if I do a :
# ls /proc/bus/usb/
I only get :
001 002 devices
Shouln't there be a "drivers" file too as mentioned in
linux-2.5.70/Documentation/usb/proc_usb_info.txt?
Here is my .config file (only USB sectio
Greg KH wrote:
and you should be fine.
On Wed, May 28, 2003 at 02:22:55PM -0700, Samuel Flory wrote:
I seem to be getting a lot of the following in dmesg:
drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s)
drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars),
On Sun, May 25, 2003 at 06:47:27PM -0700, Matthew Dharm wrote:
> This patch re-organizes abort handling and enhances disconnect handling.
>
> Not only do we keep track of the state (ABORTING, IDLE, etc.), but during
> an abort we now introduce the idea of 'okay to send' or not. The idea is
> that
On Sun, May 25, 2003 at 06:48:53PM -0700, Matthew Dharm wrote:
> This patch collapses some one-use functions into their callers. It also
> clones some code for control transfers so we can implement abortable
> control transfers with timeout.
>
> This patch is from Alan Stern.
>
> Greg, please ap
On Sat, May 24, 2003 at 12:58:02AM +0200, Oliver Neukum wrote:
> Hi,
>
> if we fail with -ENOMEM, we should do it before the device must be
> reparsed.
Applied, thanks.
greg k-h
---
This SF.net email is sponsored by: eBay
Get office equipment
On Wed, May 28, 2003 at 02:22:55PM -0700, Samuel Flory wrote:
> Greg KH wrote:
>
> >On Fri, May 23, 2003 at 10:08:07AM -0700, Samuel Flory wrote:
> >
> >
> >>
> >>
> >>Under 2.5.69-bk6 the kernel sees both the keyspan, and iogear
> >>(PL-2303) and assigns ttyUSB. Minicom will open the port, but
At 11:49 AM 5/29/03 -0700, Ted Huntington wrote:
Thanks I will look at the 2.0 spec. What would cause isochronous data to not
arrive, or not arrive with good data?
errors. After all this is a serial bus running on a PC. If you want
reliable data, bulk transfers will retry. If you want guaranteed
Thanks I will look at the 2.0 spec. What would cause isochronous data to not
arrive, or not arrive with good data?
So is there no way to guarantee data and timing with USB (1.1 or 2.0)?
So syncing 2 USB busses is possible in Linux, but difficult as you explained.
Can I use (micro)frame number?
At 10:38 AM 5/29/03 -0700, Ted Huntington wrote:
Is syncronizing 2 isochronous signals possible on 2 different hubs? on
the same hub? I need to make sure that data from 1 USB port and data
from a different USB port arrive at my circuit at the same time (to
within 1us). For now I am only using Ful
Alan Stern wrote:
On Wed, 28 May 2003, David Brownell wrote:
Right now there's
one great big usb_new_device() routine that mixes up
two very different stages
- set address, fetch device and config descriptors
- set configuration, update sysfs
The "update sysfs" should be part of usb_set_confi
I's happening on 2.4.21-rc2, and on gentoo's 2.4.20-gentoo-r5. I can
try others if you want.
/usr/src/linux $ grep USB .config | grep -v '#'
CONFIG_USB=m
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_UHCI=m
CONFIG_USB_OHCI=m
CONFIG_USB_AUDIO=m
CONFIG_USB_BLUETOOTH=m
CONFIG_USB_PRINTER=
Am Donnerstag, 29. Mai 2003 18:22 schrieb Alan Stern:
> On Thu, 29 May 2003, Oliver Neukum wrote:
> > > > Device reset is a partial re-enmeration. I suspect some
> > > > of the issues there would go better if it were more of
> > > > a full re-enumeration (you said something similar). And
> > > >
Is syncronizing 2 isochronous signals possible on 2 different hubs? on
the same hub? I need to make sure that data from 1 USB port and data
from a different USB port arrive at my circuit at the same time (to
within 1us). For now I am only using Full Speed.
thanks
Ted
--
Ted Huntington
Programme
On Fri, 23 May 2003 12:28:38 +0200
Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2003 at 11:04:36AM +0200, [EMAIL PROTECTED] wrote:
> >
> >
> > On Wed, May 21, 2003 at 06:11:06PM +0400, Sergey Vlasov wrote:
> > >>
> > >> I still think that the proper solution is to make this behavi
On Thu, 29 May 2003, Jochen Friedrich wrote:
> I reapplied your patch and reestablished the MODE-SENSE in sd.c and was
> pretty much surprised that it worked OK this time...
Very interesting... so that approach _does_ help with error recovery, at
least on your device. Probably on a lot of other
18 matches
Mail list logo
