diff options
author | Michael Ellerman <mpe@ellerman.id.au> | 2014-06-24 17:17:47 +1000 |
---|---|---|
committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2014-06-25 13:10:47 +1000 |
commit | e2500be2b801f4e95d6a1efbc50af3bf14eeb940 (patch) | |
tree | 6bf8042001b33d55bf08927cfa5d0b7a2355b050 /drivers/tty | |
parent | a1d23d5c94256ffa0de510a3d59d6eff551d97ae (diff) | |
download | linux-e2500be2b801f4e95d6a1efbc50af3bf14eeb940.tar.gz linux-e2500be2b801f4e95d6a1efbc50af3bf14eeb940.tar.bz2 linux-e2500be2b801f4e95d6a1efbc50af3bf14eeb940.zip |
powerpc/powernv: Remove OPAL v1 takeover
In commit 27f4488872d9 "Add OPAL takeover from PowerVM" we added support
for "takeover" on OPAL v1 machines.
This was a mode of operation where we would boot under pHyp, and query
for the presence of OPAL. If detected we would then do a special
sequence to take over the machine, and the kernel would end up running
in hypervisor mode.
OPAL v1 was never a supported product, and was never shipped outside
IBM. As far as we know no one is still using it.
Newer versions of OPAL do not use the takeover mechanism. Although the
query for OPAL should be harmless on machines with newer OPAL, we have
seen a machine where it causes a crash in Open Firmware.
The code in early_init_devtree() to copy boot_command_line into cmd_line
was added in commit 817c21ad9a1f "Get kernel command line accross OPAL
takeover", and AFAIK is only used by takeover, so should also be
removed.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'drivers/tty')
0 files changed, 0 insertions, 0 deletions