[lkml]   [2010]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH] ARM: allow, but warn, when issuing ioremap() on RAM
    Many drivers are broken, and there's no alternative in sight. Such a big
    change should stay as a warning for now, and only later should it
    actually fail.

    The drivers are not doing something correct, we get it, but for now it's
    better to allow them to work (they do 99% of the time anyway) rather
    than to force everyone to revert this patch in their internal trees
    until there's a solution. A slightly broken functionality is better than
    no functionality at all.

    A warning lets people know that what they are doing is not right, and
    they should fix it.

    Cc: Han Jonghun <>
    Cc: Hemant Pedanekar <>
    Cc: Arnd Hannemann <>
    Cc: Uwe Kleine-König <>
    Signed-off-by: Felipe Contreras <>
    arch/arm/mm/ioremap.c | 3 +--
    1 files changed, 1 insertions(+), 2 deletions(-)

    For issues related to this:

    diff --git a/arch/arm/mm/ioremap.c b/arch/arm/mm/ioremap.c
    index ab50627..ccff7da 100644
    --- a/arch/arm/mm/ioremap.c
    +++ b/arch/arm/mm/ioremap.c
    @@ -204,8 +204,7 @@ void __iomem * __arm_ioremap_pfn_caller(unsigned long pfn,
    * Don't allow RAM to be mapped - this causes problems with ARMv6+
    - if (WARN_ON(pfn_valid(pfn)))
    - return NULL;
    + WARN_ON(pfn_valid(pfn));

    type = get_mem_type(mtype);
    if (!type)
    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-07 11:47    [W:0.024 / U:42.604 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site