Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] add support for xtensa back to buildroot
Date: Mon, 12 Nov 2012 12:23:07 -0800	[thread overview]
Message-ID: <50A15AAB.5020202@zankel.net> (raw)
In-Reply-To: <20121110115729.357ebfdd@skate>

On 11/10/2012 02:57 AM, Thomas Petazzoni wrote:
>> I've also seen that Qemu has an Xtensa support. It would be nice if you
>> could create a qemu_xtensa_<somemachine>_defconfig with the necessary
>> kernel configuration and al (see other qemu_<foo>_defconfig that we
>> have in configs/) so that other people could build a Xtensa userspace
>> and run it inside qemu. At the moment, the qemu-system-xtensa supports
>> the following machines:
>>
>> $ qemu-system-xtensa -M ?
>> Supported machines are:
>> none                 empty machine
>> lx60                 lx60 EVB (dc232b)
>> lx200                lx200 EVB (dc232b)
>> sim                  sim machine (dc232b) (default)
> Do you have any plans for proposing the support of a Qemu board using
> the Xtensa architecture? Qemu already supports 2-3 platforms, so it
> would be nice if Buildroot had a defconfig to generate a working system
> for one of them.
Yes, I'm planing to add support for QEMU, but it will probably take a
bit to understand it better before I have a config and maybe some patches.

Thanks,
-Chris

  reply	other threads:[~2012-11-12 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  3:38 [Buildroot] [PATCH 0/2] add support for xtensa back to buildroot Chris Zankel
2012-11-08  7:22 ` Thomas Petazzoni
2012-11-09  4:49   ` Chris Zankel
2012-11-09  8:14     ` Thomas Petazzoni
2012-11-10 10:57       ` Thomas Petazzoni
2012-11-12 20:23         ` Chris Zankel [this message]
2012-11-12 21:01           ` Thomas Petazzoni

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=50A15AAB.5020202@zankel.net \
    --to=chris@zankel.net \
    --cc=buildroot@busybox.net \
    /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