#8789: /bin/read doesn't work for serial communication ---------------------------+---------------------------- Reporter: dsuden | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: x86 ---------------------------+---------------------------- Comment (by ttcoder): Wondering about stty -- since /bin/write works (at least for a dozen calls or so, it tends to become troublesome after a while), it probably means the default settings of bauds/parity/etc are correct? why would write work and not read ? Maybe we can't assume so though, let's test it -- Dane's busy for a few days, so I'll edit a summary of the suggestions made so far for him to read when he's back: - look closely at the USBserial device to see exactly what kind of hardware vendor/model that is. - test again in Terminal, invoking stty with proper settings before invoking write and read; we'll do it together via BeShare, I gotta look up its man page first and get up to speed with it. - test again with TuneTracker, making sure it's a Haiku build of TT, not a BeOS build (doubtful it has an impact, but can't rule it out since this factor has an impact on media_server code so why not on code linked against libdevice.so too) A general note @ everyone: whatever USBserial bug exists for us, it is not a Terminal-only thing, it all started when trying to make TuneTracker work with BroadcastTools(tm) switchers :-) We have edited this ticket focusing on /bin/read so that the bug could/might be reproducible without using TuneTracker, but the original problem lies in C++ code, not bash and commands.. We are unable to access the USBserial device in any way, either with bash scripts (which admittedly we never tried for serial stuff before) nor with TuneTracker (which has always been working in BeOS).. I'm not sure we can rule out a C++ problem though, maybe I should post a minimalist C++ test case that reproduces the bug ? Will look into src/tests/ when Dane is back. To be more rigorous I'll probably build it in BeOS too, so that I can come back to you saying "I tried in both -- this works in BeOS but not in Haiku". We gotta beat that one... -- Ticket URL: <http://dev.haiku-os.org/ticket/8789#comment:7> Haiku <http://dev.haiku-os.org> Haiku - the operating system.