> 2.) The other thing may be that drivers/char/tty_io.c at some levels
> does not include a call to rs285_init(). (don't quote me on the
> function name).
I do seem to have this patch in my tree. Not sure if it's still necessary.
diff -u --recursive --new-file clean/linux/drivers/char/tty_io.c
linux/drivers/char/tty_io.c
--- clean/linux/drivers/char/tty_io.c Tue Feb 16 21:12:28 1999
+++ linux/drivers/char/tty_io.c Tue Feb 16 21:13:43 1999
@@ -130,6 +130,8 @@
static int tty_fasync(int fd, struct file * filp, int on);
extern long console_8xx_init(long, long);
extern int rs_8xx_init(void);
+extern int rs285_init(void);
+extern long rs285_console_init(long, long);
#ifndef MIN
#define MIN(a,b) ((a) < (b) ? (a) : (b))
@@ -2155,6 +2160,9 @@
#endif
#ifdef CONFIG_ESPSERIAL /* init ESP before rs, so rs doesn't see the port */
espserial_init();
+#endif
+#ifdef CONFIG_SERIAL_21285
+ rs285_init();
#endif
#ifdef CONFIG_SERIAL
rs_init();
> 3.) Finally, don't define any of the other serial options such as
> because in some level of tty_io.c SERIAL_CONSOLE and
> SERIAL_21285_CONSOLE are mutually exclusive.
If this is the case in the latest kernel can you point to the problem? I just
looked at the code and didn't see anything obvious. If you select both then
the 16550 console will take precedence by default assuming both devices
actually exist (eg on CATS or NetWinder).
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
