Message-ID: <40600CDD.5050807@pop2wap.net>
Date: Tue, 23 Mar 2004 11:09:33 +0100
From: Christof <mail@pop2wap.net>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: synchronous serial port communication (16550A)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1776
Lines: 39

Hello,

I have a possible problem with the 8250 serial port driver in linux (2.6.2).
I communicate with a graphic controller with LCD-Display via ttyS0. This
controller has a small buffer: 20 bytes. When the buffer is full it
asserts the CTS line. When it can receive data again, the CTS line is
cleared.
My software checks the CTS line each time before sending a byte. If it
is asserted, it waits until its cleared and goes on. When data is sent
although CTS is asserted, the graphic controller will be confused and
garbage will appear on the LCD screen.

To make the story short: I see a lot of garbage on the LCD.
It looks like output would be buffered and all data would be sent at
once without giving me the possibility to check if everything's
allright. Sometimes I can send >400 Bytes and ioctl says that CTS is not
asserted, altough it certainly is. What I need is totally synchronous
I/O. I want all bytes to be sent physically before I check for CTS, but
I can't find a possibility to actually achieve this. I tried to hack the
driver not to use the FIFO (My Linux box has a 16550A UART) and to set
the size of the circ buffer to 1, but nothing helped.
I compiled my software for cygwin for my Windows-machine and it worked,
the only thing is that I don't know what UART is build in, but i suppose
that it also has a FIFO since it is a quite new machine. (The FIFO is
also enabled in windows too).

Do you have any idea what I could do?

Thanks in advance and sorry for the messy english =)

Regards,
  Christof Krueger


-
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/