From: Scott Wood <scottwood@freescale.com>
To: Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: RFC: replace device_type with new "class" property?
Date: Wed, 31 Oct 2007 12:06:10 -0500 [thread overview]
Message-ID: <20071031170610.GA4444@loki.buserror.net> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA3035F2AC3@az33exm25.fsl.freescale.net>
On Wed, Oct 31, 2007 at 08:31:02AM -0700, Yoder Stuart-B08248 wrote:
> This works...but certainly is weaker with respect to
> standardization. My previous argument had the assumption
> that something like "mac-address" in a network node was
> _required_, and thus needed a class id of some sort to tie
> the standardized node to.
It is certainly not required -- the device could have an eeprom, or it might
not be ethernet at all.
-Scott
next prev parent reply other threads:[~2007-10-31 17:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:37 RFC: replace device_type with new "class" property? Yoder Stuart-B08248
2007-10-29 15:20 ` Matt Sealey
2007-10-29 16:11 ` Scott Wood
2007-10-29 17:27 ` Dale Farnsworth
2007-10-29 19:02 ` Matt Sealey
2007-10-29 19:30 ` Scott Wood
2007-10-29 19:34 ` Yoder Stuart-B08248
2007-10-29 19:44 ` Scott Wood
2007-10-29 20:20 ` Yoder Stuart-B08248
2007-10-29 23:03 ` Dale Farnsworth
2007-10-30 0:29 ` David Gibson
2007-10-30 0:26 ` David Gibson
2007-10-29 18:55 ` Matt Sealey
2007-10-29 19:21 ` Scott Wood
2007-10-30 0:23 ` David Gibson
2007-10-29 21:22 ` Olof Johansson
2007-10-30 0:51 ` David Gibson
2007-10-30 14:56 ` Yoder Stuart-B08248
2007-10-30 23:27 ` David Gibson
2007-10-31 15:25 ` Yoder Stuart-B08248
2007-10-31 15:31 ` Yoder Stuart-B08248
2007-10-31 17:06 ` Scott Wood [this message]
2007-10-31 18:05 ` Yoder Stuart-B08248
2007-10-31 22:55 ` David Gibson
2007-10-30 16:23 ` Yoder Stuart-B08248
2007-10-30 16:33 ` Scott Wood
2007-10-30 19:06 ` Yoder Stuart-B08248
2007-10-30 19:38 ` Grant Likely
2007-10-30 23:02 ` David Gibson
2007-10-30 22:58 ` 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=20071031170610.GA4444@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=stuart.yoder@freescale.com \
/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).