From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-dev@ozlabs.org
Subject: New version of the device tree aware EMAC driver
Date: Wed, 16 May 2007 13:26:30 +1000 [thread overview]
Message-ID: <20070516032630.GC19127@localhost.localdomain> (raw)
I've made a few more tiny tweaks to BenH's rewritten device-tree based
4xx EMAC driver. The main change is that it now no longer requires
'device_type', just 'compatible' to be set in the ZMII and MAL device
nodes when probing. This works better with current thinking on
flattened device trees which discourages creating new device_type
values unless there is a clear use for a new device class binding.
The patch can be obtained from:
http://ozlabs.org/~dgibson/home/emac/powerpc-emac-new-20070516.patch
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next reply other threads:[~2007-05-16 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 3:26 David Gibson [this message]
2007-05-16 16:18 ` New version of the device tree aware EMAC driver Valentine Barshak
2007-05-16 17:00 ` Valentine Barshak
2007-05-16 18:03 ` Valentine Barshak
2007-05-21 5:06 ` David Gibson
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=20070516032630.GC19127@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
/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.