| Age | Commit message (Collapse) | Author |
|---|
|
It is more safe to use clear instead of msrset.
We save some instructions too.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
It was necessary to use fourth parameter(r8) in early_printk
to show messages on console.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
It is necessary to zeroed r7 when r7 points to bad
dtb - this caused that we have correct messages
about compiled-in dtb or passing via r7
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
I can't clear r7 because if I do it I lose information
where DTB come from.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
If r7 is zero at kernel boot, or does not point to a valid DTB, then
we fall back to a DTB (assumed to be) linked statically in the kernel, instead
of blindly copying bogus cruft into the kernel DTB memory region
Signed-off-by: John Williams <john.williams@petalogix.com>
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
|
Reviewed-by: Ingo Molnar <mingo@elte.hu>
Acked-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Acked-by: John Linn <john.linn@xilinx.com>
Acked-by: John Williams <john.williams@petalogix.com>
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
