From: Brian Norris <computersforpeace@gmail.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Simon Falsig <simon@newtec.dk>,
linux-mtd@lists.infradead.org, Vignesh R <vigneshr@ti.com>
Subject: Re: mmap support for m25p80 device
Date: Fri, 20 Nov 2015 16:12:08 -0800 [thread overview]
Message-ID: <20151121001208.GE64635@google.com> (raw)
In-Reply-To: <20151120084152.GA26112@frolo.macqel>
On Fri, Nov 20, 2015 at 09:41:52AM +0100, Philippe De Muyter wrote:
> On Thu, Nov 19, 2015 at 01:31:19PM -0800, Brian Norris wrote:
> > On Tue, Nov 17, 2015 at 06:15:03PM -0800, Brian Norris wrote:
> > > It's not quite so simple. Read the comments in mtdchar, and you'll see
> > > that there's some layering bugs that caused us to disable MMU mmap
> > > entirely. Apparently no one cared so far. Read the comments here:
> > >
> > > commit f5cf8f07423b2677cebebcebc863af77223a4972
> > > Author: David Woodhouse <David.Woodhouse@intel.com>
> > > Date: Tue Oct 9 15:08:10 2012 +0100
> > >
> > > mtd: Disable mtdchar mmap on MMU systems
> > >
> > > But feel free to fix it.
> >
> > I see there's an old patch that never got reviewed/tested, for doing
> > this:
> >
> > http://patchwork.ozlabs.org/patch/327981/
>
> I use that patch to access a battery-back-up'ed SRAM connected to the
> WEIM bus of a Freescale i.MX6q ARM processor, and it works perfectly for
> that. On that processor, the WEIM bus maps the connected peripherals in
> the physical memory addresses range, so it is really easy to make that
> user-accessible through mmap. Only the above patch was needed.
OK, would you mind resending it, so it can get fresh eyes?
Brian
next prev parent reply other threads:[~2015-11-21 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 14:31 mmap support for m25p80 device Simon Falsig
2015-11-18 2:15 ` Brian Norris
2015-11-19 21:31 ` Brian Norris
2015-11-20 8:41 ` Philippe De Muyter
2015-11-21 0:12 ` Brian Norris [this message]
2015-11-20 4:08 ` Vignesh R
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=20151121001208.GE64635@google.com \
--to=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=phdm@macqel.be \
--cc=simon@newtec.dk \
--cc=vigneshr@ti.com \
/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.