Subject:
|
Re: Call for debugging support
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Sat, 18 Dec 1999 13:05:22 GMT
|
Viewed:
|
1300 times
|
| |
|
|
Hello Martin,
pthreads and select sound fairly portable. And, as I mentioned before,
there's a way of having Windows dispatch asynchronous serial events to
programs, so work on porting would be fairly localized.
The library approach has one serious drawback, however: only one LNP
program may run at a time, and they all need the library, suid root or
sgid uucp depending on your serial port settings, possibly even special
scheduling. This might become painful once debugging is supported for
good. Maybe a LNP gateway listening on some TCP/IP port would be a
cleaner way of doing business. It would also allow remote clients to use
a LNP server somewhere out there...
A simple gateway would accept connections, forward all valid packets
coming from TCP/IP to IR and forward all valid IR packets to all TCP/IP
listeners. Pretty straightforward. Clients would only need a stub
library to deal with packet formatting.
Markus.
PS: No, I'm not talking kernel modules. A networking module would be
really
nice, but then again, writing Windows .vxd's definitely isn't.
--
"Nieder mit den Zitaten!" -Markus L. Noga <markus@noga.de>
|
|
Message is in Reply To:
 | | Re: Call for debugging support
|
| (...) hello Markus, i´m still working on a (hopefully) portable, robust version of linux LNP, that allows multiple client tasks or threads on the PC to communicate with one ore more RCX´s simultanously via one tower, ( one of them could be gdb, in (...) (25 years ago, 17-Dec-99, to lugnet.robotics.rcx.legos)
|
11 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
