From: Stanislav Brabec <utx@penguin.cz>
To: Andy Green <andy@warmcat.com>
Cc: Cyril Hrubis <metan@ucw.cz>, Pavel Machek <pavel@ucw.cz>,
Eric Miao <eric.y.miao@gmail.com>,
dbaryshkov@gmail.com, arminlitzel@web.de,
kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, lenz@cs.wisc.edu, rpurdie@rpsys.net,
omegamoon@gmail.com, thommycheck@gmail.com,
zaurus-devel@www.linuxtogo.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: bit errors on spitz
Date: Thu, 11 Mar 2010 16:42:35 +0100 [thread overview]
Message-ID: <1268322155.3990.114.camel@hammer.suse.cz> (raw)
In-Reply-To: <4B98EF5D.5000609@warmcat.com>
Andy Green wrote:
> I saw very similar failures for a long time on our iMX31 based device.
> Eventually I found a Freescale errata where the RAM inside the USB2
> macrocell started to make single bit errors below 1.38V Vcore; ours was
> 1.4V at that time but dipped on CPU load.
Good tip. It seems that nobody ported driver for the voltage control
chip ISL6271 from 2.4 kernel, and bootloader probably does not set
correct values.
Datasheet:
http://www.penguin.cz/~utx/zaurus/datasheets/power/Xscale/ISL6271.pdf
--
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
next prev parent reply other threads:[~2010-03-11 15:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 21:27 Pavel Machek
2010-03-08 5:37 ` Eric Miao
2010-03-08 7:28 ` Pavel Machek
2010-03-08 8:25 ` Cyril Hrubis
2010-03-08 11:48 ` Stanislav Brabec
2010-03-08 12:16 ` Cyril Hrubis
2010-03-08 12:42 ` Russell King - ARM Linux
2010-03-08 13:32 ` Cyril Hrubis
2010-06-03 0:01 ` [URGENT] Re: bit errors on spitz + voipac Marek Vasut
2010-06-03 2:30 ` Eric Miao
2010-03-21 20:40 ` bit errors on spitz Pavel Machek
2010-03-11 13:25 ` Andy Green
2010-03-11 15:42 ` Stanislav Brabec [this message]
2010-03-11 21:21 ` Andy Green
2010-03-12 9:07 ` Stanislav Brabec
2010-03-12 9:33 ` Andy Green
2010-03-12 10:43 ` Stanislav Brabec
2010-03-12 11:13 ` Andy Green
2010-03-21 20:43 ` Pavel Machek
2010-03-21 21:42 ` Stanislav Brabec
2010-03-29 18:27 ` Pavel Machek
2010-03-29 18:52 ` Stanislav Brabec
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=1268322155.3990.114.camel@hammer.suse.cz \
--to=utx@penguin.cz \
--cc=Dirk@opfer-online.de \
--cc=andy@warmcat.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=zaurus-devel@www.linuxtogo.org \
/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
all inboxes | Powered by JetHome®