From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: Patches merged to split OMAP2_IO_ADDRESS
Date: Thu, 8 Oct 2009 11:08:01 -0700 [thread overview]
Message-ID: <20091008180801.GI7417@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02BB13D268@dbde02.ent.ti.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [091008 03:59]:
> Tony,
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of Tony Lindgren
> > Sent: Thursday, October 08, 2009 5:55 AM
> > To: linux-omap@vger.kernel.org
> > Cc: Paul Walmsley
> > Subject: Patches merged to split OMAP2_IO_ADDRESS
> >
> > Hi all,
> >
> > I've pushed Santosh' patches to split OMAP2_IO_ADDRESS into
> > *_L3_IO_ADDRESS
> > and *_L4_IO_ADDRESS so we can claim more kernel address space and support
> > over 512MB of memory instead of 256MB.
> >
> > Of course, our goal is to convert everything except the .S files to
> > use ioremap() instead, but that can now be done parallel and in smaller
> > chunks.
> >
> > Please everybody, please convert your code to use ioremap(), there are
> > static mappings already in place so it should work out of the box.
> >
> > I also had add two quick patches to keep things compiling,
> > Paul can you take a look at them? I could not really test them as all
> > the code is not there yet. Will post them as a reply to this thread.
> Thanks for the merge!!
>
> I have boot tested below platforms with latest LO master.
>
> 1. OMAP3430 SDP board - BOOT OK
> 2. OMAP3 BEAGLE - BOOT OK
> 3. OMAP 4430 SDP - BOOT OK with variation of patch: http://patchwork.kernel.org/patch/50531/
Great. I guess we still have some issues on 24xx with the hwmod,
but hopefully we'll get that working again soon.
Can somebody with 512MB memory on a board try the current l-o master
and make sure things work?
Please check the dmesg for no overlaps in virtual address space,
then run some memory test like memtester.
Regards,
Tony
next prev parent reply other threads:[~2009-10-08 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 0:25 Patches merged to split OMAP2_IO_ADDRESS Tony Lindgren
2009-10-08 0:26 ` [PATCH] omap: Use ioremap for omap_hwmod instead of OMAP2_IO_ADDRESS Tony Lindgren
2009-10-08 0:28 ` [PATCH] omap: Use getnstimeofday for omap_device Tony Lindgren
2009-10-16 16:42 ` Paul Walmsley
2009-10-16 16:42 ` [PATCH] omap: Use ioremap for omap_hwmod instead of OMAP2_IO_ADDRESS Paul Walmsley
2009-10-08 10:58 ` Patches merged to split OMAP2_IO_ADDRESS Shilimkar, Santosh
2009-10-08 18:08 ` Tony Lindgren [this message]
2009-10-08 23:19 ` Nishanth Menon
2009-10-09 5:20 ` Shilimkar, Santosh
2009-10-11 8:30 ` Shilimkar, Santosh
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=20091008180801.GI7417@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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.