From: "Donald" <donald@asix.com.tw>
To: 'Alan Cox' <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: RE: Questions regarding adding a patch in linux/drivers/char/8250.c
Date: Mon, 21 May 2012 20:54:58 +0800 [thread overview]
Message-ID: <00b701cd3750$f09ced60$d1d6c820$@com.tw> (raw)
In-Reply-To: <20120521103009.7f4be5e0@pyramind.ukuu.org.uk>
Hi Alan,
Thank you for your quick reply and nice questions. We will have an internal discussion regarding your questions and then I will
reply to your questions as soon as possible.
Regards,
Donald
-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: Monday, May 21, 2012 5:30 PM
To: Donald
Cc: linux-serial@vger.kernel.org
Subject: Re: Questions regarding adding a patch in linux/drivers/char/8250.c
On Mon, 21 May 2012 14:19:34 +0800
"Donald" <donald@asix.com.tw> wrote:
> Hi,
>
> This is Donald from ASIX Electronics Corp. My company has three PCI to Serial controllers, including MCS9845, MCS9835, and
MCS9820.
> Currently those serial devices using these three chips can directly
> use the Linux kernel's serial driver in linux/drivers/char/8250.c.
> Recently we find these three chips have a hardware bug relating to parity error count function. We have a software workaround for
this issue. Below for reference is a pseudo code for this workaround.
Actually I have a second question.
Would it not be better to set the device to 8N1 and do the parity in software rather than lose the FIFO, especially at higher speeds
? Can you clarify what the erratum is triggered by ?
Alan
next prev parent reply other threads:[~2012-05-21 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:19 Questions regarding adding a patch in linux/drivers/char/8250.c Donald
2012-05-21 9:28 ` Alan Cox
2012-05-29 8:37 ` Donald
2012-06-18 3:07 ` Donald
2012-06-19 9:18 ` Alan Cox
2012-06-19 12:35 ` Donald
2012-05-21 9:30 ` Alan Cox
2012-05-21 12:54 ` Donald [this message]
2012-05-21 15:07 ` Jason Smith
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='00b701cd3750$f09ced60$d1d6c820$@com.tw' \
--to=donald@asix.com.tw \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.