Messages in this thread | | | Date | Fri, 17 Apr 1998 05:06:35 -0300 | From | "Garst R. Reese" <> | Subject | Re: Update to the serial driver |
| |
"Manuel J. Galan" <manolow@step.es> wrote: Date: Fri, 17 Apr 1998 02:28:58 +0100 (WEST)
But now, with the last serial patch and new irq detection enabled, I get - ---------------------------------------- Serial driver version 4.25 with DETECT_IRQ enabled ttyS00 at 0x03f8 (irq = 0) is a 16550A ttyS02 at 0x03e8 (irq = 0) is a ST16650V2 ttyS03 at 0x02e8 (irq = 11) is a ST16650V2 - ----------------------------------------- Which is wrong.
+Autodetect IRQ on standard ports (unsafe) +CONFIG_SERIAL_DETECT_IRQ + Enable this option if you want the kernel to try to guess which IRQ + is configured during the boot sequence and you're too lazy to edit + the boot scripts to use the setserial command. This option can be + unsafe and should not be enabled on most machines. It is far + better to dynamically request autoconfiguration during the boot-time + scripts using the setserial command. You can change the IRQ and/or + request automatic IRQ configuration at any time by using the + "setserial" program. I wouldn't include this config option at all except + people keep bellyaching about it. I guess they are really are too lazy + to edit their boot scripts. :-) If unsure, say No. + T'so what? -- Garst
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |