From: public.avatar@gmail.com ([AvataR])
To: linux-omap@vger.kernel.org
Subject: UbiFS + HWECC(?) + BeagleBoard = fail
Date: Sun, 07 Nov 2010 09:40:23 +0200 [thread overview]
Message-ID: <87iq09wpi0.fsf@gmail.com> (raw)
Hi. After moving to upstream 2.6.3{5,6,7} kernels, i forced to use jffs2
instead of ubifs, because of lot CRC errors. If i use prefetch/dma, i
can attach to ubi, make volume, write data, reboot - and got lots of CRC
errors. Without prefetch i just couldn't do anything to ubi.
Looks like hw/sw bug in ubi
next reply other threads:[~2010-11-07 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 7:40 [AvataR] [this message]
2010-11-08 11:08 ` UbiFS + HWECC(?) + BeagleBoard = fail Grazvydas Ignotas
-- strict thread matches above, loose matches on Subject: below --
2010-12-06 17:51 Luca Ceresoli
2010-12-07 10:29 Luca Ceresoli
2010-12-08 0:19 ` Charles Manning
2010-12-09 8:30 Luca Ceresoli
2010-12-15 4:13 ` Charles Manning
2010-12-15 17:35 ` Charles Manning
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=87iq09wpi0.fsf@gmail.com \
--to=public.avatar@gmail.com \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.