All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: ralf@linux-mips.org
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: MIPS - 64bit woes
Date: Wed, 09 Nov 2005 00:51:06 -0800	[thread overview]
Message-ID: <4371B87A.9040101@jg555.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0511071143210.28165@blysk.ds.pg.gda.pl>

Here is what I did to track down the errors.

I created a diff between the last working kernel 2.6.12 and the current 
kernel. Started with cpu-probe.c, that to me seemed the logical choice.

After patching the rest of files needed to support the patch in 
cpu-probe.c, I was finally able to produce a kernel under 2.6.12 with 
the same problem.

The files that I ported from 2.6.14 to 2.6.12 are the following
cpu-probe.c
cpu.h
mipsregs.h
cache.c
cpu-features.h

Here is a link to the patches I used http://ftp.jg555.com/errors

Looking at mipsregs.h, something doesn't look right for a 64 bit system. 
But I'm not the expert.

Here are my findings, I hope someone out there has an idea.

-- 
----
Jim Gifford
maillist@jg555.com

  parent reply	other threads:[~2005-11-09  8:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 18:56 MIPS - 64bit woes Jim Gifford
2005-11-05 23:19 ` Kumba
2005-11-07 22:22   ` Jim Gifford
2005-11-08  1:41     ` Stuart Anderson
2005-11-07 11:46 ` Maciej W. Rozycki
2005-11-08  0:51   ` Kumba
2005-11-09  8:51   ` Jim Gifford [this message]
2005-11-09 13:36     ` Kumba
2005-11-09 17:22       ` Jim Gifford
2005-11-15 15:17         ` Jim Gifford
2005-11-17 22:57           ` Jim Gifford
2005-11-18  1:21             ` Jim Gifford
2005-11-18 17:17               ` Ralf Baechle
2005-11-18 17:24                 ` Jim Gifford
2005-11-18 17:29                   ` Ralf Baechle
2005-11-19 17:36                     ` mips iomap.c (Was: Re: MIPS - 64bit woes) Atsushi Nemoto

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=4371B87A.9040101@jg555.com \
    --to=maillist@jg555.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 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.