netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andy Fleming <afleming@freescale.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Andy Fleming <AFLEMING@motorola.com>,
	netdev@oss.sgi.com, Kumar Gala <kumar.gala@motorola.com>,
	hadi@cyberus.ca, rmk@arm.linux.org.uk, benh@kernel.crashing.org
Subject: Re: [RFR] gianfar ethernet driver
Date: Mon, 19 Jul 2004 21:13:29 -0400	[thread overview]
Message-ID: <1090286009.4149.12.camel@localhost.localdomain> (raw)
In-Reply-To: <85DC52B0-D9DB-11D8-AE55-000393C30512@freescale.com>

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

  reply	other threads:[~2004-07-20  1:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C681B01E-CEA9-11D8-931F-000393DBC2E8@freescale.com>
     [not found] ` <89563A5C-CFAE-11D8-BA44-000393C30512@freescale.com>
2004-07-07  3:18   ` [RFR] gianfar ethernet driver jamal
2004-07-07  3:29     ` Jeff Garzik
2004-07-07  3:41       ` jamal
2004-07-07  5:35         ` Jeff Garzik
2004-07-07 18:29           ` jamal
     [not found]             ` <40EDC7A7.8060906@pobox.com>
2004-07-08 23:08               ` jamal
2004-07-21 19:51       ` Andy Fleming
2004-07-21 20:14         ` David Woodhouse
2004-08-02 22:19       ` Andy Fleming
2004-08-02 23:11         ` Jeff Garzik
2004-08-02 23:25           ` Andy Fleming
2004-08-04 23:02             ` Andy Fleming
2004-08-16 16:31               ` Kumar Gala
2004-08-22 21:03               ` Jeff Garzik
2004-07-07  5:27   ` Jeff Garzik
     [not found]     ` <D3458628-D05D-11D8-BA44-000393C30512@freescale.com>
2004-07-08 22:29       ` Jeff Garzik
     [not found]         ` <944A2374-D137-11D8-8835-000393C30512@freescale.com>
2004-07-09  1:32           ` jamal
2004-07-09  1:42             ` jamal
2004-07-26 22:06     ` Andy Fleming
2004-07-26 22:10       ` Jeff Garzik
2004-08-02 13:59         ` Kumar Gala
2004-08-02 14:09           ` Christoph Hellwig
2004-08-02 14:11             ` Kumar Gala
     [not found] ` <2A724364-D53A-11D8-8835-000393C30512@freescale.com>
     [not found]   ` <40F4A6E5.4060000@pobox.com>
2004-07-19 23:29     ` Andy Fleming
2004-07-20  1:13       ` David Woodhouse [this message]
     [not found] <8F52CF1D-C916-11D8-BB6A-000393DBC2E8@freescale.com>
2004-07-05 17:28 ` Jeff Garzik
2004-07-06  2:38   ` jamal
     [not found]   ` <20040708231131.GA20305@infradead.org>
2004-07-08 23:25     ` Jeff Garzik
2004-07-08 23:35       ` Christoph Hellwig

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=1090286009.4149.12.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=AFLEMING@motorola.com \
    --cc=afleming@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=hadi@cyberus.ca \
    --cc=jgarzik@pobox.com \
    --cc=kumar.gala@motorola.com \
    --cc=netdev@oss.sgi.com \
    --cc=rmk@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).