linux-next: kbuild tree build failure
Roman Zippel
zippel at linux-m68k.org
Fri Jul 11 00:59:25 EST 2008
Hi,
On Thu, 10 Jul 2008, Michael Ellerman wrote:
> Well yes :) But I think that's because you're thinking of
> "end-users" and I'm thinking of "users" like myself - ie. _I_ use
> Kconfig and I do expect myself to be able to type a 64-bit address.
That doesn't really answer my question, why you need this.
> > > --- .config.orig 2008-07-08 09:30:00.000000000 +1000
> > > +++ .config 2008-07-08 09:30:43.000000000 +1000
> > > @@ -370,9 +370,8 @@
> > > CONFIG_HOTPLUG_PCI_RPA=m
> > > CONFIG_HOTPLUG_PCI_RPA_DLPAR=m
> > > # CONFIG_HAS_RAPIDIO is not set
> > > -CONFIG_PAGE_OFFSET=0xc000000000000000
> > > -CONFIG_KERNEL_START=0xc000000002000000
> > > -CONFIG_PHYSICAL_START=0x02000000
> > > +CONFIG_PAGE_OFFSET=0xc0000000
> > > +CONFIG_PHYSICAL_START=0x2000000
> >
> > Why is this worse? These are constants, you're not supposed to change them
> > anyway.
> > The remaining values are generated in page.h and should be the same as
> > before. If that isn't the case and this patch produces a nonworking
> > kernel, I'd like to hear about it.
>
> You're right the built kernel is fine. So it's not a bug,
Good, could someone please ack whether the powerpc changes are acceptable?
> but I think it is nicer to have the real values in the .config.
Why?
bye, Roman
More information about the Linuxppc-dev
mailing list