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
Quoting "Alfred M. Szmidt" <[EMAIL PROTECTED]>:
>tty1"/libexec/getty 38400" hurdon secure
> trus=
>ted console
>
> Shouldn't "/libexec/getty 38400" be "/libexec/getty 9600"? Due to
> some bug; not that I remeber what bug.
38400 always worked for me. Maybe y
--- "Alfred M. Szmidt" <[EMAIL PROTECTED]> wrote:
> Make sense?
>
> Now it does. Thanks for clearing it up for me.
>
>However, here is probably a better version of your patch, since it
>uses crash_system(). Returning err, causes launch_something () to
>retry start_child as it n
tty1"/libexec/getty 38400" hurdon secure trus=
ted console
Shouldn't "/libexec/getty 38400" be "/libexec/getty 9600"? Due to
some bug; not that I remeber what bug.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://
Make sense?
Now it does. Thanks for clearing it up for me.
However, here is probably a better version of your patch, since it
uses crash_system(). Returning err, causes launch_something () to
retry start_child as it needs to and crashes the system if nothing
works.
Does it repo
