public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Remove board specific code from ENC28J60 network driver?
Date: Mon, 21 Dec 2009 08:17:51 -0500	[thread overview]
Message-ID: <200912210817.54003.vapier@gentoo.org> (raw)
In-Reply-To: <4B2F311E.8020905@googlemail.com>

On Monday 21 December 2009 03:26:06 Dirk Behme wrote:
> - Which is the 'the common SPI framework'? Files?

include/spi.h ... just grep for files that include it and you'll find a bunch 
of examples in the tree.

> - Just for correct understanding: We are talking about two issues
> here? The first issue is that enc28j60.c has board specific code, for
> e.g. setting GPIOs (as shown above)? And the second issue is that it
> doesn't use common SPI framework? Correct?

when i read the driver, i couldnt tell how much the spi was bound to the 
board, but if things can be separated that way, then sure.

for the board init issue, a driver that has been converted to NET_MULTI means 
that it provides a hook for boards to call (enc28j60_register()).  then in the 
board-specific hook (board_eth_init()), you do all the board-specific stuff 
and then call enc28j60_register().

the README.driver.eth should explain it
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20091221/47b867c4/attachment.pgp 

  reply	other threads:[~2009-12-21 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 19:30 [U-Boot] Remove board specific code from ENC28J60 network driver? Dirk Behme
2009-12-20 19:54 ` Ben Warren
2009-12-20 20:05 ` Mike Frysinger
2009-12-21  8:26   ` Dirk Behme
2009-12-21 13:17     ` Mike Frysinger [this message]
2009-12-25 18:57   ` Dirk Behme
2009-12-26 18:40     ` Mike Frysinger
2009-12-27  7:59       ` Dirk Behme
2009-12-27 15:32         ` Ben Warren
2009-12-27 18:55           ` Dirk Behme
2009-12-28 18:33             ` Mike Frysinger
2009-12-28 21:29             ` Ben Warren

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=200912210817.54003.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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