On Wed, Mar 27, 2013 at 5:02 AM, Dirk Behme <dirk.be...@de.bosch.com> wrote:
> I'll check this. > > Rethinking about the issue here, my recent understanding is: > > a) We have a VPU library which only understands 0x63 (Quad) and 0x61 > (DualLite/Solo) Correct. > b) We have Troy's existing get_cpu_rev() [1] which seems to correctly decode > the CPU revision (at least this is my impression from testing ;) ). But > reports 0x62 for the Solo which then isn't understood by the VPU library (to > be checked). Correct. > I wonder if we could find a way to combine both parts without breaking the > other? I.e. using Troy's get_cpu_rev() to correctly report the CPU revision > (in U-Boot), but let the VPU library get the revision it understands? Yes, this could be possible. The original patch in this thread fixes the returned value by get_cpu_rev(), so that we can have mainline U-boot to boot a system that can use VPU on a mx6solo. It is still possible to report the CPU revisions (Quad/Dual-lite/Solo/Solo-lite) strings in boot time. We would need to add a custom mx6 code for printing the strings. Regards, Fabio Estevam _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot