All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Building For 486
Date: Thu, 03 Jan 2013 14:11:18 -0300	[thread overview]
Message-ID: <50E5BBB6.5020708@zacarias.com.ar> (raw)
In-Reply-To: <AC90E66A6CD74D73BE3BEFF9E6A04249@beraninstruments.com.local>

On 01/03/2013 01:59 PM, Will Moore wrote:
> You need to ensure you use "an appropriate" kernel configuration for the
> vortex86dx and correctly configure buildroot to build the kernel with it, let me
> know if this makes no sense and you need more details...
> 
> IMHO a good starting place is the 2.6.29.6 kernel config provided by DM&P in
> their X-Linux distribution.  I say a good starting place as I have had no end of
> problems moving to more recent kernels.  (OT: I have had no end of problems with
> this CPU full-stop, I have a deep seated suspicion that the FPU is "broken" or
> at least both Linux and QNX kernels don't like it much, I run with it turned off
> and use the Linux FPE. YMMV).

I've got one of those "nice" ebox2300 boxes that use the original
Vortex86 (AKA SiS 550).
They're something like a 486-586 depending on how you look at it.
I don't know how much they carried over to the newer SX/DX/MX variants
but i vividly remember that the linux kernel configuration must be
almost perfect to boot on these.
I also recall that some kernel versions flat out don't like them, so
trying is the best option until you find a suitable one.
If you're interested i might be able to dig a kernel .config, but
remember it's a different beast from the newer variants and it might not
help at all.
Regards.

      reply	other threads:[~2013-01-03 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 16:14 [Buildroot] Building For 486 Ted Wood
2013-01-03 16:23 ` Richard Braun
2013-01-03 16:28   ` Ted Wood
2013-01-03 16:59 ` Will Moore
2013-01-03 17:11   ` Gustavo Zacarias [this message]

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=50E5BBB6.5020708@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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.