public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marian Aldenhövel" <marian.aldenhoevel@mba-software.de>
To: linux-kernel@vger.kernel.org
Cc: Gilles Espinasse <g.esp@free.fr>
Subject: Re: Building a kernel for SiS55-based system. No, wait! It's a  Vortex86SX.
Date: Fri, 11 Jul 2008 17:43:53 +0200	[thread overview]
Message-ID: <48777FB9.8090102@mba-software.de> (raw)
In-Reply-To: <25e301c8df53$6a525780$f9b5a8c0@pii350>

Hi,

>>> Could you try with distrib images to know if it could be related to your
>>> compilation system

Thank you for your advice re network boot and trying stock kernels. I did
set that up and learned a lot.

For one I learned that the CPU I am fighting with is in fact called
Vortex86SX. My first information (see subject) was either wrong or is a
less well-known alias for the same chip. Sorry for that.

Once armed with that information I was able to find more bits and pieces:

   http://www.phys.ethz.ch/~abe/MicroClientJr/

 > "Kompatibel zu 486SX statt Pentium MMX: Kleinerer Befehlssatz, keine FPU,
 > schmälere Bus-Breite. Debian GNU/Linux 4.0 Etch läuft darauf (X.org aus Etch
 > nicht), grml und Ubuntu nicht. Debian GNU/Linux Lenny/Sid Userland läft
 > ebenfalls darauf, aber der 2.6.24er Kernel aus Sid nicht."

"Compatible with 486SX instead of Pentium MMX: Smaller Instruction set, no
FPU, narrower Bus. Debian GNU/Linux 4.0 Etch are running (X.org from Etch
does not), grml and Ubuntu are not. Debian GNU/Linux Lenny/Sid Userland
works but the 2.6.24 Kernel from Sid does not."

The builder of the chip even has detailed information on how to build
Linux 2.6.18 for it:

   ftp://download@ftp.dmp.com.tw/vortex86sx/Vortex86SX_Linux_HowTo.pdf

Patches included:

   http://www.dmp.com.tw/tech/Vortex86SX/patch-2.6.18-DMP.gz

The bottom line is that current kernels don't work, the last one I know that
works is 2.6.18.. That is used in Debian Etch and I was able to confirm
operation by booting that one.

I have since downgraded my build-system to use 2.6.18.3 and that runs
fine on my hardware. So now I can set it all up any way I like directly
from upstream sources. Hooray!

Thank you very much.

Maybe someone smarter than me can figure out what the actual problem is,
when it was introduced since 2.6.18 and then presumeably fix it. Until
then I think I can live OK with the kernel I have now.

Ciao, MM
-- 
Marian Aldenhövel, Rosenhain 23, 53123 Bonn
http://www.marian-aldenhoevel.de
"I ran some quick calculations on it. He's about 80% on the right
  track.  That leaves him only 20% dead when he crashes." Bob C



  reply	other threads:[~2008-07-11 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  6:35 Building a kernel for SiS55-based system Marian Aldenhövel
2008-06-26  9:16 ` Gilles Espinasse
2008-07-06  8:49   ` Marian Aldenhövel
2008-07-06 10:31     ` Gilles Espinasse
2008-07-11 15:43       ` Marian Aldenhövel [this message]
2008-07-11 15:31         ` Building a kernel for SiS55-based system. No, wait! It's a Vortex86SX Alan Cox
2008-07-11 15:35         ` Alan Cox

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=48777FB9.8090102@mba-software.de \
    --to=marian.aldenhoevel@mba-software.de \
    --cc=g.esp@free.fr \
    --cc=linux-kernel@vger.kernel.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