Glauber de Oliveira Costa wrote:
Dor Laor wrote:
> Glauber de Oliveira Costa wrote:
>>
>> Currently, the -kernel option is not working.
>>
>> Reason is, because we're registering chunks for regions 0-0xa and
>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>> The real fix should be to
Dor Laor wrote:
> Glauber de Oliveira Costa wrote:
>>
>> Currently, the -kernel option is not working.
>>
>> Reason is, because we're registering chunks for regions 0-0xa and
>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>> The real fix should be to rewrite all the load_linux() code t
Glauber de Oliveira Costa wrote:
> Currently, the -kernel option is not working.
>
> Reason is, because we're registering chunks for regions 0-0xa and
> 0x10-ram_size, the phys_ram_addr + PA is broken.
> The real fix should be to rewrite all the load_linux() code to not rely
> on this, but
Dor Laor wrote:
> Glauber de Oliveira Costa wrote:
>>
>> Currently, the -kernel option is not working.
>>
>> Reason is, because we're registering chunks for regions 0-0xa and
>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>> The real fix should be to rewrite all the load_linux() code t
Glauber de Oliveira Costa wrote:
Currently, the -kernel option is not working.
Reason is, because we're registering chunks for regions 0-0xa and
0x10-ram_size, the phys_ram_addr + PA is broken.
The real fix should be to rewrite all the load_linux() code to not rely
on this, but meanwhil
Anthony Liguori wrote:
> Glauber de Oliveira Costa wrote:
>
>> Currently, the -kernel option is not working.
>>
>> Reason is, because we're registering chunks for regions 0-0xa and
>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>>
>>
>
> I think this patch is a reasonable wo
On Dec 7, 2007 7:38 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Izik Eidus wrote:
> > Anthony Liguori wrote:
> >> Glauber de Oliveira Costa wrote:
> >>
> >>> Currently, the -kernel option is not working.
> >>>
> >>> Reason is, because we're registering chunks for regions 0-0xa and
> >>> 0x
Anthony Liguori wrote:
> Izik Eidus wrote:
>> Anthony Liguori wrote:
>>> Glauber de Oliveira Costa wrote:
>>>
Currently, the -kernel option is not working.
Reason is, because we're registering chunks for regions 0-0xa and
0x10-ram_size, the phys_ram_addr + PA is broken
Izik Eidus wrote:
> Anthony Liguori wrote:
>> Glauber de Oliveira Costa wrote:
>>
>>> Currently, the -kernel option is not working.
>>>
>>> Reason is, because we're registering chunks for regions 0-0xa and
>>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>>>
>>
>> I think this
Glauber de Oliveira Costa wrote:
> Currently, the -kernel option is not working.
>
> Reason is, because we're registering chunks for regions 0-0xa and
> 0x10-ram_size, the phys_ram_addr + PA is broken.
> The real fix should be to rewrite all the load_linux() code to not rely
> on this, but
Anthony Liguori wrote:
> Glauber de Oliveira Costa wrote:
>
>> Currently, the -kernel option is not working.
>>
>> Reason is, because we're registering chunks for regions 0-0xa and
>> 0x10-ram_size, the phys_ram_addr + PA is broken.
>>
>>
>
> I think this patch is a reasonable wo
Glauber de Oliveira Costa wrote:
> Currently, the -kernel option is not working.
>
> Reason is, because we're registering chunks for regions 0-0xa and
> 0x10-ram_size, the phys_ram_addr + PA is broken.
>
I think this patch is a reasonable work-around but the long term
solution is proba
Currently, the -kernel option is not working.
Reason is, because we're registering chunks for regions 0-0xa and
0x10-ram_size, the phys_ram_addr + PA is broken.
The real fix should be to rewrite all the load_linux() code to not rely
on this, but meanwhile, filling in the gap up to 0xc
13 matches
Mail list logo