From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Blackfin BF547 board testing.
Date: Wed, 22 Aug 2012 11:33:23 -0400 [thread overview]
Message-ID: <201208221133.24428.vapier@gentoo.org> (raw)
In-Reply-To: <00fc01cd8078$beaef3e0$2901a8c0@dpn>
On Wednesday 22 August 2012 11:13:54 Dimitar Penev wrote:
> - GCC assumes rev 0.2 of the CPU is this OK with the rev 0.4 which we have
> on board?
err, gcc assumes nothing. this is controlled by your board config's
CONFIG_BFIN_CPU setting.
> The first reason for this behavior seems to be memory issue.
hardware (and certainly linux) issues are probably better diagnosed on the ADI
support forums:
http://ez.analog.com/community/dsp/blackfin-processors
http://ez.analog.com/community/dsp/software-and-development-tools
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120822/402b4fdb/attachment.pgp>
prev parent reply other threads:[~2012-08-22 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:13 [U-Boot] Blackfin BF547 board testing Dimitar Penev
2012-08-22 15:33 ` Mike Frysinger [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=201208221133.24428.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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