Hallo, Al.
After your comments (mostly minor) about patch, you've said, that you
will try to test it.
Did you manage to do so or not? I'm going to send you whitespace-cleanup.patch,
req_firm.patch, will you accept and test them? Maybe it will be
accepted to the Debian.
TIA.
--
-o--=O`C
#oo'L
Am Donnerstag, 25. Januar 2007 01:21 schrieb Oleg Verych:
On 12/15/06, Alan Stern [EMAIL PROTECTED] wrote:
It isn't exported because, generally speaking, drivers can't use it. If
your driver called usb_set_configuration() from within its probe routine,
it would hang. That's because
On 2007-01-25, Oliver Neukum wrote:
Am Donnerstag, 25. Januar 2007 01:21 schrieb Oleg Verych:
[]
Ehh... USB, Devices are designed to change configurations, linux-usb isn't.
Without much technical details -- this is a bed design. No?
It is designed to change configurations through sysfs or
On Thu, 25 Jan 2007, Oleg Verych wrote:
On Thu, Jan 25, 2007 at 03:53:58PM +0100, Oliver Neukum wrote:
[]
Yes, there is something wrong with the design of this device.
For these cases there's
int usb_driver_set_configuration(struct usb_device *udev, int config)
You check the current
On Thu, Jan 25, 2007 at 03:53:58PM +0100, Oliver Neukum wrote:
[]
Yes, there is something wrong with the design of this device.
For these cases there's
int usb_driver_set_configuration(struct usb_device *udev, int config)
You check the current configuration probe() is called with, call
Am Donnerstag, 25. Januar 2007 16:54 schrieb Oleg Verych:
On Thu, Jan 25, 2007 at 04:17:03PM +0100, Oliver Neukum wrote:
[]
It is relatively new. As comment states, it doesn't guarantee
anything, caller hangs in air...
Yes, unfortunately this is true. However, as I understand it,
Am Donnerstag, 25. Januar 2007 16:16 schrieb Oleg Verych:
On Thu, Jan 25, 2007 at 03:53:58PM +0100, Oliver Neukum wrote:
[]
Yes, there is something wrong with the design of this device.
For these cases there's
int usb_driver_set_configuration(struct usb_device *udev, int config)
You
On Thu, Jan 25, 2007 at 04:17:03PM +0100, Oliver Neukum wrote:
[]
It is relatively new. As comment states, it doesn't guarantee
anything, caller hangs in air...
Yes, unfortunately this is true. However, as I understand it, you are
helpless if you are called with the wrong configuration.
Am Donnerstag, 25. Januar 2007 15:28 schrieb Oleg Verych:
When i've known how USB defines firmware updates:
-- device appears with one firmware-loading ID;
- after loading it disconnects, and reconnects;
-- new bus connect event, new ID, same hardware-device still plugged;
-- (TI USB) is
On Thu, 25 Jan 2007, Oleg Verych wrote:
On Thu, Jan 25, 2007 at 04:17:03PM +0100, Oliver Neukum wrote:
[]
It is relatively new. As comment states, it doesn't guarantee
anything, caller hangs in air...
Yes, unfortunately this is true. However, as I understand it, you are
On Thu, Jan 25, 2007 at 11:39:33AM -0500, Alan Stern wrote:
On Thu, 25 Jan 2007, Oleg Verych wrote:
0. Here i will mean first ever driver's job -- setting up device. Was it
bound by user or not -- doesn't mater.
1. USB defines interfaces and configurations of them.
On Thu, Jan 25, 2007 at
On Thu, 25 Jan 2007, Oleg Verych wrote:
On Thu, Jan 25, 2007 at 11:39:33AM -0500, Alan Stern wrote:
On Thu, 25 Jan 2007, Oleg Verych wrote:
0. Here i will mean first ever driver's job -- setting up device. Was it
bound by user or not -- doesn't mater.
1. USB defines interfaces and
On Thu, Jan 25, 2007 at 05:28:35PM +, Oleg Verych wrote:
AFAIK, this is standard USB firmware update logic. Greg even
co-authored a standard for this.
For the record, the standard I helped author is the Device Firmware
Update for USB at:
On 12/15/06, Alan Stern [EMAIL PROTECTED] wrote:
Mister Greg, how to change configuration _inside_ the driver? Device
was made to be
working on second usb config after one reconnect/device change, i've
lost whole day
trying to make something with that. After all, usb_set_configuration()
On 12/20/06, Al Borchers [EMAIL PROTECTED] wrote:
Oleg --
Quoting Oleg Verych [EMAIL PROTECTED]:
On 12/16/06, Al Borchers [EMAIL PROTECTED] wrote:
* +#define TI_3410_EZ430_ID 0xF430 /* TI ez430 development
tool
*/
Where do you use this?
Shiny new device from
Oleg --
Quoting Oleg Verych [EMAIL PROTECTED]:
On 12/16/06, Al Borchers [EMAIL PROTECTED] wrote:
* We can't remove the compiled in firmware--that would break things
until users get and install the firmware images.
* What I did in my patch at
Oleg --
Quoting Oleg Verych [EMAIL PROTECTED]:
On 12/16/06, Al Borchers [EMAIL PROTECTED] wrote:
* +#define TI_3410_EZ430_ID 0xF430 /* TI ez430 development
tool
*/
Where do you use this?
Shiny new device from TI, don't you know? You've lost nothing MSP430
Design
Oleg --
Some comments. I will be away until next Tuesday, when I can do
more with this.
* We can't remove the compiled in firmware--that would break things
until users get and install the firmware images.
* What I did in my patch at www.brimson.com/downloads/ti_usb_multitech-1.1.tgz
is to
On 12/16/06, Al Borchers [EMAIL PROTECTED] wrote:
Oleg --
Some comments. I will be away until next Tuesday, when I can do
more with this.
Thanks.
* We can't remove the compiled in firmware--that would break things
until users get and install the firmware images.
* What I did in my
On 12/14/06, Greg KH [EMAIL PROTECTED] wrote:
On Thu, Dec 14, 2006 at 11:10:46PM +0200, Oleg Verych wrote:
Hallo. Due to very big distance to my usual work stand, please accept this.
Hm, I don't think this driver is orphaned. Please work with Al to get
this accepted through him, I'll have
Am Freitag, 15. Dezember 2006 10:30 schrieb Oleg Verych:
On 12/14/06, Greg KH [EMAIL PROTECTED] wrote:
On Thu, Dec 14, 2006 at 11:10:46PM +0200, Oleg Verych wrote:
Hallo. Due to very big distance to my usual work stand, please accept
this.
Hm, I don't think this driver is orphaned.
On 12/15/06, Oliver Neukum [EMAIL PROTECTED] wrote:
Am Freitag, 15. Dezember 2006 10:30 schrieb Oleg Verych:
On 12/14/06, Greg KH [EMAIL PROTECTED] wrote:
On Thu, Dec 14, 2006 at 11:10:46PM +0200, Oleg Verych wrote:
Hallo. Due to very big distance to my usual work stand, please accept
Mister Greg, how to change configuration _inside_ the driver? Device
was made to be
working on second usb config after one reconnect/device change, i've
lost whole day
trying to make something with that. After all, usb_set_configuration()
isn't even
EXPORT()ED at all !
It isn't exported
Oleg --
I will look at it tonight.
(The driver is not orphaned, though I have limited
time to work on it.)
-- Al
Quoting Oleg Verych [EMAIL PROTECTED]:
On 12/14/06, Greg KH [EMAIL PROTECTED] wrote:
On Thu, Dec 14, 2006 at 11:10:46PM +0200, Oleg Verych wrote:
Hallo. Due to very big
Quoting Alan Stern [EMAIL PROTECTED]:
Mister Greg, how to change configuration _inside_ the driver? Device
was made to be
working on second usb config after one reconnect/device change, i've
lost whole day
trying to make something with that. After all, usb_set_configuration()
isn't
Hallo. Due to very big distance to my usual work stand, please accept this.
--
-o--=O`C
#oo'L O
___=E M
usb-serial-ti_usb-move_firmware_to_userspace.patch.gz
Description: GNU Zip compressed data
-
Take Surveys. Earn Cash.
On Thu, Dec 14, 2006 at 11:10:46PM +0200, Oleg Verych wrote:
Hallo. Due to very big distance to my usual work stand, please accept this.
Hm, I don't think this driver is orphaned. Please work with Al to get
this accepted through him, I'll have to wait for his ACK on it.
thanks,
greg k-h
27 matches
Mail list logo
