LPARCFG

[Nathan Lynch]

Anton Blanchard wrote:
> Hi,
>
> Any reason we cant make lparcfg tristate (so we can compile it as a
> module?)

Building as a module was broken when the code was checked in to ameslab
2.6; I suggested turning it off.  I think lparcfg uses unexported
symbols -- cur_cpu_spec, systemcfg, and plpar_hcall_4out.  Should any of
those be exported?

See this thread for the history:
http://lists.linuxppc.org/linuxppc64-dev/200312/msg00023.html

Nathan

** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/