Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Gregor Waltz <gregor.waltz@raritan.com>
To: linux-mips@linux-mips.org
Subject: Toshiba JMR 3927 working setup?
Date: Fri, 04 Jan 2008 11:45:10 -0500	[thread overview]
Message-ID: <477E6296.7090605@raritan.com> (raw)

I have been working on a JMR 3927 based system for a number of years. 
For all of that time, we have been running:
binutils 2.11.90.0.1
gcc 2.95.3
glibc 2.2.1
linux 2.4.12


We want to update to a 2.6 kernel, recent build tools, and saner system 
libraries. Although, it seems that the JMR 3927 is still technically 
supported, I have not found any info on whether anybody is still running 
Linux on it and what combination of software they are using. Any idea?
Is there a combination of software versions that are known to work on 
this hardware?


I have used crosstool 0.43 to build:
binutils 2.15
gcc 3.4.5
glibc 2.3.6

I cannot get these kernels to build:
linux-2.6.13
linux-2.6.15
linux-2.6.16.57
linux-2.6.17.14
linux-2.6.9

My colleague and I have built these:
linux-2.6.21.7
linux-2.6.23.9
linux-2.6.23.12

However, they all yield a TLBL exception similar to the following:

Exception! EPC=80056eb4 CAUSE=30000008(TLBL)
80056eb4 8ce4000c lw      a0,12(a3)                         # 0xc

Each build has different exception values. The values are the same each 
attempt with the same build.

Is this a problem in the kernel code or the build tools?
Any ideas on how to make it run?

Using the recently built tools, I am currently trying to build the 
2.4.12 kernel that is known to work, which is proving difficult. If I 
can get it to build, I am hoping to see whether the tools are able to 
build a functioning kernel.

Thanks

             reply	other threads:[~2008-01-04 16:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 16:45 Gregor Waltz [this message]
2008-01-04 17:21 ` Toshiba JMR 3927 working setup? Thiemo Seufer
2008-01-04 18:40   ` Gregor Waltz
2008-01-04 18:51     ` Florian Lohoff
2008-01-04 19:23       ` Gregor Waltz
2008-01-04 19:23     ` Thiemo Seufer
2008-01-04 22:27       ` Gregor Waltz
2008-01-05 14:42         ` Atsushi Nemoto
2008-01-07 12:21           ` Ralf Baechle
2008-01-07 15:34             ` Atsushi Nemoto
2008-01-05 15:07     ` Atsushi Nemoto
2008-01-11 17:49       ` Gregor Waltz
2008-01-12 12:17         ` Atsushi Nemoto
2008-01-15 15:50           ` Gregor Waltz
2008-01-15 15:50             ` Gregor Waltz
2008-01-15 16:14             ` Thiemo Seufer
2008-01-15 20:05               ` Gregor Waltz
2008-01-15 23:14                 ` Thiemo Seufer
2008-01-16 15:28                   ` Gregor Waltz
2008-01-16 16:04                     ` Atsushi Nemoto
2008-01-17 16:50                       ` Gregor Waltz
2008-01-18  1:05                         ` Atsushi Nemoto
2008-01-05 14:45 ` Ralf Baechle
2008-01-08 23:54   ` Gregor Waltz
2008-01-09  0:17     ` Thiemo Seufer
2008-02-04  1:14     ` M. Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2008-01-25 16:50 Max Okumoto
2008-01-26  5:08 ` Atsushi Nemoto
2008-01-28 16:36   ` Gregor Waltz
2008-01-29 13:50     ` Atsushi Nemoto
2008-03-06 15:49   ` Ralf Baechle

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=477E6296.7090605@raritan.com \
    --to=gregor.waltz@raritan.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