From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Way for platforms to alter built-in serial ports
Date: Mon, 01 Nov 2004 17:15:48 +0000 [thread overview]
Message-ID: <1099329348.13633.2192.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20041006082919.B18379@flint.arm.linux.org.uk>
On Wed, 2004-10-06 at 08:29 +0100, Russell King wrote:
> The only reason it exists in its current form is because Alan says
> we can't get rid of the serial port initialisation due to the x86
> requirement for serial console to be initialised reasonably early.
>
> Unfortunately the early console stuff (afaik) never made it in to
> the kernel, so we've had to keep this hanging around.
>
> Maybe once this problem is solved we can consider dwmw2's suggestion.
Serial console working really early isn't just a requirement for x86.
It's useful elsewhere too.
The problem is that 'console=ttySx' doesn't actually do anything unless
port numer 'x' is already registered and working. We should fix that --
we ought to be able to use 'console=ttySx' on the command line and have
the console get registered with the core printk code later, when some
8250 sub-driver (8250_platform, 8250_pci, etc.) actually registers the
port which becomes number 'x'.
That would allow 'early' serial consoles to have none of the horrible
special-cased 'earlyconsole' crap -- we just call register_serial() (or
early_serial_setup() or whatever) as soon as it's actually possible to
poke at the port.
It also fixes the case of serial console on a PCI device.
--
dwmw2
next prev parent reply other threads:[~2004-11-01 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 16:14 Bjorn Helgaas
2004-09-30 23:53 ` Benjamin Herrenschmidt
2004-10-01 14:58 ` Bjorn Helgaas
2004-10-02 6:45 ` Benjamin Herrenschmidt
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 [this message]
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=1099329348.13633.2192.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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®