From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Inject the Earlycon drivers into the decompressor
Date: Mon, 4 Jun 2012 09:47:46 +0100 [thread overview]
Message-ID: <20120604084746.GA8262@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120530224043.582229064@gmail.com>
On Thu, May 31, 2012 at 12:40:44AM +0200, Domenico Andreoli wrote:
> This linker voodoo clones the Earlycon drivers from the kernel into
> the decompressor, selecting everything in the designated ELF sections
> (.text.earlycon.info and .init.earlycon.info).
No, the debug stuff in the main kernel and the decompressor stuff can
(and is in some cases) different. There's a reason we have the two
implementations separate.
Moreover, these two things operate in two different address spaces; the
debug stuff in the kernel has to cope with the MMU being either on or
off, and use the kernel v:p mappings when the MMU is on. The decompressor
on the other hand has a 1:1 v:p mapping when the MMU is on - so it
would not be able to tell the difference if you just cloned the exact
same code.
One example of this would be RiscPC, where the decompressor writes to
the framebuffer, but the debug stuff writes to the serial port.
The preference is for the decompressor to write to the normal user visible
interface when possible, and the debug stuff to a serial port.
next prev parent reply other threads:[~2012-06-04 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 22:40 [RFC 0/6] RFC: ARM: Disintegrating mach/uncompress.h: low-level debug Domenico Andreoli
2012-05-30 22:40 ` [RFC 1/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Inject the Earlycon drivers into the decompressor Domenico Andreoli
2012-06-04 8:47 ` Russell King - ARM Linux [this message]
2012-06-04 23:34 ` Domenico Andreoli
2012-05-30 22:40 ` [RFC 2/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Add Earlycon support to " Domenico Andreoli
2012-05-30 22:40 ` [RFC 3/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Earlycon support for AMBA PL010 UARTs Domenico Andreoli
2012-05-30 22:40 ` [RFC 4/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Earlycon support for AMBA PL011 UARTs Domenico Andreoli
2012-05-30 22:40 ` [RFC 5/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Earlycon support for Samsung UARTs Domenico Andreoli
2012-05-30 22:40 ` [RFC 6/6] From: Domenico Andreoli <domenico.andreoli@linux.com> ARM: Earlycon support for OMAP UARTs Domenico Andreoli
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=20120604084746.GA8262@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).