On Tue, 2010-01-12 at 23:43 -0700, Grant Likely wrote:
> On Tue, Dec 22, 2009 at 6:17 AM, Michael Ellerman
> wrote:
> > On Tue, 2009-12-22 at 18:54 +0800, Jeremy Kerr wrote:
> >> Hi Michael,
> >>
> >> > > void early_init_dt_setup_initrd_arch(unsigned long start,
> >> > >
On Tue, Dec 22, 2009 at 6:17 AM, Michael Ellerman
wrote:
> On Tue, 2009-12-22 at 18:54 +0800, Jeremy Kerr wrote:
>> Hi Michael,
>>
>> > > void early_init_dt_setup_initrd_arch(unsigned long start,
>> > > unsigned long end);
>> >
>> > arch_early_init_dt_setup_initrd(
On Tue, 2009-12-22 at 18:54 +0800, Jeremy Kerr wrote:
> Hi Michael,
>
> > > void early_init_dt_setup_initrd_arch(unsigned long start,
> > > unsigned long end);
> >
> > arch_early_init_dt_setup_initrd() makes more sense to me, but ..
>
> _arch has been the general
Hi Michael,
> > void early_init_dt_setup_initrd_arch(unsigned long start,
> > unsigned long end);
>
> arch_early_init_dt_setup_initrd() makes more sense to me, but ..
_arch has been the general convention for arch-specific hooks in
drivers/of/.
> > +#ifdef CO
On Tue, 2009-12-22 at 17:39 +0800, Jeremy Kerr wrote:
> At present, the fdt code sets the kernel-wide initrd_start and
> initrd_end variables when parsing /chosen. On ARM, we only set these
> once the bootmem has been reserved.
>
> This change adds an arch callback to setup the initrd from the dev
At present, the fdt code sets the kernel-wide initrd_start and
initrd_end variables when parsing /chosen. On ARM, we only set these
once the bootmem has been reserved.
This change adds an arch callback to setup the initrd from the device
tree:
void early_init_dt_setup_initrd_arch(unsigned long s
