From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org,
"Edgar E. Iglesias" <edgar.iglesias@petalogix.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] microblaze: Allow targeting little-endian mb
Date: Tue, 1 Mar 2011 22:25:33 +0100 [thread overview]
Message-ID: <20110301212533.GA7509@laped.lan> (raw)
In-Reply-To: <AANLkTi=+Ce+5sHxqixhx5DbtyCXNixi+WHuo9wFL8N9b@mail.gmail.com>
On Fri, Feb 25, 2011 at 05:15:57PM +0200, Blue Swirl wrote:
> On Mon, Feb 21, 2011 at 3:44 PM, Edgar E. Iglesias
> <edgar.iglesias@petalogix.com> wrote:
> > Signed-off-by: Edgar E. Iglesias <edgar.iglesias@petalogix.com>
> > ---
> > configure | 7 +++++--
> > default-configs/microblazeel-linux-user.mak | 1 +
> > default-configs/microblazeel-softmmu.mak | 4 ++++
> > 3 files changed, 10 insertions(+), 2 deletions(-)
> > create mode 100644 default-configs/microblazeel-linux-user.mak
> > create mode 100644 default-configs/microblazeel-softmmu.mak
> >
> > diff --git a/configure b/configure
> > index 791b71d..3036faf 100755
> > --- a/configure
> > +++ b/configure
> > @@ -984,6 +984,7 @@ arm-softmmu \
> > cris-softmmu \
> > m68k-softmmu \
> > microblaze-softmmu \
> > +microblazeel-softmmu \
> > mips-softmmu \
> > mipsel-softmmu \
> > mips64-softmmu \
> > @@ -1008,6 +1009,7 @@ armeb-linux-user \
> > cris-linux-user \
> > m68k-linux-user \
> > microblaze-linux-user \
> > +microblazeel-linux-user \
> > mips-linux-user \
> > mipsel-linux-user \
> > ppc-linux-user \
> > @@ -3005,7 +3007,8 @@ case "$target_arch2" in
> > target_long_alignment=2
> > target_llong_alignment=2
> > ;;
> > - microblaze)
> > + microblaze|microblazeel)
> > + TARGET_ARCH=microblaze
> > bflt="yes"
> > target_nptl="yes"
> > target_phys_bits=32
> > @@ -3231,7 +3234,7 @@ for i in $ARCH $TARGET_BASE_ARCH ; do
> > echo "CONFIG_M68K_DIS=y" >> $config_target_mak
> > echo "CONFIG_M68K_DIS=y" >> $libdis_config_mak
> > ;;
> > - microblaze)
> > + microblaze*)
> > echo "CONFIG_MICROBLAZE_DIS=y" >> $config_target_mak
> > echo "CONFIG_MICROBLAZE_DIS=y" >> $libdis_config_mak
> > ;;
> > diff --git a/default-configs/microblazeel-linux-user.mak b/default-configs/microblazeel-linux-user.mak
> > new file mode 100644
> > index 0000000..566fdc0
> > --- /dev/null
> > +++ b/default-configs/microblazeel-linux-user.mak
> > @@ -0,0 +1 @@
> > +# Default configuration for microblaze-linux-user
>
> microblazeel-linux-user?
>
> > diff --git a/default-configs/microblazeel-softmmu.mak b/default-configs/microblazeel-softmmu.mak
> > new file mode 100644
> > index 0000000..4399b8b
> > --- /dev/null
> > +++ b/default-configs/microblazeel-softmmu.mak
> > @@ -0,0 +1,4 @@
> > +# Default configuration for microblaze-softmmu
>
> microblazeel-softmmu?
Thanks, I've corrected the copy+paste:o..
Cheers
prev parent reply other threads:[~2011-03-01 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 13:44 [Qemu-devel] [PATCH 1/2] pls3adsp1800: Base load_elf endianness on target endianness Edgar E. Iglesias
2011-02-21 13:44 ` [Qemu-devel] [PATCH 2/2] microblaze: Allow targeting little-endian mb Edgar E. Iglesias
2011-02-25 15:15 ` Blue Swirl
2011-03-01 21:25 ` Edgar E. Iglesias [this message]
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=20110301212533.GA7509@laped.lan \
--to=edgar.iglesias@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@petalogix.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).