From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/1] r2dplus: add cfi flash support and enable it
Date: Mon, 27 Apr 2009 08:53:18 +0000 [thread overview]
Message-ID: <20090427085318.GA26521@linux-sh.org> (raw)
In-Reply-To: <1240764162-24117-1-git-send-email-plagnioj@jcrosoft.com>
On Mon, Apr 27, 2009 at 08:19:57AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 09:32 Mon 27 Apr , Paul Mundt wrote:
> > On Sun, Apr 26, 2009 at 06:42:42PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > +static struct resource flash_resource = {
> > > + .start = 0x00000000,
> > > + .end = 0x02000000,
> > > + .flags = IORESOURCE_MEM,
> > > +};
> > > +
> > > +static struct platform_device flash_device = {
> > > + .name = "physmap-flash",
> > > + .id = -1,
> > > + .resource = &flash_resource,
> > > + .num_resources = 1,
> > > + .dev = {
> > > + .platform_data = &flash_data,
> > > + },
> > > +};
> > > +
> > > static struct platform_device *rts7751r2d_devices[] __initdata = {
> > > &sm501_device,
> > > &heartbeat_device,
> > > &spi_sh_sci_device,
> > > + &flash_device,
> > > };
> > >
> > On RTS7751R2D-1 this is at least pretty bogus. By default the platform
> > has a socket-mounted MBM29F040 that is precisely 1MB, shadowed all the
> > way up to 0x04000000, with a fixed 16-bit bus width. There is the
> > possibility to hook up a larger flash to CN8 which will map directly over
> > top of that chip select space, but at least on RTS7751R2D-1, that is not
> > the default configuration.
> >
> on the R2dplus it's a s29gl256p
>
Ok, I've added this just for r2d+ boards. It's not worth special casing
the r2d_1 flash.
prev parent reply other threads:[~2009-04-27 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 16:42 [PATCH 1/1] r2dplus: add cfi flash support and enable it Jean-Christophe PLAGNIOL-VILLARD
2009-04-27 0:32 ` Paul Mundt
2009-04-27 6:19 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-27 8:53 ` Paul Mundt [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=20090427085318.GA26521@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox