* Benoit Cousson b-cous...@ti.com [110901 19:52]:
In order to avoid conflict with the new board-omap3-dt.c file,
remove the .dt_compat entry from the beagle regular board
file.
Any DT work for OMAP3 will have to be done on the generic DT
board file to avoid breaking the legacy board support
On 9/2/2011 10:12 AM, Tony Lindgren wrote:
* Benoit Coussonb-cous...@ti.com [110901 19:52]:
In order to avoid conflict with the new board-omap3-dt.c file,
remove the .dt_compat entry from the beagle regular board
file.
Any DT work for OMAP3 will have to be done on the generic DT
board file to
* Cousson, Benoit b-cous...@ti.com [110902 11:26]:
On 9/2/2011 10:12 AM, Tony Lindgren wrote:
* Benoit Coussonb-cous...@ti.com [110901 19:52]:
In order to avoid conflict with the new board-omap3-dt.c file,
remove the .dt_compat entry from the beagle regular board
file.
Any DT work for
On 9/2/2011 12:48 PM, Tony Lindgren wrote:
* Cousson, Benoitb-cous...@ti.com [110902 11:26]:
On 9/2/2011 10:12 AM, Tony Lindgren wrote:
* Benoit Coussonb-cous...@ti.com [110901 19:52]:
In order to avoid conflict with the new board-omap3-dt.c file,
remove the .dt_compat entry from the
* Cousson, Benoit b-cous...@ti.com [110902 15:02]:
On 9/2/2011 12:48 PM, Tony Lindgren wrote:
I'm not sure it is that simple. We have 20+ OMAP3+ boards supported
so far. Dropping pdata when a driver is adapted means that all these
boards should be properly adapted to DT and tested...
In order to avoid conflict with the new board-omap3-dt.c file,
remove the .dt_compat entry from the beagle regular board
file.
Any DT work for OMAP3 will have to be done on the generic DT
board file to avoid breaking the legacy board support until
DT migration is done.
Based on orginal patch
