From: Artem Bityutskiy <dedekind1@gmail.com>
To: George Pontis <GPontis@z9.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: atmel_nand, DMA, and "Fall back to CPU I/O"
Date: Wed, 02 May 2012 14:53:39 +0300 [thread overview]
Message-ID: <1335959619.10293.41.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <037801cd2330$0cd747d0$2685d770$@com>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Wed, 2012-04-25 at 15:09 -0700, George Pontis wrote:
> Working with 3.0.13 kernel and the at91sam9g45, 8b NAND flash with rootfs in
> NAND
>
> At boot, the kernel shows 22 DMA warnings, then another 260 as UBIFS mounts
> the root FS:
>
> atmel_nand atmel_nand: Fall back to CPU I/O
>
Unfortunately UBI and UBIFS use vmalloced memory for I/O and many people
yelled but no one cared to fix this. I think we should make UBI/UBIFS to
use kmalloc()'ed memory instead.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-02 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 22:09 atmel_nand, DMA, and "Fall back to CPU I/O" George Pontis
2012-05-02 11:53 ` Artem Bityutskiy [this message]
2012-05-02 19:32 ` Brian Norris
2012-05-03 10:35 ` Artem Bityutskiy
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=1335959619.10293.41.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=GPontis@z9.com \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).