From: Romain <ti...@li...> - 2004-04-15 09:13:01
|
Hi Tijl, > On Tue, 13 Apr 2004 23:04:51 +0200 (CEST), Romain Li=E9vin wrote: > >> Note: kernel module behaviour/implementation is the same as the >> lib-usb one but is working better (no transfer interruption). Kernel >> module should have less latency (by nature). >> >> Tijl: I think that a FreeBSD kernel module will be the only way to >> make it work on BSD. > > The cable works fine using libusb (there are no transfer > interruptions like you mentioned above), except with ohci, where the > cable doesn't get probed and attached so a kernel module wouldn't work > here either. I did'nt know. But, I noticed in libticables support that you don't reset endpoints (due to a lack of support in libusb/BSD). This is important to make sure that a transfer is starting on a known state (and this is Ti-Connect do). I can say that receiving a FLASH app or doing a ROMdump w/ libusb support under Linux (can) fails at any moment. Well, there is a good reason to keep this support ;-) Anyways, I am very happy because I flushed this pending problem. It could have been done sooner but, well, I was not so inspired :-) roms. --- Romain Li=E9vin (roms) <ti...@li...> Site web <http://www.lievin.net> "Linux, y'a moins bien mais c'est plus cher !" |