[fedora-arm] Using device trees (dtb files) on trimslice

Peter Robinson pbrobinson at gmail.com
Tue Feb 21 00:04:32 UTC 2012


Hi Will,

On Mon, Feb 20, 2012 at 9:31 PM, William Cohen <wcohen at redhat.com> wrote:
> Has any luck in using the device trees (dtb files) on arm machines?  Things do not seem to be working with the tegra-trimslice.dtb and CONFIG_ARM_APPENDED_DTB=y for me.
>
> I have been looking at Red hat Bug 741325 (ARM fc14 kernels does not provide hardware perf counter support). I suspect the reason that performance monitoring hardware is not working on my trimslice because it isn't using a device tree.  The performance monitoring hardware is never getting registered (https://bugzilla.redhat.com/show_bug.cgi?id=741325#c18). I have made a tegra-trimslice.dtb, appended it to the vmlinuz file (suppose to work kernel built with CONFIG_ARM_APPENDED_DTB=y in the config file), done a mkimage on the resulting concatenated file. and attempted to boot the machine. However, it seem to hang right after "Staring kernel ..." message.
>

A couple of points. Firstly all configurable HW bits and features
should be configurable in our kernels without device tree, it's just
not a dynamic config that we could use on any device. That said I was
looking at the kernels over the weekend to get the 3.3 bits compiling
on all our current various kernel configs and discovered the
"CONFIG_HIGH_RES_TIMERS=y" option was configured on some of our ARM
kernels but not others inc tegra. I think that might be the general
config option we need to fix our kernels for the support. The tegra
kernels compiles with that option, I'm in the process of getting the
rest cleaned up to get a new build but you might like to try that
option in the interim to see if that helps.

Peter


More information about the arm mailing list