Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Here is my first attempt at a new approach, using the new upstream clock
drivers, and
daniel wrote:
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Here is my first attempt at a new approach, using the new
On Thu, Jun 13, 2013 at 11:56 AM, Paul Fox p...@laptop.org wrote:
does this imply a future flag day, at which time new firmware will be
incompatible with old kernels, and vice-versa?
Unfortunately even without the DT changes described here, old firmware
versions already will not be able to boot
It seems okay to me on first reading.
On 6/13/2013 7:53 AM, Daniel Drake wrote:
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
