All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: chen huacai <zltjiangshi@gmail.com>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [RFC][MIPS][PATCH 1/6] Initial support of bonito north bridge used by fulong mini pc
Date: Sun, 09 May 2010 21:04:17 +0200	[thread overview]
Message-ID: <4BE70731.40302@mail.berlios.de> (raw)
In-Reply-To: <u2v69475c4c1005090425qdb14b61dif4e2764258031c3e@mail.gmail.com>

Am 09.05.2010 13:25, schrieb chen huacai:
>>>  obj-mips-y += mips_addr.o mips_timer.o mips_int.o
>>>  obj-mips-y += dma.o vga.o i8259.o
>>>  obj-mips-y += g364fb.o jazz_led.o
>>> -obj-mips-y += gt64xxx.o pckbd.o mc146818rtc.o
>>> +obj-mips-y += gt64xxx.o bonito.o pckbd.o mc146818rtc.o
>>>
>>
>> Is fulong 64 bit only?
>>
>> Maybe it would be better to add a new CONFIG_FULONG to
>> default-configs/mips64-softmmu.mak and 
>> default-configs/mips64el-softmmu.mak
>> and then use obj-mips-$(CONFIG_FULONG) here and in the other patches.
>>
>
> fulong support both 32/64 bit software, but only support
> little-endian, so I think I need to add CONFIG_FULONG to
> default-configs/mipsel-softmmu.mak and
> default-configs/mips64el-softmmu.mak.


The cpu core is Loongson with 64 bit, isn't it?
So default-configs/mips64el-softmmu.mak should be sufficient.

Of course mips64el-softmmu can run 32 bit software, too.

Kind regards,
Stefan Weil

  reply	other threads:[~2010-05-09 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09  2:00 [Qemu-devel] [RFC][MIPS][PATCH 1/6] Initial support of bonito north bridge used by fulong mini pc chen huacai
2010-05-09  9:41 ` Stefan Weil
2010-05-09 11:25   ` chen huacai
2010-05-09 19:04     ` Stefan Weil [this message]
2010-05-10 11:21   ` chen huacai
2010-05-10 17:19     ` Stefan Weil
2010-05-09  9:56 ` Stefan Weil
2010-05-10  4:02   ` yajin
2010-05-10 19:14 ` Blue Swirl
2010-05-11  2:32   ` chen huacai
2010-05-11 19:52     ` Blue Swirl
2010-05-12  0:59       ` chen huacai
2010-05-12  7:37       ` yajin

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=4BE70731.40302@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=zltjiangshi@gmail.com \
    /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.