Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Pelton, Dave" <dpelton@ciena.com>
Cc: "J.Ma" <sync.jma@gmail.com>, Markus Gothe <markus.gothe@27m.se>,
	linux-mips@linux-mips.org
Subject: Re: [SPAM] linux-2.6.25.4 Porting OOPS
Date: Fri, 13 Jun 2008 14:41:44 +0100	[thread overview]
Message-ID: <20080613134143.GE703@linux-mips.org> (raw)
In-Reply-To: <A3BA2251DD85404FBBEF7478C29D8742F26EFE@onmxm01.ciena.com>

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

  parent reply	other threads:[~2008-06-13 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09  3:01 linux-2.6.25.4 Porting OOPS J.Ma
2008-06-09  5:53 ` [SPAM] " Markus Gothe
2008-06-12  9:51   ` J.Ma
2008-06-12 19:02     ` Pelton, Dave
2008-06-12 19:02       ` Pelton, Dave
2008-06-13 13:41       ` Ralf Baechle [this message]
2008-06-13 23:33       ` David VomLehn
2008-06-16 15:52         ` Pelton, Dave
2008-06-16 15:52           ` Pelton, Dave
2008-06-16 16:27           ` Kevin D. Kissell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080613134143.GE703@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dpelton@ciena.com \
    --cc=linux-mips@linux-mips.org \
    --cc=markus.gothe@27m.se \
    --cc=sync.jma@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox