From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: kettenis@chello.nl
Cc: ac131313@ges.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Query Red Boot's i386 CPU id
Date: Fri, 30 Aug 2002 12:10:00 -0000 [thread overview]
Message-ID: <2593-Fri30Aug2002220752+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <86bs7lp92j.fsf@elgar.kettenis.dyndns.org> (message from Mark Kettenis on 30 Aug 2002 00:57:24 +0200)
> From: Mark Kettenis <kettenis@chello.nl>
> Date: 30 Aug 2002 00:57:24 +0200
>
> > (1) Why is this feature implemented for remote targets only? Why is
> > the database of CPU ids installed only for embedded builds?
>
> Seconded. I'm getting wild ideas of downloading the cpuid code to the
> target, executing it there, and fetching the return value, and use
> that to e.g. select whether it makes sense to do MMX or SSE :-).
See go32-nat.c which already does something similar ;-).
next prev parent reply other threads:[~2002-08-30 19:06 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 [this message]
2002-08-30 6:52 ` Michal Ludvig
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=2593-Fri30Aug2002220752+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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