From: Ralf Baechle <ralf@linux-mips.org>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 64bit Sead build
Date: Tue, 22 Jul 2003 14:52:47 +0200 [thread overview]
Message-ID: <20030722125247.GC12449@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0307220836390.16466-100000@ares.mmc.atmel.com>
On Tue, Jul 22, 2003 at 08:40:30AM -0400, David Kesselring wrote:
> Thanks for the info. I'm trying to build 64bit sead so that it can be a
> basis for a port to our own chip with a MIPS 5kf core. Is one of the other
> supported boards more generic (and thus a better start) than Sead?
Btw, forgot to mention I put a fix for the problem you reported into
CVS yesterday so building works. I don't have a SEAD so I wasn't
able to test.
Ralf
prev parent reply other threads:[~2003-07-22 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 14:32 64bit Sead build David Kesselring
2003-07-21 23:36 ` Ralf Baechle
2003-07-22 12:40 ` David Kesselring
2003-07-22 12:48 ` Ralf Baechle
2003-07-22 12:49 ` Dominic Sweetman
2003-07-22 13:04 ` Ralf Baechle
2003-07-22 12:52 ` 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=20030722125247.GC12449@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dkesselr@mmc.atmel.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