From: Andrew Ruder <andrew.ruder@elecsyscorp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 0/5] DM9000 support for multiple interfaces
Date: Wed, 12 Aug 2015 17:50:24 +0000 [thread overview]
Message-ID: <55CB875F.5030105@elecsyscorp.com> (raw)
In-Reply-To: <1439400246-20472-1-git-send-email-andrew.ruder@elecsyscorp.com>
On 08/12/2015 12:24 PM, Andrew Ruder wrote:
> To maintain backwards compatibility with older board files, we add a
> new initialize function taking the io address, data address, and
> availability of a SROM chip. The old initialize function is now a
> shim around this new initialize function but provides the parameters
> based on the old DM9000 preprocessor symbols.
Uh, this is not true. Forgot to remove this paragraph from the cover
letter. There is just a single dm9000_initialize() function that has
been updated in every board file.
prev parent reply other threads:[~2015-08-12 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:24 [U-Boot] [PATCH V2 0/5] DM9000 support for multiple interfaces Andrew Ruder
2015-08-12 17:24 ` [U-Boot] [PATCH V2 1/5] dm9000: whitespace cleanups Andrew Ruder
2015-08-12 19:07 ` Joe Hershberger
2015-08-12 17:24 ` [U-Boot] [PATCH V2 2/5] dm9000: mark dump_regs() function as unused Andrew Ruder
2015-08-12 19:07 ` Joe Hershberger
2015-08-12 17:24 ` [U-Boot] [PATCH V2 3/5] dm9000: Add struct eth_device * to SROM functions Andrew Ruder
2015-08-12 19:07 ` Joe Hershberger
2015-08-21 11:25 ` Andrew Ruder
2015-08-21 15:56 ` Joe Hershberger
2015-08-12 17:24 ` [U-Boot] [PATCH V2 4/5] dm9000: dm9000_initialize stub Andrew Ruder
2015-08-12 19:07 ` Joe Hershberger
2015-08-16 0:51 ` Marcel Ziswiler
2015-08-16 1:15 ` Marcel Ziswiler
2015-08-12 17:24 ` [U-Boot] [PATCH V2 5/5] dm9000: rework dm9000 to support multiple devices Andrew Ruder
2015-08-12 19:07 ` Joe Hershberger
2015-08-12 17:50 ` Andrew Ruder [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=55CB875F.5030105@elecsyscorp.com \
--to=andrew.ruder@elecsyscorp.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.