Douglas Beattie wrote:
> [beaglebone: ~]$ dmesg | egrep "^com|OpenBSD"
> OpenBSD 5.5-beta (GENERIC-OMAP) #7: Wed Feb 19 15:42:30 EST 2014
> com0 at omap0: ti16750, 64 byte fifo
> com0: console
>
> Somehow I would expect to see 4 or 5 'com' devices reported.
> ... is this a simple configuration issue, or how should I proceed?
>
I don't think the code to detect and load a driver for the additional com*
ports exists yet.
I tried adding devices analoguous to com0 but it crashes the kernel with
a "External Non-Linefetch Abort (S)". After looking up this message on the
internet, my guess is that the memory of the additional devices probably
needs to mapped in a special way to make it accessible as device memory, but
that's just a guess and I don't know how to fix that at present.
For those interested, I don't have a patch handy but my silly, non-working,
approach was something like: (IIRC)
/sys/arch/armv7/omap/am335x.c:
- addition to struct armv7_dev am335x_devs[]:
{ .name = "com",
.unit = 1,
.mem = { { UART1_ADDR, UARTx_SIZE } },
.irq = { UART1_IRQ }
},
/sys/arch/armv7/armv7/armv7.c
- addition to struct board_dev beaglebone_devs[]:
{ "com", 1 }, /* UART1 */
