On Tue, Apr 01, 2003 at 06:52:44PM +0100, Nick Craig-Wood wrote: > It sets up the ttys into the mode suggested on the command line, sets > them non-blocking then launches into an infinite read() and write() > loop. > > For each port... > > It generates some random data if it hasn't got any > It attempts to write() that data to the port. > If the write() succeeds it decrements the amount of random data its got > It then attempts to read data from the port. > If it gets some and it is already synced up then it continues.
Ah, sounds like a good serial driver test :) > > Could we just be flooding the first port and not getting a chance to > > send any data out the second? > > Do you mean user space or kernel space here? cambert itself just > tries to write() stuff to each port in turn and when that succeeds it > generates a little more random data and write()s that in turn. I mean within the kernel driver, sorry. I'd like to test this with some other adapters I have here, to try to see if it's a userspace or kernel problem. I only have one loopback connector on me at the moment, but have a bunch more at home. thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
