diff options
author | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2013-07-25 04:12:32 +0200 |
---|---|---|
committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2013-08-14 06:57:40 +0200 |
commit | 7191b615759ec10cab9eea43be5ecc42cda82364 (patch) | |
tree | 48e96713113f5c8a54a7021d0dd5bc6b31d32f15 /drivers | |
parent | powerpc/pci: Remove duplicate check in pcibios_fixup_bus() (diff) | |
download | linux-7191b615759ec10cab9eea43be5ecc42cda82364.tar.xz linux-7191b615759ec10cab9eea43be5ecc42cda82364.zip |
powerpc/pmac: Early debug output on screen on 64-bit macs
We have a bunch of CONFIG_PPC_EARLY_DEBUG_* options that are intended
for bringup/debug only. They hard wire a machine specific udbg backend
very early on (before we even probe the platform), and use whatever
tricks are available on each machine/cpu to be able to get some kind
of output out there early on.
So far, on powermac with no serial ports, we have CONFIG_PPC_EARLY_DEBUG_BOOTX
to use the low-level btext engine on the screen, but it doesn't do much, at
least on 64-bit. It only really gets enabled after the platform has been
probed and the MMU enabled.
This adds a way to enable it much earlier. From prom_init.c (while still
running with Open Firmware), we grab the screen details and set things up
using the physical address of the frame buffer.
Then btext itself uses the "rm_ci" feature of the 970 processor (Real
Mode Cache Inhibited) to access it while in real mode.
We need to do a little bit of reorg of the btext code to inline things
better, in order to limit how much we touch memory while in this mode as
the consequences might be ... interesting.
This successfully allowed me to debug problems early on with the G5
(related to gold being broken vs. ppc64 kernels).
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions