Hi,


quoted text
>> I'd recommend splitting prom.c into code that can be shared between powerpc
>> and microblaze and architecture specific code. Anything that deals with
>> LMB should go into powerpc, and you can simply use the alloc_bootmem
>> mechanism for your architecture.
> 
> That is non trivial... the unflatten DT code among others relies heavily
> on the LMB's to allocate the objects.
> 
> We could split the early accessors, unflatten code, and kernel-side
> accessors at one point, though we already did most of it no ?
> 
> Ben.

I look at latest LMB version currenty in lib folder. There is some changes which
I think go against version.

I would like to ask some question about.

in include/asm-powerpc/lmb.h is written LMB_REAL_LIMIT.

Is this real limit memory limit? Why I ask. I think powerpc start with main
memory from zero address and you can set your high limit from zero. In this case
is high limit equal to size of memory.

In Microblaze systems we don't have main memory from zero. Starting point can be
everywhere in 2^32.

I hope I can avoid in this constant in MB system and only direct start and size
mem with DTS description. Am I right?

The similar code was added to of files which are in arch/powerpc/kernel/ folder.
I would like to fix LMB and OF together.

I have some fixed around coding style violation. I'll send them ASAP.

I don't have any idea what files use Sparc. Can you inform me about? I don't
want to break something with MB port.

Thanks for info.

Regards,
Michal Simek
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/