From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] SPARC: CFI flash_read64 is defined a weak function.
Date: Sat, 29 Mar 2008 07:08:52 +0100 [thread overview]
Message-ID: <200803290708.52675.sr@denx.de> (raw)
In-Reply-To: <1206733219-23179-1-git-send-email-daniel@gaisler.com>
On Friday 28 March 2008, Daniel Hellstrom wrote:
> SPARC has implemented __raw_readq, it reads 64-bit from any 32-bit address.
> SPARC CPUs implement flash_read64 which calls __raw_readq.
>
> For current SPARC architectures (LEON2 and LEON3) each read from the
> FLASH must lead to a cache miss. This is because FLASH can not be set
> non-cacheable since program code resides there, and alternatively disabling
> cache is poor from performance view, or doing a cache flush between each
> read is even poorer.
>
> Forcing a cache miss on a SPARC is done by a special instruction "lda" -
> load alternative space, the alternative space number (ASI) is processor
> implementation spcific and can be found by including <asm/processor.h>.
Added to cfi-flash repository. Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2008-03-29 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 19:40 [U-Boot-Users] [PATCH] SPARC: CFI flash_read64 is defined a weak function Daniel Hellstrom
2008-03-29 6:08 ` Stefan Roese [this message]
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=200803290708.52675.sr@denx.de \
--to=sr@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