LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Rob Prowel <prowel@kuchera.com>
Cc: Stuart MacDonald <stuartm@connecttech.com>, linux-kernel@vger.kernel.org
Subject: Re: questions about 8250 uart support for adhoc boards
Date: Thu, 8 Mar 2007 15:16:12 +0000	[thread overview]
Message-ID: <20070308151612.GD30023@flint.arm.linux.org.uk> (raw)
In-Reply-To: <45E49759.6050301@kuchera.com>

On Tue, Feb 27, 2007 at 03:40:57PM -0500, Rob Prowel wrote:
> Stuart MacDonald wrote:
> >Would it be more intuitive to give ports the default uartclk of
> >1843200 at init time? That would avoid this issue, but would make the
> >baud rates come out wrong on hardware with a non-standard clock, if a
> >base baud wasn't specified.
> >
> >  
> 
> I prefer the option to specify the base baud rate in setserial from a 
> startup script.  Having the additional ports at BAUD 0 (unusable) until 
> some explicit action is taken strikes me as a safer option, provided 
> this gets properly documented in the kernel Documentation directory and 
> in Linux HOWTO docs.

Is someone going to do that?  Who volunteers?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

      reply	other threads:[~2007-03-08 15:16 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
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 [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=20070308151612.GD30023@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prowel@kuchera.com \
    --cc=stuartm@connecttech.com \
    /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).