From: Holger Schurig <holgerschurig@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org, gianluca <gianlucarenzi@eurek.it>
Subject: Re: Ethernet PHY KSZ9031 is not working
Date: Wed, 16 Mar 2016 13:34:24 +0100 [thread overview]
Message-ID: <87zityiotr.fsf@gmail.com> (raw)
In-Reply-To: <20160309085831.GA1563@omega> (Alexander Aring's message of "Wed, 9 Mar 2016 09:58:37 +0100")
Alexander Aring <alex.aring@gmail.com> writes:
> do you know why memtester from Linux found issues?
No, I actually didn't even look into the source code.
> I saw some people which use memtester under Linux and randomly
> "MTD/filesystem broken" messages blobs out while running memtester. I would
> guess that the memtester written in some memory mapped area of connected
> NAND devices.
In my case this wasn't the issue ... I don't have NAND in my hardware.
Later, when our hardware guy fixed layout and DDR3 timing values with
the Freescale tool, memtester worked perfectly. Barebox' memory test
however didn't show an error before the rework ... and afterwards also
not :-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-16 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 12:44 gianluca
2016-03-03 13:52 ` Antony Pavlov
2016-03-03 13:47 ` gianluca
2016-03-03 15:21 ` Antony Pavlov
2016-03-04 11:12 ` Ethernet PHY KSZ9031 is not working [SOLVED] gianluca
2016-03-03 14:42 ` Ethernet PHY KSZ9031 is not working Holger Schurig
2016-03-09 8:58 ` Alexander Aring
2016-03-16 12:34 ` Holger Schurig [this message]
2016-03-03 14:53 ` Sascha Hauer
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=87zityiotr.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=gianlucarenzi@eurek.it \
/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