On Mon, 18 Jun 2007 11:33:54 +0100 Russell King wrote: > On Mon, Jun 18, 2007 at 01:21:21PM +0300, Ivan Kuten wrote: > > Hi Haavard, > > > > I tried /dev/ttyAT3, break appeared but not the way I expected, after: > > stty -F /dev/ttyAT3 brkint I get: > > > > cat /proc/tty/driver/atmel_serial > > serinfo:1.0 driver revision: > > 0: uart:ATMEL_SERIAL mmio:0xFEFFF200 irq:1 tx:0 rx:0 CTS|DSR|CD|RI > > 1: uart:ATMEL_SERIAL mmio:0xFFFC0000 irq:6 tx:0 rx:0 CTS|DSR|CD|RI > > > > 2: uart:ATMEL_SERIAL mmio:0xFFFC4000 irq:7 tx:0 rx:0 RI > > > > 3: uart:ATMEL_SERIAL mmio:0xFFFC8000 irq:8 tx:1530 rx:115 brk:1 > > RTS|DTR|DSR|CD|RI > > 4: uart:ATMEL_SERIAL mmio:0xFFFCC000 irq:9 tx:0 rx:0 DSR|CD|RI > > > > brk is 1 not depending on how many breaks was sent. May be I missunderstood > > "break" meaning? > > I use from minicom: Main Functions : send break.........F . > > Note that if you want to use magic sysrq on ttyAT3, you need the kernel > console on ttyAT3. Since you successfully received one break event on > ttyAT3, the next character should have caused a sysrq event. >
Yes, I added to kernel command line "console=ttyAT3,115200" . I do not receive brk event via minicom, break counter sets to 1 only if I issue this command: stty -F /dev/ttyAT3 brkint Anyway I try to debug further to locate the problem. BR, Ivan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
