On Mon, Nov 15, 2010 at 04:27:06PM -0800, H. Peter Anvin wrote:
> On 11/13/2010 10:22 PM, Grant Likely wrote:
> >
> > 'char' is completely bogus in this context. Either void or struct
> > boot_param_header would be more accurate and useful. I believe you
> > can do:
> >
> > extern void __dt
On 11/13/2010 10:22 PM, Grant Likely wrote:
>
> 'char' is completely bogus in this context. Either void or struct
> boot_param_header would be more accurate and useful. I believe you
> can do:
>
> extern void __dtb_start;
> extern_void __dtb_end;
>
> And then reference the addresse
On Sat, Nov 13, 2010 at 11:26 PM, Stephen Neuendorffer
wrote:
>
>
>> > + initial_boot_params = blob;
>
>> Blech! I really need to get Stephen (cc'd) to respin his "of/fdt: Add
>> unflatten_partial_device_tree" patch that decouples the flattree
>> functions from initial_boot_para
> > + initial_boot_params = blob;
> Blech! I really need to get Stephen (cc'd) to respin his "of/fdt: Add
> unflatten_partial_device_tree" patch that decouples the flattree
> functions from initial_boot_params. Having to do it this way is just
> plain ugly.
> Stephen: nudge,
On Thu, Nov 11, 2010 at 04:03:50PM -0800, dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> Add support for specifying a "compatible" string from the kernel
> command line and functions for the platform to find the compatible
> blob present in the kernel image if any.
>
> Signed-off-by:
From: Dirk Brandewie
Add support for specifying a "compatible" string from the kernel
command line and functions for the platform to find the compatible
blob present in the kernel image if any.
Signed-off-by: Dirk Brandewie
---
drivers/of/fdt.c | 52
