From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Lowe <nick.lowe@gmail.com>
Cc: Hans-Peter Jansen <hpj@urpla.net>, linux-kernel@vger.kernel.org
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2
Date: Wed, 8 Sep 2010 22:11:44 +0100 [thread overview]
Message-ID: <20100908221144.73066e2d@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTi=FNFKmBgobH4q-GHguHM-0UOCQpa7JhPhyZZHG@mail.gmail.com>
> 1) Those enterprise long term distributions aren't going to be
> targeting the Crusoe or Geode. It's not their market. Would they even
See this is the problem. You've forgotten *users*. It's easy to roll a
special kernel, its hell on earth
> back port, therefore, if it was an issue?
> (This hypothetical anyway as it assuming they have an i686 targeted
> build already. Who does? Centos, RHEL and SUSE Enterprise are all i386
> targeted at the moment for x86.)
Wrong for some packages - and enough to break things. Bits like glibc for
example and chunks of X and proprietary apps.
>. (Again, hypothetical, as they're not targeted at i686!)
See above
> 4) As for proprietary apps, again, is it likely that they're targeting
> i686 already? Or is it far more likely they're compiled for i386 et.
> al.
Lots used -i686 because the compiler people said its faster and it works
on all 686 platforms. Neither of which it turns out is exactly true in
many cases.
> 6) What we are talking about is future distributions, whatever they
> are, that are now or are changing to target i686 which end users will
> ultimately want to migrate to and run.
s/we/you
Getting the stuff right in the current kernel makes it easier to backport
and fix and do tidily. It's not as if NOPL is complicated to emulate.
next prev parent reply other threads:[~2010-09-08 20:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fmbxh-5N8-41@gated-at.bofh.it>
2010-09-07 15:57 ` Nick Lowe
2010-09-08 9:15 ` Hans-Peter Jansen
2010-09-08 11:34 ` Nick Lowe
2010-09-08 11:55 ` Nick Lowe
2010-09-08 17:56 ` Alan Cox
2010-09-08 17:51 ` Nick Lowe
2010-09-08 19:07 ` Alan Cox
2010-09-08 19:44 ` Nick Lowe
2010-09-08 21:11 ` Alan Cox [this message]
2010-09-08 21:05 ` H. Peter Anvin
2010-09-08 21:07 ` Nick Lowe
2010-08-27 18:07 Matteo Croce
2010-08-27 18:48 ` H. Peter Anvin
2010-08-27 20:15 ` Matteo Croce
2010-08-27 20:49 ` Thomas Backlund
2010-08-27 21:32 ` Matteo Croce
2010-08-27 22:16 ` Matteo Croce
2010-08-27 22:19 ` Matteo Croce
2010-08-27 23:07 ` H. Peter Anvin
2010-08-29 12:52 ` Avi Kivity
2010-08-29 13:39 ` Matteo Croce
2010-09-08 20:59 ` H. Peter Anvin
2010-08-27 20:54 ` H. Peter Anvin
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=20100908221144.73066e2d@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.lowe@gmail.com \
/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®