A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Tue, Dec 13, 2011 at 07:14:08AM +0100, Jérôme Stadelmann wrote: > Hi, thanks for the reply > > Using usbmon I can see that the data is arriving correctly on my > host (not buffered). > I can see something strange in the way that the data is arriving > byte per byte like this : > > cfe76cc0 1231821044 S Bo:1:003:1 -115 1 = 5e > cfe76c40 1231821044 S Bo:1:003:1 -115 1 = 40 > cfe76bc0 1231821075 S Bo:1:003:1 -115 1 = 5e > cfe76b40 1231821075 S Bo:1:003:1 -115 1 = 40 > cfe76ac0 1231821105 S Bo:1:003:1 -115 1 = e6 > cfe76a40 1231821136 C Bo:1:003:1 0 1 > > cfe769c0 1231821136 C Bo:1:003:1 0 1 > > cfe76940 1231821136 C Bo:1:003:1 0 1 > > cfe76a40 1231821166 S Bo:1:003:1 -115 1 = 6c > > If I check the same in a working system (ubuntu with kernel 2.6.38), > the packets arrive in one line : > > .... 16 = b5620210 0800c8fc 08000 .... > > Now if I use picocom, I can see some data arriving every second (but > I've no way to know if the data is correct). That's good. > In my application, I'm opening the device like that : > > open("/dev/ttyACM0", O_RDWR); > > But I also have the "buffering" problem. Adding to this the fact > that the packets seem to be incomplete... Are you sure you are actually reading the data not in a buffered manner? Is your code reading continously, and have you set up the line settings correctly? Remember, this is a "virtual" serial port, but you still need to tell the tty layer to do things properly. As the driver looks good, and other programs read the data properly, I'm guessing it's your userspace program, sorry. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
