Have you seen ser2net -- its in apt on debian. It makes serial ports
available over telnet (i.e. you can telnet into say port 3000 and that
will be ttyS0 and port 3001 will be ttyS1 etc). It might either serve
your purposes directly, or give you some clues to help you fix your
one?
Cheers,
Hugo Vincent.
On 3/09/2005, at 8:58 PM, Paul Parkyn wrote:
On Sat, 03 Sep 2005 17:40, Isaac Devine wrote:
The 2.6 tty layer has started to have some major rework done on it
lately. Would drivers/kernel-version are you using? You could try an
earlier kernel version - something like 2.6.8 (highest aval. on deb
stable).
What is the driver you are trying to compile? (Or is it something
closed
source that you are not able to share?)
I am struggling a little to understand what it is you are trying to
do.
pty devices are already in the kernel. OTOH maybe I don't understand
enough about pty devices :)
Real Quick Guide to the Linux serial and tty subsystem/layer:
ttys are just serial ports with some extra(character) handling on top
- stuff like escape character handling etc.
On linux serial ports and ttys are treated pretty much the same.
ie. : System calls for handling serial ports are the same as those for
tty devices.
A serial port is just a file - /dev/ttyS* etc.
ptys are user-emulated tty's - things like gnome-terminal, xterm etc.
create these. (I'm not too sure how completely they emulate them tho).
I think Paul meant a fake serial(tty) device?
HTH,
Isaac
Hi Nick & Isaac,
The driver is probably best described as a com port redirector, to the
program
it looks like a standard serial tty device the driver sends its output
via
the network.
The program was originally written for a 2.4 kernel I have tried using
a 2.4
Redhat 7.1 system and a 2.6.8.1-12mdk Mandrake 10.1 system.
With the 2.6 kernel the tty struct appears to have been changed
compared to
the 2.4 so get a lot of errors .
The driver is part of a package called Termnet-3.1 the pseudo tty
driver code
has been modified by Sena Technology to work with their Serial to
Ethernet
hardware.
There is four parts , the pty driver, a tty Daemon, a vtty manager
program and
the Termnet program. The tty daemon and the pty driver work as a
master/slave
combination. The vtty manager is used to configure the devices.
Thanks for your input, I´ll leave it for awhile and do a bit more
reading, was
hoping there might be a comms program that would do the job.
I´ll have a look at the Glabels program, thanks Isaac
regards Paul
