RFC: replace device_type with new "class" property?
stuart.yoder at freescale.com
Thu Nov 1 05:05:45 EST 2007
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Wednesday, October 31, 2007 12:06 PM
> To: Yoder Stuart-B08248
> Cc: David Gibson; Olof Johansson; linuxppc-dev at ozlabs.org
> Subject: Re: RFC: replace device_type with new "class" property?
> 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.
Fine, I picked a bad example. My point was that if a
property was _required_ that it should have a class id
of some sort that ties it back to the standard that
More information about the Linuxppc-dev