All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: baitisj@evolution.com
Cc: ppopov@mvista.com, linux-mips@linux-mips.org
Subject: Re: fixup_bigphys_addr and DBAu1500 dev board
Date: Fri, 21 Feb 2003 15:40:44 -0500	[thread overview]
Message-ID: <3E568ECC.2090601@embeddededge.com> (raw)
In-Reply-To: 20030221122515.E20129@luca.pas.lab

Jeff Baitis wrote:

> I'd love to know where this mystery fixup_bigphys_addr comes from!?

You need the 36-bit patch from Pete that is not yet part of the
linux-mips tree.

You can find it on linux-mips.org in /pub/linux/mips/people/ppopov.

Have fun!


	-- Dan

  reply	other threads:[~2003-02-21 20:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20  6:05 Ramdisk image on flash Krishnakumar. R
2003-02-20 18:27 ` Pete Popov
2003-02-20 19:30   ` Tibor Polgar
2003-02-20 19:41     ` Mark Salter
2003-02-20 20:01       ` Tibor Polgar
2003-02-20 20:16         ` Mark Salter
2003-02-20 20:35         ` Dan Malek
2003-02-20 20:44           ` Jun Sun
2003-02-20 20:57             ` Pete Popov
2003-02-20 21:24               ` Dan Malek
2003-02-20 20:37         ` Jun Sun
2003-02-20 21:08           ` Guido Guenther
2003-02-20 21:12         ` Alan Cox
2003-02-20 19:41     ` Pete Popov
2003-02-20 19:42     ` Brian Murphy
2003-02-20 20:59   ` Guido Guenther
2003-02-20 21:27     ` Dan Malek
2003-02-21  2:24 ` Atsushi Nemoto
2003-02-21 20:25   ` fixup_bigphys_addr and DBAu1500 dev board Jeff Baitis
2003-02-21 20:40     ` Dan Malek [this message]
2003-02-21 22:10       ` Pete Popov
2003-02-22  3:50       ` Jeff Baitis
2003-02-23  9:19         ` Geert Uytterhoeven
2003-02-24 17:46         ` Pete Popov
2003-02-25 21:54           ` Jeff Baitis
2003-02-25 22:05             ` Pete Popov

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=3E568ECC.2090601@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=baitisj@evolution.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.