public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems using vxboot
Date: Mon, 22 Aug 2011 12:23:12 +0200	[thread overview]
Message-ID: <m2bovhu4mn.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1QrmtL-1NYgTI0@fwd12.aul.t-online.de> (Reinhard's message of "Fri, 12 Aug 2011 10:14:55 +0200")


Hi Reinhard,

> i do not find a requirement that the cache needs to be off in the vxWorks manuals.
>  
> The entry point sysInit(int) intended by Windriver to be called from
> the vxWorks bootrom, a very small vxWorks system.
> The routine is called by the go() handler in the bootrom, that clears
> the cache from start of image to end of usable memory.
>  
> The POWERPC implementations only invalidates and disable the cache,
> the ARM implementations also flush it.
>  
>  U-boot will be on the save side, if it disables the data cache before
> calling vxWorks sysInit(int).

Then put this information in the commit log and resend your patch - I
don;t see why it should not be merged.

Thanks
  Detlev

-- 
Music scenes ain't real life / They won't get rid of the bomb
Won't eliminate rape / Or bring down the banks / any kind of change
Takes more time and work / than changing channels on a TV set
                                        -- Jello Biafra
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2011-08-22 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12  8:14 [U-Boot] Problems using vxboot Reinhard.Arlt at t-online.de
2011-08-22 10:23 ` Detlev Zundel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-06  8:12 Reinhard Arlt
2011-08-10  9:40 ` Detlev Zundel

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=m2bovhu4mn.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox