mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: n0ano@n0ano.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: donald.d.dugger@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enable console on PCI serial devices
Date: Tue, 14 Oct 2008 17:04:32 -0600	[thread overview]
Message-ID: <20081014230432.GA14490@xolotl.n0ano.com> (raw)
In-Reply-To: <20081014235317.398c0a1a@lxorguk.ukuu.org.uk>

Alan-

Wait off a bit.  YH pointed out that early printk (I should have checked
that) already has be ability to specify a I/O address.  All I need to do
is enhance the early printk code to specify a clock frequency, I should
have that patch ready shortly.

I was kind of torn between specifying the frequency vs. the max baud rate
and went with the frequency on the off chance that some weird HW might
come out that needs a different multiplier.  I figured anybody who needs
to specify the number can do the appropriate arithmetic.

On Tue, Oct 14, 2008 at 11:53:17PM +0100, Alan Cox wrote:
> > F is the flow control, III is the I/O port address (prefix with 0x for
> > hexadecimal) and CCC is the crystal frequency.  -III and /CCC are optional
> > and can be omitted although -III must be specified if you want to set
> > /CCC.  For example, the option I use is:
> 
> I am sure real men would compute the equivalent baud rate for the clock by
> hand ;) This looks a sensible patch, will queue.
> 
> Now I wonder if uart_parse_options can be __init 
> 
> Alan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@n0ano.com
Ph: 303/443-3786

  reply	other threads:[~2008-10-14 23:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 22:31 donald.d.dugger
2008-10-14 22:39 ` Yinghai Lu
2008-10-14 23:30   ` n0ano
2008-10-15  9:13     ` Paul Bolle
2008-10-15 20:48       ` n0ano
2008-10-16 10:43         ` Paul Bolle
2008-10-16 16:23           ` Yinghai Lu
2008-10-16 17:12             ` n0ano
2008-10-16 18:19               ` Yinghai Lu
2008-10-16 18:25                 ` n0ano
2008-10-16 18:30                   ` Yinghai Lu
2008-10-16 18:57                     ` n0ano
2008-10-17  2:45                     ` n0ano
2008-10-17  3:32                       ` Yinghai Lu
2008-10-17 16:05                         ` n0ano
2008-10-17 17:01                           ` Yinghai Lu
2008-10-14 22:53 ` Alan Cox
2008-10-14 23:04   ` n0ano [this message]
2008-10-16 23:16 ` Bjorn Helgaas
2008-10-17  2:39   ` n0ano
2008-10-17  9:28     ` Alan Cox
2008-10-17 14:11       ` n0ano
2008-10-17 14:46         ` Bjorn Helgaas
2008-10-17 15:36           ` n0ano
2008-10-17 16:39             ` Bjorn Helgaas
2008-10-17 17:06               ` n0ano
2008-10-20 16:44                 ` Lennart Sorensen
2008-10-20 17:11                   ` Bjorn Helgaas
2008-10-20 17:43                     ` n0ano
2008-10-20 19:11                       ` Bjorn Helgaas
2008-10-21 20:08                         ` n0ano
2008-10-21 22:08                           ` Bjorn Helgaas
2008-10-21 22:33                             ` n0ano
2008-10-17 14:44     ` Bjorn Helgaas

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=20081014230432.GA14490@xolotl.n0ano.com \
    --to=n0ano@n0ano.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=donald.d.dugger@intel.com \
    --cc=linux-kernel@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 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®