On Mon, 03 Dec 2018 12:57:28 PST (-0800), atish.pa...@wdc.com wrote:
From: Palmer Dabbelt
Someone must have read the device tree specification incorrectly,
because we were putting timebase-frequency in the wrong place. This
corrects the issue, moving it from
/ {
cpus {
On Mon, 03 Dec 2018 12:57:28 PST (-0800), atish.pa...@wdc.com wrote:
From: Palmer Dabbelt
Someone must have read the device tree specification incorrectly,
because we were putting timebase-frequency in the wrong place. This
corrects the issue, moving it from
/ {
cpus {
From: Palmer Dabbelt
Someone must have read the device tree specification incorrectly,
because we were putting timebase-frequency in the wrong place. This
corrects the issue, moving it from
/ {
cpus {
timebase-frequency = X;
}
}
to
/ {
cpus {
From: Palmer Dabbelt
Someone must have read the device tree specification incorrectly,
because we were putting timebase-frequency in the wrong place. This
corrects the issue, moving it from
/ {
cpus {
timebase-frequency = X;
}
}
to
/ {
cpus {
4 matches
Mail list logo
