From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC][PATCH 1/1] Add board_eth_init() function
Date: Wed, 26 Mar 2008 10:15:20 -0400 [thread overview]
Message-ID: <47EA5A78.1000804@gmail.com> (raw)
In-Reply-To: <20080326134131.6f13fec0@hskinnemo-gx620.norway.atmel.com>
Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 20:39:26 +0900
> Shinya Kuribayashi <skuribay@ruby.dti.ne.jp> wrote:
>
>
>> I just thought that, a header file full of driver-specific declarations,
>> is somewhat ugly.
>>
>
> The functions must be declared somewhere, but declaring them at the
> callsite is not only ugly, but error-prone as well.
>
> One alternative might be to add one header file per driver and put the
> declarations there. Maybe we should add a include/netdev directory for
> network driver-specific header files?
>
> Haavard
>
>
No, I like the way I did it with a single header file for all
interfaces. It's not ugly - externs in every board file or a directory
of tiny header files or the existing #ifdef mess is ugly. One header
file means one-stop-shopping for finding a controller's interface. The
only thing that might be better is to #include netdev.h in common.h,
getting rid of the requirement to include it in each board file. OTOH,
cascading header files is itself an ugly practice. In an entirely
biased way, I think the way I've implemented this is a big improvement
over the status quo and should make things easier going forward.
regards,
Ben
next prev parent reply other threads:[~2008-03-26 14:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 2:46 [U-Boot-Users] [RFC][PATCH 1/1] Add board_eth_init() function Ben Warren
2008-03-22 5:03 ` Shinya Kuribayashi
[not found] ` <f8328f7c0803220505n39c9ddb5sf9c9cf037b8f4665@mail.gmail.com>
2008-03-22 12:07 ` Ben Warren
2008-03-22 15:55 ` Vlad Lungu
2008-03-23 6:19 ` Shinya Kuribayashi
2008-03-26 10:00 ` Haavard Skinnemoen
2008-03-26 11:39 ` Shinya Kuribayashi
2008-03-26 12:41 ` Haavard Skinnemoen
2008-03-26 14:15 ` Ben Warren [this message]
2008-03-26 14:27 ` Haavard Skinnemoen
2008-03-22 6:31 ` Stefan Roese
2008-03-22 9:59 ` Wolfgang Denk
2008-03-22 10:14 ` Stefan Roese
2008-03-22 11:35 ` Markus Klotzbücher
2008-03-22 14:01 ` Wolfgang Denk
2008-03-22 15:43 ` Ben Warren
2008-03-25 7:04 ` Stefan Roese
2008-03-25 11:11 ` Ben Warren
2008-03-25 14:22 ` Ben Warren
2008-03-25 14:41 ` Joakim Tjernlund
2008-03-25 14:57 ` Ben Warren
2008-03-25 15:31 ` Joakim Tjernlund
2008-03-25 15:56 ` Jerry Van Baren
2008-03-25 16:59 ` Joakim Tjernlund
2008-03-25 14:43 ` Stefan Roese
2008-03-25 16:17 ` Andy Fleming
2008-03-25 16:33 ` Stefan Roese
2008-03-25 17:04 ` Andy Fleming
2008-03-25 17:53 ` Ben Warren
2008-03-26 10:06 ` Haavard Skinnemoen
2008-03-26 10:14 ` Stefan Roese
2008-03-26 10:25 ` Haavard Skinnemoen
2008-03-26 10:34 ` Stefan Roese
2008-03-26 11:06 ` Haavard Skinnemoen
2008-03-26 11:43 ` Stefan Roese
2008-03-26 12:19 ` Haavard Skinnemoen
2008-03-26 12:39 ` Stefan Roese
2008-03-23 0:06 ` [U-Boot-Users] [OT] Using MTD to manipulate CFI flash on PCI boards? David Hawkins
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=47EA5A78.1000804@gmail.com \
--to=biggerbadderben@gmail.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 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.