public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Leonard <ian@smallworld.cx>
To: linux-kernel@vger.kernel.org
Subject: Serial port problem
Date: Tue, 04 Apr 2006 14:32:36 +0100	[thread overview]
Message-ID: <44327574.1030803@smallworld.cx> (raw)

Hi,

The trouble started when I upgraded a machine from FC3 to FC4. It had a 
serial touchscreen. With FC4 it stopped working completely. I added 
debug to the X input driver and found read() permanently blocked despite 
the file having been opened with O_NDELAY.

I then tried a simple test with two machine connected with a serial 
cable and using minicom to send characters both ways. One was a laptop. 
If you typed from the failing machine to the laptop all was well. Typing 
the other way caused one character to be displayed and then it hung 
(although I could use 'cat >/dev/ttyS0' to send data just fine).

I then repeated the test using 4 different motherboards. 2 exhibited the 
problem 2 didn't. So to recap, sending data without changing the driver 
settings (stty) seems to work. Configuring the port seems to cause a 
problem on some motherboards. One of those is a VIA mini-itx. The other 
is more standard Gigabyte.

I have tried using the standard FC4 kernel and 2.6.15.6.

Not sure what to try next, so any pointer gratefully received.


-- 
Ian Leonard

Please ignore spelling and punctuation - I did.

             reply	other threads:[~2006-04-04 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 13:32 Ian Leonard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-01 11:29 serial port problem Dmitry Melekhov
2008-11-01 11:54 ` Adam Nielsen
2002-02-26 13:07 Serial Port problem Vinayak P Risbud

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44327574.1030803@smallworld.cx \
    --to=ian@smallworld.cx \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox