From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC83xx and uec
Date: Tue, 22 Sep 2009 18:14:04 +0400 [thread overview]
Message-ID: <20090922141404.GA8321@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <OFB70A48DB.A152D25D-ONC1257639.004C79E1-C1257639.004D342D@transmode.se>
On Tue, Sep 22, 2009 at 04:03:16PM +0200, Joakim Tjernlund wrote:
[...]
> > > > Also
> > > > drivers/qe/uec.h:int uec_initialize(bd_t *bis, uec_info_t *uec_info);
> > > > include/netdev.h:int uec_initialize(int index);
> > > > different prototypes for the same function.
> > >
> > > BTW, I am looking for a way to swap the order of ethernet interfaces:
> > > static uec_info_t uec_info[] = {
> > > #ifdef CONFIG_UEC_ETH1
> > > STD_UEC_INFO(1), /* UEC1 */
> > > #endif
> > > #ifdef CONFIG_UEC_ETH2
> > > STD_UEC_INFO(2), /* UEC2 */
> > > #endif
> > > #ifdef CONFIG_UEC_ETH3
> > > STD_UEC_INFO(3), /* UEC3 */
> > > #endif
> > > };
> >
> > Works for me:
> >
> > http://lists.denx.de/pipermail/u-boot/2009-September/060821.html
>
> Right, but I don't consider a include as this:
> +#include "../../../drivers/qe/uec.h"
> as the correct way of getting of required data types and macros.
> Consider that uec_initialize() is exported by netdev.h (although with the
> wrong prototype ATM). As far as I can tell, I should only have to include
> netdev.h to get the required types and macros.
Not sure if having all-in-one netdev header is a good idea.
It might be a good idea to move uec.h to "include/" though.
--
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-09-22 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 7:27 [U-Boot] MPC83xx and uec Joakim Tjernlund
2009-09-22 11:02 ` Joakim Tjernlund
2009-09-22 13:51 ` Anton Vorontsov
2009-09-22 14:03 ` Joakim Tjernlund
2009-09-22 14:14 ` Anton Vorontsov [this message]
2009-09-22 16:55 ` Ben Warren
2009-09-22 18:44 ` Joakim Tjernlund
2009-10-22 8:31 ` Joakim Tjernlund
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=20090922141404.GA8321@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.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