Jimi Xenidis wrote:
> Sorry for the pause, lots of other things getting done... questions below.
>
> On Nov 9, 2012, at 10:33 PM, Michael Neuling wrote:
>
> > Benjamin Herrenschmidt wrote:
> >
> >> On Fri, 2012-11-09 at 11:43 -0600, Jimi Xenidis wrote:
> >>> The CPU_FTR_* values are pretty t
Sorry for the pause, lots of other things getting done... questions below.
On Nov 9, 2012, at 10:33 PM, Michael Neuling wrote:
> Benjamin Herrenschmidt wrote:
>
>> On Fri, 2012-11-09 at 11:43 -0600, Jimi Xenidis wrote:
>>> The CPU_FTR_* values are pretty tight (a few bits left) yes I need to s
Benjamin Herrenschmidt wrote:
> On Fri, 2012-11-09 at 11:43 -0600, Jimi Xenidis wrote:
> > The CPU_FTR_* values are pretty tight (a few bits left) yes I need to save
> > and restore the QPX registers.
> > There are 32 QPX registers, each 32 bytes in size, it is otherwise managed
> > by the FPSC
On Fri, 2012-11-09 at 11:43 -0600, Jimi Xenidis wrote:
> The CPU_FTR_* values are pretty tight (a few bits left) yes I need to save
> and restore the QPX registers.
> There are 32 QPX registers, each 32 bytes in size, it is otherwise managed by
> the FPSCR and MSR[FP]
>
> I was thinking that I c
