public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Way for platforms to alter built-in serial ports
Date: Sat, 02 Oct 2004 16:45:50 +1000	[thread overview]
Message-ID: <1096699550.11996.24.camel@gaston> (raw)
In-Reply-To: <200410010858.27390.bjorn.helgaas@hp.com>

On Sat, 2004-10-02 at 00:58, Bjorn Helgaas wrote:

> My main point is that I think the early init stuff (i.e.,
> serial8250_isa_init_ports()) should go away, so we don't have the
> dichotomy of having the compiled-in stuff handled differently than
> the run-time enumerated stuff.

Right. But that's a long term goal ;)

> It really doesn't matter for ia64, since we discover all the ports
> via either PCI enumeration or ACPI.  We don't put anything in
> old_serial_port[] at all.  For platforms that can't do that,
> there'd still have to be compiled-in tables, but the entries
> should be added using the standard register_serial() interface
> just like everything else.

I discover everything at boot time via Open Firmware, though on
ppc32, embedded platforms have gazillion different ways of getting
to them.

> > In the meantime, that patch would fix urgent problems for ppc now so
> > I'd appreciate if Russell would consider it for inclusion asap. This
> > is the kind of subject on which everybody comes up with a different
> > "better" way to do it and no code, and nothign ever gets implemented
> > and we end up with no progress...
> 
> We've both posted working code that are at least baby steps toward
> a better solution, so I hope we can make some progress.

Yes. Well, I suppose having a 8250_ppc{64}.c where I do the discovery
a bit like it's done with ACPI would be ok for everything but serial
console... I can do an OF plaform device that gets probed a bit late
though, and that wouldn't help for embedded stuffs, but then, those
people can always still use the hard coded table for a while ... :)

That would mean though having the kernel serial console for early boot
be separate from the 8250 driver... like you proposed. That would work
too... I have to ponder this approach, indeed probably better than
my patch provided you get your early uart stuff upstream :)

Ben.



  reply	other threads:[~2004-10-02  6:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 16:14 [RFC][PATCH] Way for platforms to alter built-in serial ports Bjorn Helgaas
2004-09-30 23:53 ` Benjamin Herrenschmidt
2004-10-01 14:58   ` Bjorn Helgaas
2004-10-02  6:45     ` Benjamin Herrenschmidt [this message]
2004-10-06  7:32     ` Russell King
2004-10-06 19:54       ` Bjorn Helgaas
2004-10-08 19:49         ` Bjorn Helgaas
2004-10-06  7:29 ` Russell King
2004-10-06 19:47   ` Bjorn Helgaas
2004-11-01 17:15   ` David Woodhouse
2004-11-02 16:39     ` Bjorn Helgaas
2004-11-03  7:43       ` Russell King
2004-11-03 12:07         ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30  8:50 Benjamin Herrenschmidt
2004-10-06  7:26 ` Russell King
2004-10-06  8:15   ` Benjamin Herrenschmidt
2004-10-06  9:07   ` Benjamin Herrenschmidt

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=1096699550.11996.24.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=bjorn.helgaas@hp.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