Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Louis Hamilton <hamilton@redhat.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] Mips64 Ocelot-C and Jaguar ATX platform support
Date: Wed, 30 Jul 2003 03:30:20 +0200	[thread overview]
Message-ID: <20030730013019.GA7366@linux-mips.org> (raw)
In-Reply-To: <3F1F0BDC.8040609@redhat.com>

On Wed, Jul 23, 2003 at 05:27:40PM -0500, Louis Hamilton wrote:

> Notes the board support lives under arch/mips/momentum.
> Also, CONFIG_BOARD_SCACHE and CONFIG_RM7000_CPU_SCACHE are utilized and
> integrated into each platform's default configuration files.
> As in the first patch, drivers/net/mv64340_eth.{c,h} is added to provide 
> ethernet support.
> 
> If it looks ok, please check changes into the tree.

Ehhh, sorry.  This CONFIG_JAGUAR_DMALOW thing just isn't the way to go.
I know the Jaguar's DMA architecture is unpleassant to say the least but
still, cluttering generic code with ifdefs isn't the way to go.  Declare
all memory above the DMA limit high-memory and put the rest into ZONE_DMA
rsp. ZONE_NORMAL, as appropriate for the Jaguar.  Then provide a dummy
implementation of kmap, kunmap etc. (unless you have "real" highmem of
course) that does the same thing as if highmem was disabled, see
<linux/highmem.h>.

  Ralf

      parent reply	other threads:[~2003-07-30  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 22:27 [patch] Mips64 Ocelot-C and Jaguar ATX platform support Louis Hamilton
2003-07-28 19:05 ` William Jhun
2003-07-28 19:05   ` William Jhun
2003-07-28 20:20   ` Louis Hamilton
2003-07-30  1:30 ` Ralf Baechle [this message]

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=20030730013019.GA7366@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=hamilton@redhat.com \
    --cc=linux-mips@linux-mips.org \
    /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