From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/9] iMX/MXS: Get ready for cache
Date: Fri, 16 Mar 2012 05:36:07 +0100 [thread overview]
Message-ID: <201203160536.07159.marex@denx.de> (raw)
In-Reply-To: <1331872405-1451-1-git-send-email-marex@denx.de>
Hi,
> This series of patches prepares iMX platforms based on MXS (i.MX28, i.MX6Q)
> for use of caches. This patchset prepares:
>
> Ethernet: FEC MXC is ready to use caches
> NAND: NAND driver is ready to use caches
> SPI/MMC: i.MX28 MMC driver is ready to use caches
Stefano, I consider these eligible for application. Most of these are
resubmissions from the mailing list, I just cobbled them together as I was
running tests on them.
Andy, you might want to review the bounce buffer business though. We'll probably
need bounce buffers in a lot of places, until we can start slowly squeezing them
into the code.
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-03-16 4:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 4:33 [U-Boot] [PATCH 0/9] iMX/MXS: Get ready for cache Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 1/9] ARM926EJS: Implement cache operations Marek Vasut
2012-03-20 7:28 ` Stefano Babic
2012-03-16 4:33 ` [U-Boot] [PATCH 2/9] i.MX28: Add cache support into the APBH DMA driver Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 3/9] i.MX28: Add cache support to MXS NAND driver Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 4/9] MMC: Implement generic bounce buffer Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 5/9] i.MX28: Do data transfers via DMA in MMC driver Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 6/9] i.MX28: Make use of the bounce buffer Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 7/9] i.MX28: Enable caches by default Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 8/9] net: force PKTALIGN to ARCH_DMA_MINALIGN Marek Vasut
2012-03-16 4:33 ` [U-Boot] [PATCH 9/9] net: fec_mxc: allow use with cache enabled Marek Vasut
2012-03-16 4:36 ` Marek Vasut [this message]
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=201203160536.07159.marex@denx.de \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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