Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: Oddities with CVS Kernels, Memory on Indigo2
Date: Tue, 15 Apr 2003 04:35:23 -0400	[thread overview]
Message-ID: <3E9BC44B.8080708@gentoo.org> (raw)
In-Reply-To: <20030414140717.GA805@simek>


	A question with the CVS Kernel.  Are there any known issues as to the 
specific toolchain used to build it?  Currently I'm using GCC 3.2.2 + 
Glibc 2.3.2 + Binutils 2.13.90.0.16.  I tried a CVS updateshortly after 
testing this kernel, and it still doesn't boot, so either my timing is 
really bad, or I'm using a toolchain with known issues.  I have noticed 
the toolchain does not support -mcpu in .18 of binutils, and I 
originally thought this was only going to be a GCC change in 3.3, but my 
guess if it's the same in .18/.20, and as such I'll need to use the 
instructions posted about a month about to use -mabi/-march?

--Kumba


Ladislav Michl wrote:
> On Sun, Apr 13, 2003 at 01:13:42AM -0400, Kumba wrote:
> 
> I'd say you've tried cvs kernel at the times when support for R4400
> caches was broken. I put kernel I'm currently running at
> http://www.linux-mips.org/~ladis/vmlinux.gz (gunzip it :)), as you can
> see from dmesg at the end of this mail CPU used in your machine is the
> same. If kernel I provided doesn't boot for you I'd like to ask you for
> help with debugging (kernel was build from cvs updated at 8:30 CEST)

  parent reply	other threads:[~2003-04-15  8:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  5:13 Oddities with CVS Kernels, Memory on Indigo2 Kumba
2003-04-14 14:07 ` Ladislav Michl
2003-04-14 15:53   ` Kumba
2003-04-14 16:00     ` Marc Zyngier
2003-04-14 16:16       ` Kumba
2003-04-14 16:27         ` Marc Zyngier
2003-04-14 16:24       ` Kumba
2003-04-14 16:35         ` Ladislav Michl
2003-04-14 16:58           ` Kumba
2003-04-15  8:35   ` Kumba [this message]
2003-04-15  8:50     ` Ladislav Michl
2003-04-15  9:02       ` Kumba

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=3E9BC44B.8080708@gentoo.org \
    --to=kumba@gentoo.org \
    --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