> -Original Message-
> From: Scott Wood [mailto:scottw...@freescale.com]
> Sent: Wednesday, September 22, 2010 1:00 AM
> To: Chen, Tiejun
> Cc: linuxppc-dev@lists.ozlabs.org; Guillaume Dargaud
> Subject: Re: Generating elf kernel ?
>
> On Tue, 21 Sep 2010 03:00:
On Tue, 21 Sep 2010 03:00:40 +0200
"Chen, Tiejun" wrote:
> This should be depend on the hypervisor design implementation. I think
> your
> option should be based on the Freescale hypervisor.
Again, I was giving an example, about ELF loading. I was not making any
claims about what all hyperviso
> -Original Message-
> From: Scott Wood [mailto:scottw...@freescale.com]
> Sent: Monday, September 20, 2010 11:44 PM
> To: Chen, Tiejun
> Cc: linuxppc-dev@lists.ozlabs.org; Guillaume Dargaud
> Subject: Re: Generating elf kernel ?
>
> On Sun, 19 Sep 2010 09:40
On Sun, 19 Sep 2010 09:40:15 +0800
"tiejun.chen" wrote:
> Scott Wood wrote:
> > On Fri, 17 Sep 2010 09:58:41 +0800
> > "tiejun.chen" wrote:
> >
> >> Scott Wood wrote:
> >>> The guest OS *is* the same as native Linux, as far as TLB handling is
> >>> concerned.
> >> Looks you means the TLB except
Scott Wood wrote:
> On Fri, 17 Sep 2010 09:58:41 +0800
> "tiejun.chen" wrote:
>
>> Scott Wood wrote:
>>> The guest OS *is* the same as native Linux, as far as TLB handling is
>>> concerned.
>> Looks you means the TLB exception handler should be same between the native
>> and
>> the guest OS. Rig
On Fri, 17 Sep 2010 09:58:41 +0800
"tiejun.chen" wrote:
> Scott Wood wrote:
> > The guest OS *is* the same as native Linux, as far as TLB handling is
> > concerned.
>
> Looks you means the TLB exception handler should be same between the native
> and
> the guest OS. Right?
Yes.
> Here I assum
Scott Wood wrote:
> On Thu, 16 Sep 2010 10:37:32 +0800
> "tiejun.chen" wrote:
>
>> 1> can you load the Linux vmlinux directly to the physical address '0' on
>> current bootloader?
>
> That depends on what bootloader we're talking about -- I don't know
> what the original poster's custom loader c
On Thu, 16 Sep 2010 10:37:32 +0800
"tiejun.chen" wrote:
> 1> can you load the Linux vmlinux directly to the physical address '0' on
> current bootloader?
That depends on what bootloader we're talking about -- I don't know
what the original poster's custom loader can do. Obviously the
bootloader
Guillaume Dargaud wrote:
Please use simpleImage..elf.
>>> Great, that seems to be it...
>>> Except that nothing happens when I jump to 0x4, no message from the
>> 0x4? I recalled the entry point should be 0x40 for
>> simepleImage.*.elf. So you have to change this on the file,
>> ar
> >> Please use simpleImage..elf.
> >
> > Great, that seems to be it...
> > Except that nothing happens when I jump to 0x4, no message from the
>
> 0x4? I recalled the entry point should be 0x40 for
> simepleImage.*.elf. So you have to change this on the file,
> arch/powerpc/boot/wrap
Guillaume Dargaud wrote:
>> Please use simpleImage..elf.
>
> Great, that seems to be it...
> Except that nothing happens when I jump to 0x4, no message from the
0x4? I recalled the entry point should be 0x40 for simepleImage.*.elf.
So you have to change this on the file, arch/powerpc
Scott Wood wrote:
> On Wed, 15 Sep 2010 16:27:10 +0800
> "tiejun.chen" wrote:
>
>> It's impossible to boot PPC vmlinux format directly if you only change the
>> original entry point address, 0xc000.
>
> Why? That's pretty much what the bootwrapper does. Our hypervisor has
> directly booted
On Wed, 15 Sep 2010 16:27:10 +0800
"tiejun.chen" wrote:
> It's impossible to boot PPC vmlinux format directly if you only change the
> original entry point address, 0xc000.
Why? That's pretty much what the bootwrapper does. Our hypervisor has
directly booted vmlinux this way.
Note that in
> Please use simpleImage..elf.
Great, that seems to be it...
Except that nothing happens when I jump to 0x4, no message from the
kernel, nothing.
I'm a bit stumped here as my old kernel worked fine.
--
Guillaume Dargaud
http://www.gdargaud.net/
___
Guillaume Dargaud wrote:
>>> How do I generate an elf file ?
>> vmlinux?
>
> Thanks.
>
> The entry point address has change and I can't upload it:
> New (bad) one:
> $ readelf -h vmlinux
> ...
> Entry point address: 0xc000
>
> Old (good) one:
> $ readelf -h zImage.elf
> ...
> > How do I generate an elf file ?
> vmlinux?
Thanks.
The entry point address has change and I can't upload it:
New (bad) one:
$ readelf -h vmlinux
...
Entry point address: 0xc000
Old (good) one:
$ readelf -h zImage.elf
...
Entry point address: 0x40
How
On Tue, Sep 14, 2010 at 10:53:11AM +0200, Guillaume Dargaud wrote:
> How do I generate an elf file ?
vmlinux?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozl
> Which bootloader? Looks you want to run it as XIP.
I have my own downloader which does a few things and then transfers the kernel
from a flash to the memory and then simply jumps to the 1st address with a
0x4() C function call.
But I need to first use Xilinx tools to transfer the kernel f
Guillaume Dargaud wrote:
> Hello all,
> In the past I've been using the PPC architecture to generate elf kernels (I
> wrote my own bootloader):
> $ file zImage.elf
> zImage.elf: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1
> (SYSV), statically linked, not stripped
>
> I'm now try
19 matches
Mail list logo
