From: chen huacai <zltjiangshi@gmail.com>
To: Stefan Weil <weil@mail.berlios.de>
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: Mon, 10 May 2010 19:21:31 +0800 [thread overview]
Message-ID: <AANLkTim0ICUCKawRlPgWGH_57udqWxVnd9Gd8KNci9--@mail.gmail.com> (raw)
In-Reply-To: <4BE68342.2020202@mail.berlios.de>
>> --- a/hw/mips.h
>> +++ b/hw/mips.h
>> @@ -5,6 +5,9 @@
>> /* gt64xxx.c */
>> PCIBus *pci_gt64120_init(qemu_irq *pic);
>>
>> +/* bonito.c */
>> +PCIBus *bonito_init_2e(qemu_irq pic);
>> +
>> /* ds1225y.c */
>> void *ds1225y_init(target_phys_addr_t mem_base, const char *filename);
>> void ds1225y_set_protection(void *opaque, int protection);
>> -----
>>
>
> Please see my annotations above.
>
> Kind regards,
> Stefan Weil
>
Hi, Stefan, do you means that I should do something like this?
#ifdef CONFIG_FULONG
/* bonito.c */
PCIBus *bonito_init_2e(qemu_irq pic);
#endif
I found that even if I put CONFIG_FULONG=y in
default-configs/mips64el-softmmu.mak, CONFIG_FULONG will not get
defined in config-target.h.
Because CONFIG_FULONG=y will appear config-device.mak, but not
config-target.mak.
Could you please give me some suggestions?
--
Huacai Chen
next prev parent reply other threads:[~2010-05-10 11:21 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
2010-05-10 11:21 ` chen huacai [this message]
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=AANLkTim0ICUCKawRlPgWGH_57udqWxVnd9Gd8KNci9--@mail.gmail.com \
--to=zltjiangshi@gmail.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).