[lkml]   [2010]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] ARM: allow, but warn, when issuing ioremap() on RAM
    On Mon, Oct 11, 2010 at 10:02:12AM +0100, Russell King - ARM Linux wrote:
    > On Mon, Oct 11, 2010 at 10:35:08AM +0200, Uwe Kleine-König wrote:
    > > Alternatively when calling fixup only after parse_tags in setup_arch()
    > > it worked. But I guess this change is not for discussion.
    > > OTOH I wonder why fixup gets passed meminfo. It's not very useful if
    > > it's not yet filled.
    > Because, rather than pass in ATAGs or set the memory on the command line,
    > they instead wanted to hard-code it in C - something which still happens
    > today:
    > arch/arm/mach-msm/board-halibut.c
    > arch/arm/mach-msm/board-mahimahi.c
    > arch/arm/mach-msm/board-sapphire.c
    > arch/arm/mach-msm/board-trout.c
    > arch/arm/mach-pxa/eseries.c
    > arch/arm/mach-pxa/spitz.c
    > arch/arm/mach-s3c2412/mach-smdk2413.c
    > arch/arm/mach-s3c2412/mach-vstms.c
    > arch/arm/mach-tegra/board-harmony.c
    > This is part of the on-going pain of poor quality boot loaders.
    Yep, so (at least regarding the memory layout) the name "fixup" is
    wrong, it's more "initializ"ish.

    So what now? Do the memory reservation in mdesc->reserve as Felipe

    Best regards

    Pengutronix e.K. | Uwe Kleine-König |
    Industrial Linux Solutions | |
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2010-10-11 11:27    [W:0.022 / U:1.400 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site