diff for duplicates of <20140921204100.GA10111@linutronix.de> diff --git a/a/1.txt b/N1/1.txt index 79edbe3..f521170 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -32,7 +32,7 @@ shell responded with "\r\n" which I see and then nothing more. less isn't sending data for some reason. Exactly the same thing happens in a Debian environment except that it continues: -… +? | bash-2468 [000] d.h. 99.657899: serial8250_tx_chars: put 0a | bash-2468 [000] d.h. 99.658089: serial8250_handle_irq: iir c2 lsr 60 | bash-2468 [000] d.h. 99.658095: serial8250_tx_chars: empty @@ -46,15 +46,15 @@ thing happens in a Debian environment except that it continues: It has to be something about the environment. Booting Debian and chroot into this RFS and less works perfectly. But since it behaves like that -with both drivers, I guess the problem is somewhere else… +with both drivers, I guess the problem is somewhere else? > vi runs normally, only occupies part of the total screen estate in > minicom. After quitting, a weird character shows up (typically I see -> ÿ there), but minicom can use the rest of the screen estate again. +> ? there), but minicom can use the rest of the screen estate again. > If we disregard the odd character, this is much like the behavior we > have on the omap-serial driver. >- Custom board: Yocto poky, custom image -> Login, "less file" locks up, showing only "ÿ" in the top left corner +> Login, "less file" locks up, showing only "?" in the top left corner > of the screen. Can get out of there by having something dumped through > /dev/kmsg. @@ -79,7 +79,3 @@ complete then it seems that the TX-DMA stall does not tall anymore. >Frans Sebastian --- -To unsubscribe from this list: send the line "unsubscribe linux-serial" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 32c1345..7599672 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,20 +8,10 @@ "ref\020140912102816.GF28458@ci00147.xsens-tech.local\0" "ref\0541716DC.9020904@linutronix.de\0" "ref\020140917102812.GA20438@ci00147.xsens-tech.local\0" - "From\0Sebastian Andrzej Siewior <bigeasy@linutronix.de>\0" - "Subject\0Re: [PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx\0" + "From\0bigeasy@linutronix.de (Sebastian Andrzej Siewior)\0" + "Subject\0[PATCH 09/16] tty: serial: 8250_dma: Add a TX trigger workaround for AM33xx\0" "Date\0Sun, 21 Sep 2014 22:41:00 +0200\0" - "To\0Frans Klaver <frans.klaver@xsens.com>\0" - "Cc\0Heikki Krogerus <heikki.krogerus@linux.intel.com>" - Peter Hurley <peter@hurleysoftware.com> - tony@atomide.com - gregkh@linuxfoundation.org - linux-kernel@vger.kernel.org - balbi@ti.com - linux-serial@vger.kernel.org - linux-omap@vger.kernel.org - linux-arm-kernel@lists.infradead.org - " Alan Cox <alan@linux.intel.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "* Frans Klaver | 2014-09-17 12:28:12 [+0200]:\n" @@ -58,7 +48,7 @@ "\n" "nothing more. less isn't sending data for some reason. Exactly the same\n" "thing happens in a Debian environment except that it continues:\n" - "\342\200\246\n" + "?\n" "| bash-2468 [000] d.h. 99.657899: serial8250_tx_chars: put 0a\n" "| bash-2468 [000] d.h. 99.658089: serial8250_handle_irq: iir c2 lsr 60\n" "| bash-2468 [000] d.h. 99.658095: serial8250_tx_chars: empty\n" @@ -72,15 +62,15 @@ "\n" "It has to be something about the environment. Booting Debian and chroot\n" "into this RFS and less works perfectly. But since it behaves like that\n" - "with both drivers, I guess the problem is somewhere else\342\200\246\n" + "with both drivers, I guess the problem is somewhere else?\n" "\n" "> vi runs normally, only occupies part of the total screen estate in\n" "> minicom. After quitting, a weird character shows up (typically I see\n" - "> \303\277 there), but minicom can use the rest of the screen estate again.\n" + "> ? there), but minicom can use the rest of the screen estate again.\n" "> If we disregard the odd character, this is much like the behavior we\n" "> have on the omap-serial driver.\n" ">- Custom board: Yocto poky, custom image\n" - "> Login, \"less file\" locks up, showing only \"\303\277\" in the top left corner\n" + "> Login, \"less file\" locks up, showing only \"?\" in the top left corner\n" "> of the screen. Can get out of there by having something dumped through\n" "> /dev/kmsg.\n" "\n" @@ -104,10 +94,6 @@ ">Hope this helps. Thanks for your effort so far,\n" ">Frans\n" "\n" - "Sebastian\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-serial\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Sebastian -a43a9492490af2538fcbb8d475771d981b51f9a62bfb972be2ed6c0c566c0b9c +7f32024eeb3325c777b62559941b10b3ab1a707c6444aa43231048309e2ce504
diff --git a/a/1.txt b/N2/1.txt index 79edbe3..6c3023b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -79,7 +79,3 @@ complete then it seems that the TX-DMA stall does not tall anymore. >Frans Sebastian --- -To unsubscribe from this list: send the line "unsubscribe linux-serial" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 32c1345..89dd902 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -104,10 +104,6 @@ ">Hope this helps. Thanks for your effort so far,\n" ">Frans\n" "\n" - "Sebastian\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-serial\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Sebastian -a43a9492490af2538fcbb8d475771d981b51f9a62bfb972be2ed6c0c566c0b9c +f85525d1c5568f7b6de97455e15e35daf49f95db18a34de99e6566f6ef8e94d9
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.