linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: 'kees schoenmakers' <kees3328@gmail.com>, linux-serial@vger.kernel.org
Subject: RE: TIOCSERGETLSR
Date: Wed, 11 Apr 2007 10:11:52 -0400	[thread overview]
Message-ID: <063201c77c43$5aeb1f80$294b82ce@stuartm> (raw)
In-Reply-To: <a754e89f0704110633m495d8fa3y433d925c6a0279c0@mail.gmail.com>

From: On Behalf Of kees schoenmakers
> I have noticed difference in return "value" of ioctl(port,
> TIOCSERGETLSR, &value) between different chips(hardware).
> Kernel is Linux version 2.6.20.4 (root@pc_develop02.fluidwell.local)
> (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP
> PREEMPT Fri Apr 6 13:41:02 CEST 2007 (build from source)
> My mobo is from recent date and has an on-board serial port (ttyS0).
> An extra PCI board with 2 serial ports is added:
> 07:00.0 Serial controller: NetMos Technology PCI 9835 
> Multi-I/O Controller (rev 01) (prog-if 02 [16550])

If this
http://www.moschip.com/html/MCS9835.html
is your board, the data sheet is
http://www.moschip.com/data/products/NM9835/Data%20Sheet_9835.pdf

I looked it over quickly. The UART is contained within a chip they
make. The LSR looks good from the documentation. **

> My application uses a simplex modem connection over the low-speed
> serial port, therefore I need to know for sure that all chararcters
> have been written out before changing over from xmit to receive. I use
> the TIOCSERGETLSR to check if this is the case. My problem is that for
> the on board serial port the ioctl returns that situation OK but it is
> wrong for the 9835 ports. There the TIOCSERGETLSR returns empty almost
> after the first/second character is written which is not correct
> (verified with scope). It may be a bug in the 9835 controller.  Do
> others have similar findings?

** I don't have one of these boards, but I'm suspecting a hardware
error as well, based on your description. (I'm assuming that you do
see the proper bits go high briefly, and then go off too quickly.)

I'd try contacting the OEM or Moschip.

..Stu

-- 
We make multiport serial products.
http://www.connecttech.com/
(800) 426-8979


      reply	other threads:[~2007-04-11 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 13:33 TIOCSERGETLSR kees schoenmakers
2007-04-11 14:11 ` Stuart MacDonald [this message]

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='063201c77c43$5aeb1f80$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=kees3328@gmail.com \
    --cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).