Hello,

The attached (a patch against my sysregs branch) based mostly by code 
previously written by Fernando Nasser, adds MSR and system register 
support for an i386 RedBoot target.  They each get their own group. 
That way:
	info registers msr
and 
info registers system
works (but MSR and SYSTEM registers are not displayed by ``info 
registers''.).

The patch (apart from demonstrating that reggroups really do work :-) 
identifies a number of issues:

- The patch makes RedBoot the default i386 abi -- if nothing else hits, 
this gets to be it.  Its done by brute force.  This goes back to the 
default discussed earlier for the ``set osabi'' command.  Better re-read 
the thread ...

- The patch makes use of Fernando's `p' packet (proposed long ago) for 
fetching registers beyond the end of the G packet.  To get the code to 
work (since remote.c still can't describe G packets) it contains a, er, 
small ``small tweak''.

- Because the MSR register space contains 4g of regististers) Fernando 
used ``target_query()'' and a RedBoot specific packet to funnel commands 
down to the the target that tell the target which MSR to read.  Remote.c 
should be able to handle sparse register spaces.

- Given that there are ~130 registers here (check ``maint print 
registers'') GUI's such as insight and MI are going to want an interface 
to reggroups pretty quick.

I'll park this in my sysregs branch.  RedBoot is available at 
http://sources.redhat.com/redboot/

comments?
Andrew