linux-mips
[Top] [All Lists]

Re: [SPAM] linux-2.6.25.4 Porting OOPS

To: "Pelton, Dave" <dpelton@ciena.com>
Subject: Re: [SPAM] linux-2.6.25.4 Porting OOPS
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 13 Jun 2008 14:41:44 +0100
Cc: "J.Ma" <sync.jma@gmail.com>, Markus Gothe <markus.gothe@27m.se>, linux-mips@linux-mips.org
In-reply-to: <A3BA2251DD85404FBBEF7478C29D8742F26EFE@onmxm01.ciena.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <dcf6addc0806082001m19d54184pc8ab42b0875c5238@mail.gmail.com> <20B109E2-594E-4329-95C7-F67E9A7882E2@27m.se> <dcf6addc0806120251t4785dc09tc4a6f0854c5cd425@mail.gmail.com> <A3BA2251DD85404FBBEF7478C29D8742F26EFE@onmxm01.ciena.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.17 (2007-11-01)
On Thu, Jun 12, 2008 at 03:02:31PM -0400, Pelton, Dave wrote:

> --- linux-2.6.25.4-clean/include/asm-mips/fixmap.h      2008-05-15
> 11:00:12.000000000 -0400
> +++ linux-2.6.25.4/include/asm-mips/fixmap.h    2008-06-12
> 13:21:49.042673000 -0400
> @@ -69,6 +69,8 @@ enum fixed_addresses {
>   */
>  #if defined(CONFIG_CPU_TX39XX) || defined(CONFIG_CPU_TX49XX)
>  #define FIXADDR_TOP    ((unsigned long)(long)(int)(0xff000000 -
> 0x20000))
> +#elif defined(CONFIG_CPU_BMIPS3300)
> +#define FIXADDR_TOP    ((unsigned long)(long)(int)0xff200000 - 0x1000)
>  #else
>  #define FIXADDR_TOP    ((unsigned long)(long)(int)0xfffe0000)
>  #endif
> 
> You will need to define CONFIG_CPU_BMIPS3300 in your config file for
> this change to be applied.  I suspect that the same core is present in
> a number of Broadcom SOC designs, so this issue may exist for a number
> of different chips.

There are a few other processors such as some TX4900 family members which
use up some virtual address space without telling telling the OS.  In any
case I consider that a blatant violation fo the architecture and the
kernel should be tought about these special cases.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>