linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Improve MMC performance on Versatile Express
Date: Mon, 24 Jan 2011 16:30:30 +0000	[thread overview]
Message-ID: <20110124163030.GD24104@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110124162400.GC24104@n2100.arm.linux.org.uk>

On Mon, Jan 24, 2011 at 04:24:00PM +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 24, 2011 at 04:13:14PM +0000, Pawel Moll wrote:
> > > The real answer is to avoid PIO mode, and use DMA support.
> > > However,
> > > I've had problems using DMA on the ARM development boards.  You can
> > 
> > Well, using DMA won't be easy on VE, will it? ;-) Besides even with
> > this, in some extreme situation, the bus could be potentially stalled
> > long enough to cause an underrun. Yes, very unlikely, but not impossible.
> 
> I'm running SD rootfs alongside NFS/ssh/NTP and the buggy ISP1761.  With the
> pile of 'fixes' patches I have here (which are currently stuck with various
> maintainers) I have a completely stable system.
> 
> I've also had it running gstreamer on CLCD with AACI too, again with SD
> rootfs.  Provided the video is already loaded off the SD card (because
> the transfer rate is too slow) it's fine.
> 
> The only remaining problem I have with it is !"?$%% busybox shell which
> doesn't like readonly rootfs with command history.  The last command is
> /sbin/reboot - I'm sure you can imagine what keeps on happening,
> particularly at the most annoying points in time.

I should also point out that my Versatile Express has been on continuously
for the last two to three weeks, running off SD rootfs, and since fixing
the ISP1761 driver and MMC block driver error handling there's been zero
issues with MMC or ISP1761.

So, MMCI overruns is now a complete non-issue for me.

  reply	other threads:[~2011-01-24 16:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 13:59 [PATCH] arm: Improve MMC performance on Versatile Express Pawel Moll
2011-01-21 15:09 ` Sergei Shtylyov
2011-01-21 19:59 ` Nicolas Pitre
2011-01-21 21:51   ` Russell King - ARM Linux
2011-01-21 22:20     ` Nicolas Pitre
2011-01-21 22:29       ` Russell King - ARM Linux
2011-02-01 14:29         ` Linus Walleij
2011-02-01 17:25           ` Pawel Moll
2011-01-24 12:27   ` Pawel Moll
2011-01-24 13:35     ` Russell King - ARM Linux
2011-01-24 16:13       ` Pawel Moll
2011-01-24 16:24         ` Russell King - ARM Linux
2011-01-24 16:30           ` Russell King - ARM Linux [this message]
2011-01-24 16:39           ` Pawel Moll
2011-01-24 16:53             ` Russell King - ARM Linux
2011-01-24 17:03               ` Russell King - ARM Linux
2011-01-24 17:54                 ` Pawel Moll
2011-01-24 18:09                   ` Russell King - ARM Linux
2011-01-24 19:59                     ` Pawel Moll
2011-01-24 23:10                       ` Russell King - ARM Linux
2011-02-01 11:18                         ` Russell King - ARM Linux
2011-02-01 13:34                           ` Pawel Moll
2011-02-01 14:28                             ` Russell King - ARM Linux
2011-02-01 17:25                               ` Pawel Moll
2011-02-03 14:15       ` Linus Walleij

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=20110124163030.GD24104@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@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).