LPARCFG

Will Schmidt willschm at us.ibm.com
Fri Feb 6 15:24:22 EST 2004


> > 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
>
> Ahh yeah, I have such a short memory.
>
> Actually I enabled it as a module and built all modules and didnt get
> any warnings. Either we have everything exported now, Im not getting
> undefined symbol warnings any more or else Im going blind.

I've got some more updates for this code, will try to get a patch onto this
list tomorrow.   (still need to forward port to current and check on
iSeries)..
I couldnt build it as a module without exporting a few symbols, but  my
tree is about a week old, so i'm probably missing those fixes.


-Will

willschm at us.ibm.com
Linux on PowerPC-64 Development
IBM Rochester


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





More information about the Linuxppc64-dev mailing list