All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Questions about the name of qemu bin file for different archs
Date: Tue, 14 Dec 2010 09:46:57 -0500	[thread overview]
Message-ID: <4D078361.2040301@windriver.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D3065973313A6A37@shsmsx501.ccr.corp.intel.com>

On 10-12-14 02:40 AM, Ke, Liping wrote:
> Hi, Jessica
>
> I found qemu bin file name convention is different for different archs, for example, for x86, it is bzImage-qemuXXX.
> For arm, it is zImage-qemuXXX. My question is why it is bzXXX or zXXX, is there any reason of such naming convention?

The leading part of the image name is dependent
on the type of kernel we are booting.

]> grep KERNEL_IMAGETYPE qemu*
qemuarm.conf:KERNEL_IMAGETYPE = "zImage"
qemumips.conf:KERNEL_IMAGETYPE = "vmlinux"
qemumips-variant.conf:KERNEL_IMAGETYPE = "vmlinux"
qemuppc.conf:KERNEL_IMAGETYPE = "zImage"
qemux86-64.conf:KERNEL_IMAGETYPE = "bzImage"
qemux86.conf:KERNEL_IMAGETYPE = "bzImage"

And those are your differences in the name.

As for why the symlinks may not be created at times, I'm
not sure.

>
> Or I must did name translate for each kind of arch qemu bin file?

Should be something you can script by checking the
KERNEL_IMAGETYPE.

Cheers,

Bruce

>
>
> Thanks&  Regards,
> criping
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  parent reply	other threads:[~2010-12-14 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14  7:40 Questions about the name of qemu bin file for different archs Ke, Liping
2010-12-14  7:50 ` Ke, Liping
2010-12-14 14:46 ` Bruce Ashfield [this message]
2010-12-22  6:38   ` Ke, Liping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D078361.2040301@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=liping.ke@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.