Messages in this thread | | | Date | Wed, 23 Nov 2005 15:25:59 +0000 | From | Russell King <> | Subject | Re: Christmas list for the kernel |
| |
On Wed, Nov 23, 2005 at 10:19:19AM -0500, Jon Smirl wrote: > On 11/23/05, Russell King <rmk+lkml@arm.linux.org.uk> wrote: > > On Wed, Nov 23, 2005 at 09:43:58AM -0500, Jon Smirl wrote: > > > My system has: > > > 2 serial > > > > > > In /sys/bus/platform/devices I see this: > > > serial8250 > > > shouldn't there be entries for all of the legacy devices? > > > > > > In /dev > > > ttyS0 > > > ttyS1 > > > ttyS2 > > > ttyS3 > > > > You're basically confused about serial ports. The kernel serial devices > > whether or not hardware is found, to allow programs such as setserial to > > function. > > > > If you disagree with that, there'll be an equal number of people who > > have serial cards that need setserial who will in turn disagree with > > you. > > This is confusing... > > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled > serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Yes it is, but it's down to the way folk want things to operate. The first two come from the legacy table in include/asm-*/serial.h. The second two come from something-that-I-have-no-clue-about but is probably ACPI related. Dunno. We're back to the far-too-many-complex-ways-to- initialise-serial problem again that I've given up really caring how many lines of serial printk junk folk end up with. I can't fight it all.
-- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |