David Miller wrote:
> From: Badari Pulavarty <[EMAIL PROTECTED]>
> Date: Fri, 29 Feb 2008 17:12:44 -0800
>
>
>> Here is what I cooked up and it seems to work fine.
>> It may be easier to review the code (against my earlier patches).
>>
>
> BTW, the lmb code now lives under lib/ (sparc64 wil
From: Badari Pulavarty <[EMAIL PROTECTED]>
Date: Fri, 29 Feb 2008 17:12:44 -0800
> Here is what I cooked up and it seems to work fine.
> It may be easier to review the code (against my earlier patches).
BTW, the lmb code now lives under lib/ (sparc64 will be using it too)
and has several bug fixe
On Fri, 2008-02-29 at 09:56 -0800, Badari Pulavarty wrote:
> Hi,
>
> I am wondering if you could give me your opinion on how to proceed
> (before I code too much).
>
> eHEA driver writers wants to know what the memory layout is - where the
> holes are and where the reserved memory is. They can ge
Hi,
I am wondering if you could give me your opinion on how to proceed
(before I code too much).
eHEA driver writers wants to know what the memory layout is - where the
holes are and where the reserved memory is. They can get this from
parsing through the device-tree every time, but it would be t
