Here is my second attempt. If this interface is somewhat sane I start
to hack the needed wrapper code.
thanks,
daniel
/*
* Copyright (c) 1997-1998,2002 University of Utah and the Flux Group.
* All rights reserved.
* @OSKIT-FLUX-GPLUS@
*/
/*
* Definition of a COM interface to support basic
Hi Wagi,
>
> > The main nonobvious thing we need is an interface for being notified on
> > modem status changes. A simple thing is just to support asyncio and report
> > "exceptional conditions" on a modem status change. So the caller wakes up
> > and calls read_modem_control or whatever it is
Roland McGrath <[EMAIL PROTECTED]> writes:
> Nice work! Can you show the code and say something about the problems and
> hacks you had to do?
Sure (I was hopping to conceal my cruel hacks :) I modified the oskit
sio driver so that only ttyS1 is initialised and ttyS0 left alone so
that remote d
> I finally managed to get the sio driver from freebsd working with the
> gnumach kernel. Was quite tricky to find the problems and the code is
> more or less a hack. To fix the last we defently need a such a
> interface. Here is my (first) attempt to such an interface. Of
> course some more gl
> for a low-level interface. My thinking is to come up with a reasonable
> oskit interface for serial ports with modem control (layered on top of the
> trivial streamdev, but different from ttydev).
I finally managed to get the sio driver from freebsd working with the
gnumach kernel. Was quite
> gnumach/include/device/tty_status.h describes the interface which is
> used for term. In the todo list is mentioned that this interface is
> somewhat limited. My question is should I change this interface as
> well, let's say taking the one from oskit (oskit/oskit/io/ttystream.h)?
That is a cr
> I'm quite sure that "@isa@0x02f8" is wrong. The syntax for bus tree
> walk is for me a bit cryptic (oskit/unsupported/bus_walk_lookup.c).
It's intended to be adequately featureful and straightforward for
mechanical purposes, not intuitive.
> oskit_dump_devices() dumps following tree for sio de
> BTW looks this setup correct?
>
> hurd:~# showtrans /dev/ttyS1
> /hurd/term /dev/ttyS1 device @isa@0x02f8
I'm quite sure that "@isa@0x02f8" is wrong. The syntax for bus tree
walk is for me a bit cryptic (oskit/unsupported/bus_walk_lookup.c).
oskit_dump_devices() dumps following tree fo
> You need a lot more glue work in oskit-mach to support a set of control
> interfaces sufficient for serial devices.
gnumach/include/device/tty_status.h describes the interface which is
used for term. In the todo list is mentioned that this interface is
somewhat limited. My question is should
You cited the code for oskit_bus_t devices, which has nothing to do with
the serial device in particular.
The code you cited is used if you do e.g. "storecat -Tdevice @". From
that you can see the bus structure and then use other names starting with @
for "bus-walk" syntax as described in the co
Hi
I'm try to get the serial driver from OSKit working with gnumach2.
Basically I just changed the Makefile to include the freebsd driver
library and added the oskit_freebsd_init_sio call to
gnumach/oskit/ds_osenv.c. Of course things are not that simple and so
I see a panic as soon the ttyS1 devi
11 matches
Mail list logo
