netdev
[Top] [All Lists]

Re: [RFR] gianfar ethernet driver

To: Andy Fleming <afleming@xxxxxxxxxxxxx>
Subject: Re: [RFR] gianfar ethernet driver
From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
Date: Mon, 19 Jul 2004 21:13:29 -0400
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>, Andy Fleming <AFLEMING@xxxxxxxxxxxx>, netdev@xxxxxxxxxxx, Kumar Gala <kumar.gala@xxxxxxxxxxxx>, hadi@xxxxxxxxxx, rmk@xxxxxxxxxxxxxxxx, benh@xxxxxxxxxxxxxxxxxxx
In-reply-to: <85DC52B0-D9DB-11D8-AE55-000393C30512@xxxxxxxxxxxxx>
References: <C681B01E-CEA9-11D8-931F-000393DBC2E8@xxxxxxxxxxxxx> <2A724364-D53A-11D8-8835-000393C30512@xxxxxxxxxxxxx> <40F4A6E5.4060000@xxxxxxxxx> <85DC52B0-D9DB-11D8-AE55-000393C30512@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 2004-07-19 at 18:29 -0500, Andy Fleming wrote:
> > I could have sworn OCP does struct device these days.  If not, poke 
> > the platform people.
> 
> Ah, I found it.  ocpdev->dev.  Done.

So we have BenH talking about pre-populating sysfs with objects for all
the on-chip peripherals and metadata like MAC addresses. We have some
PPC platforms using 'OCP' which does much the same thing, and ARM
platforms using yet another implementation. Some drivers support more
than one of these.

I suspect we need to bash some heads together... :)

-- 
dwmw2


<Prev in Thread] Current Thread [Next in Thread>