Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jes Sorensen <jes@wildopensource.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Manish Lachwani <mlachwani@mvista.com>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH]PCI on SWARM
Date: Mon, 18 Oct 2004 21:15:07 +0200	[thread overview]
Message-ID: <20041018191507.GA14440@linux-mips.org> (raw)
In-Reply-To: <yq0zn2ks9em.fsf@jaguar.mkp.net>

On Mon, Oct 18, 2004 at 04:44:17AM -0400, Jes Sorensen wrote:

> Dual address cycles, ie. 64 bit addressing is fscked on the 1250 from
> what I remember. Correct way to work around this is to stick all
> physical memory outside the 32 bit space into ZONE_HIGHMEM - had a patch
> for 2.4, but I lost it ages ago ;-(

The Momentum Jaguar suffers from similar problems, so I've implemented
that for Linux 2.6 as CONFIG_LIMITED_DMA.

> One can just hope Broadcom will learn how to make chips some day ;-(

Well, they've just done their homework, also known as the 1450.  Pick
your red pen and give grades ;-)

  Ralf

  reply	other threads:[~2004-10-18 19:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14  2:23 [PATCH]PCI on SWARM Manish Lachwani
2004-10-14 19:17 ` Ralf Baechle
2004-10-14 22:14   ` Maciej W. Rozycki
2004-10-14 22:20     ` Manish Lachwani
2004-10-14 22:32       ` Maciej W. Rozycki
2004-10-14 22:55         ` Ralf Baechle
2004-10-15  2:19           ` Maciej W. Rozycki
2004-10-18  8:44             ` Jes Sorensen
2004-10-18 19:15               ` Ralf Baechle [this message]
2004-10-20  5:56                 ` Jes Sorensen
2004-10-20 11:34                   ` Ralf Baechle
2004-10-18 20:17               ` Maciej W. Rozycki
2004-10-20  5:57                 ` Jes Sorensen
2004-10-20 11:17                   ` Ralf Baechle
2004-10-15  1:14         ` Manish Lachwani

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=20041018191507.GA14440@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jes@wildopensource.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=mlachwani@mvista.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