From: Ralf Baechle <ralf@linux-mips.org>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mips64/setup.c
Date: Thu, 31 Jul 2003 22:17:13 +0200 [thread overview]
Message-ID: <20030731201713.GA13263@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0307311421110.6891-100000@ares.mmc.atmel.com>
On Thu, Jul 31, 2003 at 02:22:45PM -0400, David Kesselring wrote:
> > On Thu, Jul 31, 2003 at 11:54:15AM -0400, David Kesselring wrote:
> >
> > > Is the file mips64/setup.c used? I believe that I see two problems in it;
> > > 1) The Ocelot options in setup_arch have case statements without a switch.
> >
> > Ocelot 64-bit kernel is currently work in progress. A first cut of
> > the patch was posted to this mailing list a few days ago.
> >
> > > 2) There is no option for Sead but the mips64 build for sead compiles
> > > fine.
> >
> > The fun of when two almost identical files go out of sync.
> Then do you know what is happening when 64bit sead is configured? Why
> doesn't the compile fail?
This is easy, there is a function call missing which won't cause an
error message unlike a missing function. Don't ask me why - it just seems
the 64-bit SEAD port was never completly sent to me or so. Anyway, I
just fixed this in the linux_2_4 CVS branch; as the result of merging
mips with mips64 this bug was magically dealt with in 2.6.
Ralf
prev parent reply other threads:[~2003-07-31 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 15:54 mips64/setup.c David Kesselring
2003-07-31 16:52 ` mips64/setup.c Ralf Baechle
2003-07-31 18:22 ` mips64/setup.c David Kesselring
2003-07-31 20:17 ` 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=20030731201713.GA13263@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