Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Elvis Dowson <elvis.dowson@gmail.com>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: QEMU with ARM Cortex A9 with hard float configuration - Kernel panic
Date: Mon, 26 Aug 2013 15:08:59 -0400	[thread overview]
Message-ID: <521BA7CB.7070206@windriver.com> (raw)
In-Reply-To: <6324D287-2CA2-4A88-AFF4-58CABE82B2CC@gmail.com>

On 13-08-26 11:49 AM, Elvis Dowson wrote:
> Hi Bruce,
>
> On Aug 26, 2013, at 8:24 AM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>
>> Perhaps the zynq machine definition is the right way to go, since nearly
>> enough support is mainline (in both qemu and the kernel), and we can
>> motivate the rest into their respective upstreams.
>>
>> If someone can come up the right conf files, and machine definition, I
>> can pretty easily support it in linux-yocto.
>
> Could you tell me what's steps I need to follow, to add a new machine
> definition and support to the linux-yocto kernel?

Are you interested in something from scratch, versus something that
isn't already partially in the tree (like qemuarma9) ?

We've got a few docs and tutorials, but I can also help step you through
the process to assist the existing material.

Bruce

>
> I'd like to learn how to do this!
>
> Best regards,
>
> Elvis Dowson
>



  reply	other threads:[~2013-08-26 19:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25 17:43 QEMU with ARM Cortex A9 with hard float configuration - Kernel panic rewitt
2013-08-25 18:02 ` Elvis Dowson
2013-08-25 18:31   ` Elvis Dowson
2013-08-25 19:09     ` Elvis Dowson
2013-08-26  1:03       ` Bruce Ashfield
2013-08-26  3:58         ` Elvis Dowson
2013-08-26  4:24           ` Bruce Ashfield
2013-08-26 15:49             ` Elvis Dowson
2013-08-26 19:08               ` Bruce Ashfield [this message]
2013-08-26 19:35                 ` Elvis Dowson
2013-08-27 20:03                   ` Bruce Ashfield
2013-08-28 15:16                     ` Elvis Dowson
2013-08-28 22:43                       ` Bruce Ashfield
2013-08-29  4:36                         ` Elvis Dowson
2013-08-29  5:48                           ` Khem Raj
2013-08-29  8:50                             ` Elvis Dowson
2013-08-29 16:17                               ` Khem Raj
2013-08-29 16:18                                 ` Bruce Ashfield
2013-08-29 16:22                                 ` Elvis Dowson
2013-08-29 12:35                           ` Bruce Ashfield
2013-08-29 14:02                             ` Elvis Dowson
2013-08-29 16:23                               ` Bruce Ashfield
2013-08-29 16:28                                 ` Elvis Dowson
2013-08-26  1:11   ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2013-08-29 19:32 rewitt
2013-08-29 19:40 ` Bruce Ashfield
2013-08-30 10:17 ` Elvis Dowson
2013-08-29 18:53 rewitt
2013-08-29 18:58 ` Bruce Ashfield
2013-08-29 19:01 ` Elvis Dowson
2013-08-29 19:16   ` Bruce Ashfield
2013-08-29 19:25     ` Elvis Dowson
2013-08-29 19:30       ` Bruce Ashfield
2013-08-25 14:37 Elvis Dowson
2013-08-25 14:44 ` Martin Jansa
2013-08-25 15:09   ` Elvis Dowson

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=521BA7CB.7070206@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=elvis.dowson@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox