Subject:
|
Re: Can't open serial port in Linux
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 30 Dec 1999 21:35:52 GMT
|
Viewed:
|
2142 times
|
| |
|
|
In article <FnKK9A.38z@lugnet.com>, "Tim Gilbert" <_spoon_@yahoo.com> wrote:
> It also gives better error messages than NQC does. I'm trying to see
> if I can make NQC a little better in this regard; if so I'll send a
> patch to Dave. (Hi Dave).
>
> Cheers, Tim
Currently there isn't any notion of an "error code" from the serial port
class - opening the serial port just returns true/fals. I'm wary of
adding error codes here because they'd need to be added in a portable
manner (and across the Unix, Mac, and Win implementations). I'm not
flat-out against it...I just don't want to rush into things without
considering portability.
If you have a proposal for the type of error codes you'd like to see
coming from the serial class, let me know. If they make sense across all
platforms, we can add it to the generic interface. If they are too
platform specific, then perhaps we push the whole thing into the
individual implementations (e.g. each would remember a "last error" and
this could be extracted as a C-string).
Dave
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | Re: Can't open serial port in Linux
|
| Hi. I just got through fixing a similar problem with my linux box (the fix involved a lot of tedious changing IRQ's in the BIOS, with a lot of tedious rebooting in between). Beyond Dave's good advice, you might want to check out the linux serial (...) (25 years ago, 30-Dec-99, to lugnet.robotics.rcx.nqc)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
