From: Matt <mporter@kernel•crashing.org>
To: Tom Rini <trini@kernel•crashing.org>
Cc: linuxppc-embedded Linux list <linuxppc-embedded@ozlabs•org>
Subject: Re: 440EP FPU patch
Date: Thu, 31 Mar 2005 13:10:44 -0700 [thread overview]
Message-ID: <20050331131044.A29501@cox.net> (raw)
In-Reply-To: <20050331163420.GI25923@smtp.west.cox.net>; from trini@kernel.crashing.org on Thu, Mar 31, 2005 at 09:34:21AM -0700
On Thu, Mar 31, 2005 at 09:34:21AM -0700, Tom Rini wrote:
> On Thu, Mar 31, 2005 at 09:26:18AM -0700, Wade Farnsworth wrote:
> > On Fri, 2005-03-18 at 12:30, Tom Rini wrote:
> > > On Fri, Mar 18, 2005 at 01:43:11PM -0500, Jason McMullan wrote:
> > > > On Fri, 2005-03-18 at 10:06 -0600, Kumar Gala wrote:
> > > > > Can you build your patch for the lopec_defconfig and fix the errors
> > > > > associated with enabling altivec.
> > > > >
> > > > > Looks like you need to include asm/offset.h & asm/page.h in vector.S,
> > > > > however there is another build error after that.
> > > >
> > > > Thanks! That also found a linking bug, fixed in this patch.. Please
> > > > double check the call in 'AltiVecUnavalible' in head.S, and the re-load
> > > > of 'ctr' at the end of load_up_altivec, as I do not have an AltiVec
> > > > machine here.
> > >
> > > No dice:
> > > VFS: Mounted root (nfs filesystem) readonly.
> > > Freeing unused kernel memory: 100k init 4k prep
> > > floating point used in kernel (task=c03816b0, pc=c000d664)
> > > Doing some objdump'ing, that's the start of load_up_altivec.
> >
> > Hi Jason and Tom,
> >
> > Has there been any more progress on this patch?
>
> Sadly no. We got to the point where it was reliably crashing on my
> LoPEC (7400), but no time to try and fix it. The problem should show up
> on any classic PPC box..
If nobody has time to work on this, then I intend to put Wade's 440EP
support in as is (actually, he's planning on resubmitting with some
additional changes). When somebody has time, they can redo the patch
against that.
-Matt
next prev parent reply other threads:[~2005-03-31 20:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 17:17 [PATCH 1/3] PPC440EP SoC and Bamboo board support Wade Farnsworth
2005-03-15 18:41 ` Eugene Surovegin
2005-03-15 19:08 ` Wade Farnsworth
2005-03-15 20:58 ` Jason McMullan
2005-03-15 21:38 ` Wade Farnsworth
2005-03-15 18:47 ` [PATCH 2/3] PPC440EP: ibm_emac phy mode bug fix Wade Farnsworth
2005-03-15 18:58 ` [PATCH 3/3] PPC440EP IBM EMAC support Wade Farnsworth
2005-03-15 19:22 ` Eugene Surovegin
2005-03-15 19:24 ` Eugene Surovegin
2005-03-15 20:43 ` Matt Porter
2005-03-15 20:37 ` Matt Porter
2005-03-28 17:52 ` Wade Farnsworth
2005-03-15 19:31 ` 440EP FPU patch McMullan, Jason
2005-03-15 20:50 ` Matt Porter
2005-03-15 21:09 ` Kumar Gala
2005-03-15 22:18 ` Jason McMullan
2005-03-16 7:22 ` Kumar Gala
2005-03-16 22:14 ` Tom Rini
2005-03-16 22:52 ` Kumar Gala
2005-03-16 23:18 ` Tom Rini
2005-03-18 16:06 ` Kumar Gala
2005-03-18 18:43 ` Jason McMullan
2005-03-18 19:30 ` Tom Rini
2005-03-31 16:26 ` Wade Farnsworth
2005-03-31 16:34 ` Tom Rini
2005-03-31 18:45 ` Kumar Gala
2005-03-31 19:04 ` Tom Rini
2005-03-31 20:10 ` Matt [this message]
2005-03-31 20:15 ` Tom Rini
2005-03-31 23:10 ` Kumar Gala
2005-03-31 23:37 ` Josh Boyer
2005-03-16 1:43 ` [PATCH 1/3] PPC440EP SoC and Bamboo board support Josh Boyer
2005-03-16 16:09 ` Wade Farnsworth
2005-03-16 17:26 ` Jason McMullan
2005-03-16 18:04 ` Wade Farnsworth
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=20050331131044.A29501@cox.net \
--to=mporter@kernel$(echo .)crashing.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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