Re: [patches] Re: Status of E500 Linux kernel trap handlers?

[Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx>]

Mark,

If you want to get a preview take a look at http://www.bitshrine.org/ 
gpp/ and search for IEEE754

- k

On Jan 11, 2007, at 1:26 AM, Steve Papacharalambous wrote:

> Hi Mark,
>
> They have been completed and are undergoing internal review.  I'll let
> you know when they're available externally,
>
> Best regards,
>
> Steve
>
> On Wed, 2007-01-10 at 10:41 -0600, Mark Hatle wrote:
> > Just wondering if there is any status on the progress of moving  
> > the trap
> > handlers to 2.6.19 or newer?
> >
> > Thanks,
> > Mark
> >
> > Steve Papacharalambous wrote:
> > > Hi Kumar,
> > >
> > > My apologies, I should have posted this to the list earlier. :-(
> > >
> > > There are kernel patches for e500 floating point trap handling  
> > > available
> > > from the ltib gpp, see link below.  In addition these have been  
> > > ported
> > > to 2.6.19 and should be posted on the gpp in the next couple of  
> > > weeks,
> > >
> > > Best regards,
> > >
> > > Steve
> > >
> > > On Fri, 2006-12-15 at 01:36 +0000, Joseph S. Myers wrote:
> > > > On Mon, 11 Dec 2006, Steve Papacharalambous wrote:
> > > >
> > > > > Hi Joseph,
> > > > >
> > > > > I believe that these kernel patches have been released, you can  
> > > > > get the
> > > > > patches from:
> > > > > http://www.bitshrine.org/autodocs/bsp_ext_ava_mpc8548cds.html
> > > > >
> > > > > I think that the IEEE754 patches are the one that you need,
> > > > Thanks - you will have seen Kumar Gala's message on the EGLIBC  
> > > > patches
> > > > list <http://www.eglibc.org/archives/patches/msg00018.html>  
> > > > saying "there
> > > > isn't any code today that does this", could you respond to that  
> > > > list
> > > > message explaining the current status of these patches and any  
> > > > plans for
> > > > merging them into kernel.org kernels, to avoid list readers  
> > > > duplicating
> > > > effort?
> > > >
> > > > The patches definitely need at least refreshing against 2.6.19,  
> > > > they
> > > > affect files that are no longer in the locations shown in those  
> > > > patches,
> > > > and so would probably be difficult for anyone to use as is with  
> > > > a current
> > > > kernel.