From: Mark Jackson <mpfj-list@mimc.co.uk>
To: Jon Hunter <jon-hunter@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: DT GPMC SRAM and NOR flash support ?
Date: Tue, 05 Feb 2013 16:16:12 +0000 [thread overview]
Message-ID: <5111304C.7090706@mimc.co.uk> (raw)
In-Reply-To: <510C19FC.8090906@mimc.co.uk>
On 01/02/13 19:39, Mark Jackson wrote:
> On 01/02/13 17:12, Jon Hunter wrote:
>> Hi Mark,
>>
>> On 02/01/2013 10:56 AM, Mark Jackson wrote:
>>> There's plenty of DT support going in for NAND flash, but is there any work going on to support NOR
>>> flash ?
>>
>> What board and device are you working that is using NOR? I have a
>> OMAP2420 H4 with NOR that I have been doing a bit of maintenance for but
>> I don't spend much time on it. Eventually it will have to be done but it
>> is always good to know if there is a pressing need.
>
> We have a custom AM335x CPU board (arriving on my desk within the next few weeks) that has both NAND
> and NOR Flash.
>
>>> And how about SRAM chips or other memory mapped devices ?
>>
>> Not sure about SRAM (trying to think if I have a board with SRAM even),
>> but definitely, boards using the GPMC to interface to ethernet chips
>> need to be added.
>
> The board also contains an FRAM chip (which is just treated as SRAM).
>
> If you'd anything in the pipeline, I'm glad to help in any testing. I've created a custom cape board
> for the BeagleBone which contains the NOR flash and FRAM chips, so I'm not waiting for the new
> hardware to arrive.
I've experimented with trying to add a mtd-physmap device, but no joy.
I'm guessing that the current mtd-physmap code is (in some way) currently incompatible with the GPMC
device ?
Mark J.
next prev parent reply other threads:[~2013-02-05 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 16:56 DT GPMC SRAM and NOR flash support ? Mark Jackson
2013-02-01 17:12 ` Jon Hunter
2013-02-01 19:39 ` Mark Jackson
2013-02-05 16:16 ` Mark Jackson [this message]
2013-02-05 16:35 ` Jon Hunter
2013-02-05 16:48 ` Mark Jackson
2013-02-05 17:08 ` Jon Hunter
2013-02-07 9:51 ` Mark Jackson
2013-02-07 10:34 ` Mark Jackson
2013-02-09 0:43 ` Jon Hunter
2013-02-09 13:27 ` Ezequiel Garcia
2013-02-11 22:21 ` Jon Hunter
2013-02-12 14:36 ` Ezequiel Garcia
2013-02-13 21:07 ` Jon Hunter
2013-02-14 10:18 ` Ezequiel Garcia
2013-02-15 7:42 ` Jon Hunter
2013-03-01 21:08 ` Ezequiel Garcia
2013-03-01 21:42 ` Ezequiel Garcia
2013-03-01 22:23 ` Jon Hunter
2013-02-06 5:07 ` Mohammed, Afzal
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=5111304C.7090706@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--cc=jon-hunter@ti.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.