In message <[EMAIL PROTECTED]> you wr
ote:
> On Tue, Aug 19, 2008 at 12:25 AM, Becky Bruce <[EMAIL PROTECTED]> wro
te:
> >
> > On Aug 18, 2008, at 3:51 PM, Michael Neuling wrote:
> >
> >> In message <[EMAIL PROTECTED]>
> >> you wrote:
> >>>
> >>> The mmu is still disabled at this point.
> >>>
> >>>
In message <[EMAIL PROTECTED]> you wrote:
> Michael Neuling wrote:
> >> It seems like no one else is interested in the subject, so i will talk
> >> directly to you.
> >>
> >> If you say that the cpu also seg faults, it means that the problem is
> >> in the code of the linux kernel... :)
> >
> > So
Michael Neuling wrote:
It seems like no one else is interested in the subject, so i will talk
directly to you.
If you say that the cpu also seg faults, it means that the problem is
in the code of the linux kernel... :)
Sorry, I was only joking. The hardware does _not_ segfault. There is
no e
> It seems like no one else is interested in the subject, so i will talk
> directly to you.
>
> If you say that the cpu also seg faults, it means that the problem is
> in the code of the linux kernel... :)
Sorry, I was only joking. The hardware does _not_ segfault. There is
no equivalent to seg
On Tue, Aug 19, 2008 at 12:25 AM, Becky Bruce <[EMAIL PROTECTED]> wrote:
>
> On Aug 18, 2008, at 3:51 PM, Michael Neuling wrote:
>
>> In message <[EMAIL PROTECTED]>
>> you wrote:
>>>
>>> The mmu is still disabled at this point.
>>>
>>> What is marked as readonly is the text section of the vmlinux f
On Aug 18, 2008, at 3:51 PM, Michael Neuling wrote:
In message <[EMAIL PROTECTED]
> you wrote:
The mmu is still disabled at this point.
What is marked as readonly is the text section of the vmlinux file
generated when compiling the kernel. And since the code tries to
write
to the text sect
In message <[EMAIL PROTECTED]> you wrote:
> The mmu is still disabled at this point.
>
> What is marked as readonly is the text section of the vmlinux file
> generated when compiling the kernel. And since the code tries to write
> to the text section, I assumed it was the reason for the segmentati
The mmu is still disabled at this point.
What is marked as readonly is the text section of the vmlinux file
generated when compiling the kernel. And since the code tries to write
to the text section, I assumed it was the reason for the segmentation
fault.
I'm not sure how this is dealt with on re
In message <[EMAIL PROTECTED]> you wrote:
> Hello,
>
> First, I'm talkin about the 2.6.11 version. I know arch/ppc is gone in
> latest versions,
> but i assume the code is still the same and just moved to powerpc.
>
> There is a piece of code in the early initialization of the 2.6 kernel
> that i
Hello,
First, I'm talkin about the 2.6.11 version. I know arch/ppc is gone in
latest versions,
but i assume the code is still the same and just moved to powerpc.
There is a piece of code in the early initialization of the 2.6 kernel
that identifies the cpu type and then tries to eliminate code th
10 matches
Mail list logo
