From mboxrd@z Thu Jan 1 00:00:00 1970 In-Reply-To: <4109B225.8020604@mvista.com> References: <41090F9A.8000901@mvista.com> <4109B225.8020604@mvista.com> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Cc: , Kumar Gala From: Kumar Gala Subject: Re: Patch for debug setcontext Date: Fri, 30 Jul 2004 09:08:53 -0500 To: Corey Minyard Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: If you can look at on of the 2.6.8-rc releases that would be good. In adding support for e500, I cleaned up some CONFIG_BOOKE references, and changed the load_4xx_dbcr0 code to just load_dbcr0 since it applies to both 4xx and Book-E. thanks - kumar On Jul 29, 2004, at 9:27 PM, Corey Minyard wrote: > I'm using stock 2.6.7. Is there a different kernel I should be using? > > -Corey > > Kumar Gala wrote: > >> >> On Jul 29, 2004, at 9:54 AM, Corey Minyard wrote: >> >>> Kumar Gala wrote: >>> >>> > I'm guessing, this should really be #if defined(CONFIG_4xx) || >>> > defined(CONFIG_BOOKE) >>> > There are a number of similar cases later in this code as well. >>> >>> That may be the case, but it is very confusing in entry.S. The >>> dbcr0 register seems to only be defined on 4xx processor, not on >>> book E. Look, for instance, at load_4xx_dbcr0:, it is only defined >>> if 4xx is enabled, not if book E is enabled. >> >> >> Corey, >> >> I think you may have an old linux-2.6 tree. I remember renaming >> load_4xx_dbcr0 to just load_dbcr0 because of such issues. Hopefully >> a newer tree (one with e500 support, if its going head_e500.S) should >> be cleaner. If not, let me know. >> >> - kumar >> ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/