From: Shinya Kuribayashi <skuribay@pobox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] qemu_mips: Fix CONFIG_NET_MULTI build warning
Date: Tue, 20 Oct 2009 08:59:02 +0900 [thread overview]
Message-ID: <4ADCFD46.4080508@pobox.com> (raw)
In-Reply-To: <4ADC96B2.9030305@gmail.com>
Hi Ben,
Ben Warren wrote:
> Shinya Kuribayashi wrote:
>> First. I'm not sure why CONFIG_NET_MULTI is "undef"ed for qemu_mips,
>> while CONFIG_DRIVER_NE2000 has been enabled for qemu_mips at an early
>> stage.
>>
>> I don't follow recent changes around eth.c and CONFIG_NET_MULTI, but
>> it's probably CONFIG_NET_MULTI used to be used strictly for multi
>> ports, isn't it?
>>
> Currently, there are two incompatible networking APIs. One that uses
> CONFIG_NET_MULTI, and one that doesn't. I'm trying to move everything
> towards the former (single-port applications are of course a degenerate
> instance of multi-port ones). Once all drivers have been ported to the
> MULTI API, that config option will magically disappear.
Thanks, got it.
>> Next. As far as looking at drivers/net/ne2000*.[ch], NE2000 driver
>> doesn't seem to require board_eth_init() or cpu_eth_init(). Right?
>> Therefore I've not added a corresponding hook in board/qemu_mips/
>> qemu_mips.c. If my understanding is wrong, please let me know.
>>
> The NE2000 driver hasn't been ported yet. It's on my short term to-do
> list, and will be in the next release (01.2010, I guess?)
So CONFIG_NE2000_DRIVER needs some work, and is not ready for
migration. I missed that point, thanks for clarification.
>> @@ -157,7 +157,7 @@
>>
>> #define CONFIG_ENV_OVERWRITE 1
>>
>> -#undef CONFIG_NET_MULTI
>> +#define CONFIG_NET_MULTI
>>
>>
> This won't do anything other than disabling networking. Since QEMU is
> an emulator, though, maybe it would make sense to use a device driver
> that has CONFIG_NET_MULTI support?
Who knows? It's hard, at least for me, to say. But it'd be better to
port NE2000 driver into an appropriate shape whether it's used by QEMU
or not.
>> #define MEM_SIZE 128
>>
>>
> If the warning isn't more than a nuisance, please live with it for now.
No problem. Please ignore the patch.
Thanks,
Shinya
prev parent reply other threads:[~2009-10-19 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 13:04 [U-Boot] [PATCH] qemu_mips: Fix CONFIG_NET_MULTI build warning Shinya Kuribayashi
2009-10-19 16:41 ` Ben Warren
2009-10-19 23:59 ` Shinya Kuribayashi [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=4ADCFD46.4080508@pobox.com \
--to=skuribay@pobox.com \
--cc=u-boot@lists.denx.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