mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Marian Aldenhövel" <marian.aldenhoevel@mba-software.de>
Cc: linux-kernel@vger.kernel.org, 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 16:31:03 +0100	[thread overview]
Message-ID: <20080711163103.6c2102a0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <48777FB9.8090102@mba-software.de>

> 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.

So 2.6.18 works and 2.6.19 fails ? What is the failure that is observed.
My first thought would be FPU emulation as nobody uses it any more.

Alan

  reply	other threads:[~2008-07-11 15:48 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       ` Building a kernel for SiS55-based system. No, wait! It's a Vortex86SX Marian Aldenhövel
2008-07-11 15:31         ` Alan Cox [this message]
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=20080711163103.6c2102a0@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=g.esp@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marian.aldenhoevel@mba-software.de \
    /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

all inboxes | Powered by JetHome®