all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Todd Allen <todd@etallen.com>
Cc: 39762@debbugs.gnu.org
Subject: [bug#39762] [PATCH] gnu: cpuid: Update to 20200211.
Date: Mon, 24 Feb 2020 20:14:23 +0100	[thread overview]
Message-ID: <CAEwRq=oJy7g+Bb9W9HvkgCanbxNhBq35rcwBAHVVoagrv3QJoA@mail.gmail.com> (raw)
In-Reply-To: <20200224151248.GA27726@toad>

Hello Todd

thanks to chime in.

On Mon, Feb 24, 2020 at 4:12 PM Todd Allen <todd@etallen.com> wrote:

> Yes, often cpuid changes because of new features in the CPUID instruction, or
> because of new CPUs determinable by the (synth) and (uarch synth) "leaves".
> Sometimes it's because there was a feature I didn't know existed, like 0x2000000
> leaves for Itanium.  The ":" change to "=" in a couple cases was deliberate.  It
> had been inconsistent before.

Thanks also for the details, I was just not expecting that much
changes initially when
doing a refresh only a few weeks after the preceding one. That means you're doig
lots of work, which is great !

And to Tobias, yes, I was erring on the (too much) safe side, not
really being sure
what I'm doing... I'm still fairly new to guix, even if I lurked in
the vicinity for a long
time. Looks like I'm digging a bit deeper this time (bare-metal
install on an old laptop
in addition to the VM I did my previous attempts with...) And while
trying to be useful,
I don't want to disrupt or make others loose time on my early mistakes...

Thanks all for the help, I'll go package something else now...

-- 
Vincent Legoll

      reply	other threads:[~2020-02-24 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 22:54 [bug#39762] [PATCH] gnu: cpuid: Update to 20200211 Vincent Legoll
2020-02-23 23:49 ` bug#39762: " Tobias Geerinckx-Rice via Guix-patches via
2020-02-24 15:12 ` [bug#39762] " Todd Allen
2020-02-24 19:14   ` Vincent Legoll [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='CAEwRq=oJy7g+Bb9W9HvkgCanbxNhBq35rcwBAHVVoagrv3QJoA@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=39762@debbugs.gnu.org \
    --cc=todd@etallen.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.