mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Martin Diehl <lists@mdiehl.de>
Subject: Re: [Serial 2.5]: packet drop problem (FE ?)
Date: Fri, 8 Nov 2002 00:18:22 +0000	[thread overview]
Message-ID: <20021108001822.E11437@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021107224750.GA699@bougret.hpl.hp.com>; from jt@bougret.hpl.hp.com on Thu, Nov 07, 2002 at 02:47:50PM -0800

On Thu, Nov 07, 2002 at 02:47:50PM -0800, Jean Tourrilhes wrote:
> 	I tried swapping the IrDA dongles themselves, and this didn't
> make any difference. No other device/driver is using irq4. I also try
> using a FIR as a sender, and I still see this packet dropped in Rx in
> 2.5.X. And this used to work properly way back when I had 2.4.X on
> this box.
> 	I'm kind of suspicious about the "fe" number above. Could
> anybody tell me a bit more about what "fe" means ?

FE = framing error, which is an error which is solely detected by the
hardware when the stop bit(s) are not the mark value.  They can appear
when the wrong parity setting, number of stop bits, or baud rate is
programmed.

If you were overruning the serial port FIFOs, then you would see "oe"
errors.

What baud rate are you trying to run the link at?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-11-08  0:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 22:47 Jean Tourrilhes
2002-11-08  0:18 ` Russell King [this message]
2002-11-08  0:41   ` Jean Tourrilhes
2002-11-08  0:49     ` Russell King
2002-11-08  0:55       ` Jean Tourrilhes
2002-11-08  2:40       ` Jean Tourrilhes
2002-11-08 22:34         ` Martin Diehl
2002-11-08 23:25           ` Russell King

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=20021108001822.E11437@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mdiehl.de \
    /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

all inboxes | Powered by JetHome®