On Tue, Apr 28, 2009 at 06:42:43AM +0200, Heiko Schocher wrote: > Scott Wood wrote: > > On Mon, Apr 27, 2009 at 07:38:38AM +0200, Heiko Schocher wrote: > >> 1) add in the soc node an "errata" node and in this "errata" node > >> we can add all CPU specific errata as an example the qe_enet10 > >> errata, which above code covers: > > > > What about errata discovered after the device tree is deployed? > > Didn;t know that there are such errata. Ok, this is a problem.
Bugs can be discovered at any point in time. > > The presence of the erratum itself is indicated by the presence of the > > buggy device, possibly in conjunction with SVR if the device tree is not > > specific enough. > > Ah, Ok, that was just an idea ... so, where and how to solve the qe_enet10 > errata without using get_immrbase() Get the register block address from the par_io node. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
