public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul B Schroeder <pschroeder@uplogix.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Exar quad port serial
Date: Wed, 18 Oct 2006 10:07:03 -0500	[thread overview]
Message-ID: <45364317.7020908@uplogix.com> (raw)
In-Reply-To: <20061018133430.GU30991@csclub.uwaterloo.ca>



Lennart Sorensen wrote:
> On Tue, Oct 17, 2006 at 08:00:17PM -0500, Paul B Schroeder wrote:
>> Sorry for the late response..  Here is a fuller explanation.  Maybe 
>> somebody out there has a better solution:
>>
>> This is on our "Envoy" boxes which we have, according to the documentation, 
>> an "Exar ST16C554/554D Quad UART with 16-byte Fifo's".  The box also has 
>> two other "on-board" serial ports and a modem chip.
>>
>> The two on-board serial UARTs were being detected along with the first two 
>> Exar UARTs.  The last two Exar UARTs were not showing up and neither was 
>> the modem.
>>
>> This patch was the only way I could the kernel to see beyond the standard 
>> four serial ports and get all four of the Exar UARTs to show up.
>>
>> I hope this explains it well enough..
> 
> I suspect all you have to do might be to change how many ports it looks
> for.  The default max ports is 4 I believe on many kernel versions.
> 
> Look for CONFIG_SERIAL_8250_NR_UARTS and
> CONFIG_SERIAL_8250_RUNTIME_UARTS in the kernel config.
> 
Yea..  I tried that..  It had no effect..

> If that doesn't work and you do need a special driver, at least label it
> with more detail like 'for exar st16c554 quad uart' or 'for envoy board'
> or whatever makes it clear which hardware it is for.  I use exar pci
> uarts (exar XR17d15[248] chips) which work fine already with the 8250
> driver, or optionally with the jsm driver with a small change to the
> list if pci identifiers.  THey of course would not work with your driver
> since they are completely different exar chips (even though one is also
> a quad uart, although 64byte fifo).
In that case, I will redo the patch with better labeling..

Thanks...Paul...



-- 
---

Paul B Schroeder <pschroeder "at" uplogix "dot" com>
Senior Software Engineer
Uplogix, Inc. (http://www.uplogix.com/)


  reply	other threads:[~2006-10-18 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:13 [PATCH] Exar quad port serial Paul B Schroeder
2006-10-05 17:36 ` Lennart Sorensen
2006-10-18  1:00   ` Paul B Schroeder
2006-10-18 13:34     ` Lennart Sorensen
2006-10-18 15:07       ` Paul B Schroeder [this message]
2006-10-22 20:30       ` Paul B Schroeder
2006-10-23  4:24         ` Paul B Schroeder

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=45364317.7020908@uplogix.com \
    --to=pschroeder@uplogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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