All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] PPC4xx: Minimal changes to add vxWorks support
Date: Fri, 30 Nov 2007 09:11:45 -0500	[thread overview]
Message-ID: <47501A21.2010107@ge.com> (raw)
In-Reply-To: <200711301501.58665.niklausgiger@gmx.ch>

Niklaus Giger wrote:
> Hi
> 
> I have to support vxWorks on our boards. In order to avoid changing the TLB
> in all PPC440x based boards  I need this small patch. Can it go into the
> git repository or do I have to maintain it out of the tree forever?
> 
> Best regards
> 
> Signed-off-by: Niklaus Giger <niklaus.giger@netstal.com>
> ---
>  cpu/ppc4xx/start.S |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/cpu/ppc4xx/start.S b/cpu/ppc4xx/start.S
> index 9626b65..8f19444 100644
> --- a/cpu/ppc4xx/start.S
> +++ b/cpu/ppc4xx/start.S
> @@ -1432,7 +1432,10 @@ relocate_code:
>  	dccci	0,0			/* Invalidate data cache, now no longer our stack */
>  	sync
>  	isync
> -	addi	r1,r0,0x0000		/* TLB entry #0 */
> +#ifndef CFG_TLB_FOR_BOOT_FLASH
> +#define CFG_TLB_FOR_BOOT_FLASH 0
> +#endif
> +	addi	r1,r0,CFG_TLB_FOR_BOOT_FLASH	/* TLB entry (default #0) */
>  	tlbre	r0,r1,0x0002		/* Read contents */
>  	ori	r0,r0,0x0c00		/* Or in the inhibit, write through bit */
>  	tlbwe	r0,r1,0x0002		/* Save it out */

Hi Niklaus,

I don't know the answer to your question, but the following alternate 
construct is cleaner (and cleaner may help get acceptance ;-):

#ifdef CFG_TLB_FOR_BOOT_FLASH
	addi	r1,r0,CFG_TLB_FOR_BOOT_FLASH	/* Use defined TLB */
#else
	addi	r1,r0,0x0000		/* Default TLB entry is #0 */
#endif

Best regards,
gvb

  reply	other threads:[~2007-11-30 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 14:01 [U-Boot-Users] [PATCH] PPC4xx: Minimal changes to add vxWorks support Niklaus Giger
2007-11-30 14:11 ` Jerry Van Baren [this message]
2007-11-30 19:54   ` Stefan Roese

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=47501A21.2010107@ge.com \
    --to=gerald.vanbaren@ge.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.