On 08/11/2015 12:58 PM, Joe Hershberger wrote:
> What ever became of this series?
I failed to ever email it in... I have a redone series, let me clean it
up and give it a quick test and make sure it works on latest... Needed
to rebase on about 10 months of upstream.
___
Hi Andrew,
On Mon, Oct 20, 2014 at 6:47 PM, Tom Rini wrote:
> On Mon, Oct 20, 2014 at 08:16:59PM +, Andrew Ruder wrote:
>> On 10/20/2014 03:00 PM, Tom Rini wrote:
>> > So, on new platforms we call dm9000_initialize with the right IO/DATA
>> > locations for the given device, yes? I think I'd
On Mon, Oct 20, 2014 at 08:16:59PM +, Andrew Ruder wrote:
> On 10/20/2014 03:00 PM, Tom Rini wrote:
> > 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 wa
On 10/20/2014 03:00 PM, Tom Rini wrote:
> 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.
The expectation is that
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 c
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 und
6 matches
Mail list logo
