Hi, I upgraded my linux system to 2.6.36. Now suddenly my serial driver for my MSF receiver stopped working. Two things I noticed: I need to open the serial device (/dev/ttyS0, a regular uart, see below) with O_NDELAY for open() to return at all. Then something funny happens: I read bytes from the device (at 50bps) which runs fine for a while but then suddenly I get a burst of '0x00' bytes - precisely at the point at which the MSF radio device sends a timecode! So I think the device fiddles with one of the pins of the serial port confusing the linux serial driver. This worked fine upto and including 2.6.25 (maybe later too) but with 2.6.36 this fails. Anyone an idea what might go wrong here? And how to fix it? The sourcecode of my driver can be found here: http://vanheusden.com/lpc-ntpd/lindy_precision_clock.php [ 0.826110] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.596509] 0000:04:06.0: ttyS0 at I/O 0xbf00 (irq = 20) is a 16550A [ 2.617685] 0000:04:06.0: ttyS1 at I/O 0xbe00 (irq = 20) is a 16550A weerstationserver:/usr/local/src/lpc-ntpd-1.0.1.hacked# setserial -a -g /dev/ttyS0 /dev/ttyS0, Line 0, UART: 16550A, Port: 0xbf00, IRQ: 20 Baud_base: 115200, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal skip_test Folkert van Heusden -- Nagios user? Check out CoffeeSaint - the versatile Nagios status viewer! http://www.vanheusden.com/java/CoffeeSaint/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
