This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [rfc] Query Red Boot's i386 CPU id

From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
To: kettenis at chello dot nl
Cc: ac131313 at ges dot redhat dot com, gdb-patches at sources dot redhat dot com
Date: Fri, 30 Aug 2002 22:07:52 +0300
Subject: Re: [rfc] Query Red Boot's i386 CPU id
References: <Pine.SUN.3.91.1020829080855.26003D-100000@is> <86bs7lp92j.fsf@elgar.kettenis.dyndns.org>
Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>

> 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 ;-).

References:
- Re: [rfc] Query Red Boot's i386 CPU id
  - From: Eli Zaretskii
- Re: [rfc] Query Red Boot's i386 CPU id
  - From: Mark Kettenis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]