From: Michal Ludvig <mludvig@suse.cz>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Query Red Boot's i386 CPU id
Date: Fri, 30 Aug 2002 06:52:00 -0000 [thread overview]
Message-ID: <3D6F37B9.6000703@suse.cz> (raw)
In-Reply-To: <Pine.SUN.3.91.1020829080855.26003D-100000@is>
Eli Zaretskii wrote:
> (3) We should add code/data for identification of AMD CPUs, I think.
> They also support CPUID.
... including x86-64 CPUs. They support CPUID as well.
I can supply the code/data later, but please count with the fact, that
I'd like to include it to x86-64 port too.
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
next prev parent reply other threads:[~2002-08-30 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 15:20 Andrew Cagney
2002-08-29 0:08 ` Eli Zaretskii
2002-08-29 16:01 ` Mark Kettenis
2002-08-29 16:44 ` Daniel Jacobowitz
2002-08-30 12:10 ` Eli Zaretskii
2002-08-30 6:52 ` Michal Ludvig [this message]
2002-08-29 17:30 ` Daniel Jacobowitz
2002-08-30 13:08 ` Andrew Cagney
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=3D6F37B9.6000703@suse.cz \
--to=mludvig@suse.cz \
--cc=ac131313@ges.redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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