LKML Archive on
help / color / mirror / Atom feed
From: Rob Prowel <>
To: Rob Prowel <>,,
Subject: Re: questions about 8250 uart support for adhoc boards
Date: Fri, 23 Feb 2007 15:48:27 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks so much for your followup.

Russell King wrote:
> On Fri, Feb 23, 2007 at 12:05:48PM -0500, Rob Prowel wrote:
>> At least now, with fourport compiled into the kernel,
> You don't even need to do that.  Just configure SERIAL_8250_NR_UARTS
> and SERIAL_8250_RUNTIME_UARTS appropriately for your system.  There's
> absolutely no need to build any of the additional modules.
Unfortunately what I'm seeing in seems to differ from this.  If 
I use the options below:

# CONFIG_SERIAL_8250_FOURPORT is not set
# CONFIG_SERIAL_8250_ACCENT is not set
# CONFIG_SERIAL_8250_BOCA is not set
# CONFIG_SERIAL_8250_EXAR_ST16C554 is not set
# CONFIG_SERIAL_8250_HUB6 is not set
# Non-8250 serial port support

Then I can only access ttyS0 through ttyS3 sith setserial.  Only after I add
CONFIG_SERIAL_8250_FOURPORT=y am I actually able to do anything with the 
additional ports.  I would otherwise get the evil setserial: invalid 
parameter error.

If you'd like I can offline you my complete .config file.  lemme know.

>> I can use 
>> setserial to see the uarts and correctly identify them...but the shared 
>> interrupt vector doesn't seem to work.  I haven't even attempted yet to 
>> try stty or echoing data our to an o-scope.
> I dropped support for the shared interrupt vector - having multiple
> different ISRs depending on the way the wind was blowing was extremely
> complex, and in this day and age of GHz CPUs rather silly.
> The serial driver can still share interrupts just fine.  Just omit
> configuring the multiport address and masks.

OK.  Fair enough.  My question then becomes, how does the driver deal 
with this now? scan all applicable uarts when any relevant interrupt is 
detected (as identified in setserial)?


  reply	other threads:[~2007-02-23 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 17:05 questions about 8250 uart support for adhoc boards Rob Prowel
2007-02-23 20:21 ` Russell King
2007-02-23 20:48   ` Rob Prowel [this message]
2007-02-24 20:34     ` Stuart MacDonald
2007-02-26 17:02       ` Rob Prowel
2007-02-26 18:05         ` Russell King
2007-02-27 14:24           ` Rob Prowel
2007-02-27 17:38             ` Russell King
2007-02-27 19:06               ` Stuart MacDonald
2007-02-27 20:40                 ` Rob Prowel
2007-03-08 15:16                   ` 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:

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

  git send-email \ \ \ \ \

* 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).