acm/ttyACM0/cdc_acm does not deliver data

[AW]

Hi!

I made some USB devices using the CDC-ACM proposal...
They work fine with 2.6.38.8-35.fc15/amd64 and earlier.

But since 2.6.40-4.fc15/amd64 it doesnt work as before...


My device receives a byte and then echoes it...
Sometimes when the 65th byte is sent, a read(2) returns with 0...
When I close the device and open it again and send 1 byte, I receive the echo for the 65th byte...
(btw: after 65 bytes, the roles change: my self-tinkered device sends 65bytes and listens to the echoes...)
Funnily some 65-byte-sequences are always echoed as before, while some are not (I tried it at least 10 times; I think the "bad" sequences had a lot of zeroes...)...

On my headless Atom N270 I have 1 self-tinkered USB-ACM-device and 2 DVB-T USB sticks...
When I boot the 2.6.40 kernel it crashes after some minutes...

Can we change that somehow? *wag tail*
Is it safe to use 2.6.38.8-35 behind a NAT? (I mean: r there big security holes?)

PS: I reported it here https://bugzilla.redhat.com/show_bug.cgi?id=727610 , but fedora/redhat cant help me so much, because i m the only one who has that problem...

Thx.

Bye
Arne
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/