Ok well I have been using puc_cardbus as a starting point and in
fact in the beginning I was hoping to just the interrupt handler
and so on to it, but I belive com(4) cannot be used for the serial
ports this card presents.
I'm confused as to how things interact with the device tree: I see
for exam
I think your process is difficult because it is backwards.
Probably easier to take the closest openbsd driver, start removing
wrong-device-specific parts from it and put your own device specific
parts into it.
It will difficult to ensure your driver-independent pieces are correct
if you are picki
Thanks for your reply. Yes, I'm using ttymalloc but I'm having a
hard time telling where the terminal has attached to. For context,
I'm working on adding support for a certain cardbus 3g modem. For
a while I considered using puc at cardbus but it seems both the
interrupt handling and the non stand
On 2023/02/25 11:32, jon@elytron.openbsd.amsterdam wrote:
> Hello, I'm in the process of adapting a driver from freebsd to
> openbsd. I was wondering what I should use in place of a call like
> ttycreate(tmptty, TS_CALLOUT, "N%r", i);
>
> any hints appreciated, tmptty is a struct tty from /sys/ker
Hello, I'm in the process of adapting a driver from freebsd to
openbsd. I was wondering what I should use in place of a call like
ttycreate(tmptty, TS_CALLOUT, "N%r", i);
any hints appreciated, tmptty is a struct tty from /sys/kern/tty.c
(openbsd)
