From: Michael M. <mic...@gm...> - 2007-08-10 20:26:54
|
Juerg Haefliger wrote: > ---------- Forwarded message ---------- > From: Klaubert Herr da Silveira <kla...@gm...> > Date: Aug 10, 2007 5:43 AM > Subject: Re: "setserial /dev/ttyS1 uart none" broken in 2.6.22? > To: Juerg Haefliger <ju...@gm...> > > > Juerg, > > Sorry for lack of information... > > But when I'm locking for more information about my problem, I discover > the cause and solution. > > For some weird reason, after update of my Fedora 7 to kernel > 2.6.22.1-41, the /dev/ttyS1 was set to use same IRQ and IO Port as > used by /dev/ttyS0 (irq=4 io=0x3f8), I tried to change this, but I > can't do this at boot time, so I change to use /dev/ttyS1 instead of > ttyS0 (however the ttyS1 now are using the IRQ and IO from first > serial port although it is theorecaly the second serial device). Thanks for this info, Klaubert and Juerg. Apparently I see the same here: Until 2.6.21 I had this in dmesg: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A With 2.6.22 and built-in serial modules it changed to: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A That's ugly. With modular serial modules I see now: # setserial -G /dev/ttyS0 /dev/ttyS0 uart unknown port 0x0000 irq 0 baud_base 0 spd_normal # setserial -G /dev/ttyS1 /dev/ttyS1 uart unknown port 0x0000 irq 0 baud_base 0 spd_normal And any attempt to set these values to something useful only results in nasty error messages: # setserial -v /dev/ttyS0 port 0x3F8 irq 4 uart 16550A Cannot set serial info: Invalid argument # setserial -v /dev/ttyS1 port 0x3F8 irq 4 uart 16550A Cannot set serial info: Invalid argument I'm not using the serial ports at the moment (only for lirc_serial), so I didn't notice this, although Juerg asked whether the ports changed. Time to ask on lkml. Regards... Michael |