From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 20 Oct 2014 16:00:16 -0400 Subject: [U-Boot] [PATCH 3/3 V2] dm9000: rework dm9000 to support multiple devices In-Reply-To: <1413828708-24729-1-git-send-email-andrew.ruder@elecsyscorp.com> References: <1413817185-32636-1-git-send-email-andrew.ruder@elecsyscorp.com> <1413828708-24729-1-git-send-email-andrew.ruder@elecsyscorp.com> Message-ID: <20141020200016.GS25506@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Oct 20, 2014 at 01:11:48PM -0500, Andrew Ruder wrote: > The DM9000 was hard-coded to only support one DM9000 device. This patch > adds a new initialization function - dm9000_initialize_ex() - to support > registering multiple (and possibly dynamic) numbers of dm9000 devices. > This patch consists of: > > * Change the board_info struct to a private struct under eth_device. > * Add io address/data address/srom availability information to this > private struct. > * Replace all uses of DM9000_IO/DM9000_DATA with new members, ensure > that the eth_device struct propagates down to all helper functions. > * Make dm9000_initialize() call dm9000_initialize_ex() with filled > in information from the old preprocessor symbols (DM9000_IO, > DM9000_DATA, etc.) So, on new platforms we call dm9000_initialize with the right IO/DATA locations for the given device, yes? I think I'd rather update everyone else to call things the right and new way, rather than work-around supporting both. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: