I2C not working upon 2.6.24 to 2.6.28 kernel upgrade

[Mitch Bradley]

>
> Binding on device_type or name is strongly discouraged, so the above
> > snippit isn't a good idea.
>   
>
> Would you please explain why? I just want to weigh the risk of
> changing the DTB vs. the risk of using a device_type binding.
>   


This has been discussed to death, but ...

The proper meaning of "device_type" is to tell Open Firmware that the 
device node contains a specific set of methods that implements a 
specific API that the firmware can for internal purposes like, for 
example, a console.

People have tried to co-opt it for other uses, but doing so just makes 
its meaning ambiguous, thus making it difficult to use for any purpose.

The "compatible" property is specifically intended for driver selection.