qt is a real clusterfluck sometimes. it's the most gigantic library ever. sometimes it's like using a 10 pound sledgehammer to push a tack into a wall.
anyways qt's serial driver probably isn't the issue, it's well tested on linux.
what kernel are you running, what serial driver and chipset do you use?
the ultimate solution in linux or freebsd (which i used in my old aldl-io program) was to completely disable the kernel's serial driver and use libftdi to just send/recieve raw usb commands directly to the chip from userland. a bit more overhead, but that way you don't have a universal serial driver that needs to interface with ttys and junk telling you that a baud rate is no good, you can command the chip to do whatever it's capable of doing.. i found it rediculously stable.
unfortunately qserialport does not support libftdi, but if i had to write a version that DID use libftdi, it would be a no brainer, i could just port the serial layer from aldl-io, as the api is fairly similar.
edit: also what version of QT are you building against?
Reply With Quote
Bookmarks