public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: r030t1@gmail.com
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>,
	Gentoo x86 AT <x86@gentoo.org>,
	release@gentoo.org
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Wed, 22 Aug 2018 16:39:16 -0400	[thread overview]
Message-ID: <CAGfcS_nM0zspLFb_-zvckKK5offGy5jAP8YYhB-88dgA9prjBA@mail.gmail.com> (raw)
In-Reply-To: <CAAD4mYgqnTsYkGoh+0oPyfJNndeSZ9PYA_iu-B3dnw9GgHq3vA@mail.gmail.com>

On Wed, Aug 22, 2018 at 4:27 PM R0b0t1 <r030t1@gmail.com> wrote:
>
> Even newer embedded i586 and i686 hardware isn't cost effective
> considering power consumption. When considering power it often does
> not even make sense to run donated hardware ~5 years old.
>

I was referring to running the x86 arch on hardware that is
otherwise-capable of running the amd64 arch.  I'm not really sure how
important that would be, but I wanted to at least consider the
possibility.

In any case, this is becoming moot it seems.

-- 
Rich


  reply	other threads:[~2018-08-22 20:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 12:26 [gentoo-dev] Gentoo i486 support Ben Kohler
2018-08-22 13:08 ` Rich Freeman
2018-08-22 13:23   ` Mart Raudsepp
2018-08-22 14:22   ` Peter Stuge
2018-08-22 20:27   ` R0b0t1
2018-08-22 20:39     ` Rich Freeman [this message]
2018-08-25 11:07   ` Andrew Savchenko
2018-08-22 13:21 ` James Le Cuirot
2018-08-22 14:30 ` Mike Gilbert
2018-08-22 15:27   ` Thomas Deutschmann
2018-08-22 19:20 ` Matt Turner
2018-08-22 19:27   ` M. J. Everitt
2018-08-22 20:19 ` Richard Yao
2018-08-24 13:19 ` Kent Fredric
2018-08-24 13:57   ` Mike Gilbert
2018-08-24 14:13     ` Rich Freeman
2018-08-24 14:40       ` Kent Fredric

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=CAGfcS_nM0zspLFb_-zvckKK5offGy5jAP8YYhB-88dgA9prjBA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=r030t1@gmail.com \
    --cc=release@gentoo.org \
    --cc=x86@gentoo.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