From: Adam Kropelin <akropel1@rochester.rr.com> Fix serious regression on non-EPiC edgeport usb-serial devices. Baud rate and MCR/LCR registers are not being written on these models due to apparent copy-n-paste errors introduced with EPiC support. Failure reported by Nick Pasich <Nick@NickAndBarb.net>. Signed-off-by: Adam Kropelin <akropel1@rochester.rr.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> --- drivers/usb/serial/io_edgeport.c | 19 ++++++++----------- 1 file ...

There are not any Sierra Wireless chips in the Dell laptops. -Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the ...

[Please use Reply-to-All.] Not only is there no way to look at the SYNC and related fields from usb_control_msg() or usb_submit_urb() -- there is no way to look at them in software at all! The hardware strips those fields out before storing the data in the computer's memory. If you have an oscilloscope or USB bus analyzer, you can monitor the USB data lines and see the fields directly. Otherwise it's impossible. Alan ...

Hi, I'm reading (and implementing) the "USB Command Verifier Compliance Test Specification", on page 19 it gives me 3 starting states which I'll be using to issue the tests, those are "Default State", "Address State" and "Configured State", in order to achieve the Configured State I'd follow these steps: Configured State: The device is enumerated using the following procedure. 1. Reset the USB host controller. 2. For each port on the USB host controller turn on port power. 3. Sleep for 1 ...

Not quite. It isn't used for error recovery; when an error occurs it is called to insure the controller is quiescent. The driver doesn't really try to recover from errors. What's wrong with removing the kernel module to reset the driver? Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX ...

Kim Liu found that in the original code certain class setup requests are wrongly recognized and processed as standard setup requests. For that reason gadget ether can't work in RNDIS mode with Windows host. The patch fixes the setup request processing code, and makes class requests correctly passed to gadget layer. Signed-off-by: Kim Liu <KLiu@vixs.com> Signed-off-by: Li Yang <leoli@freescale.com> Cc: David Brownell <david-b@pacbell.net> --- drivers/usb/gadget/fsl_usb2_udc.c | 77 ...

Are you positive these are really not sierra wireless chipsets inside of these devices? thanks, greg k-h ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> ...

Hi Matthew et al., I've gotten around to creating a log of the verbose debug output when I attach the card reader with an SD card inserted. This is a multi card reader with 4 slots for different media type, the other three of which are empty. I've placed the log here: http://www.opensourcejason.info/files/usb-storage-attach-debug Cheers, Jason ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping ...

This patch is definitely wrong (besides being line-wrapped). Note that EHCI_USBLEGSUP_OS is equal to (1 << 24) -- it makes no sense to use it as an argument for a byte-sized write. Also note that the two low-order bytes in the USBLEGSUP register are read-only; you shouldn't try to write them at all. It looks like you are simply attempting to do what the previous line of code already does. Alan Stern ------------------------------------------------------------------------- This ...