RE: Patches merged to split OMAP2_IO_ADDRESS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Shilimkar, Santosh
> Sent: Friday, October 09, 2009 10:51 AM
> To: Tony Lindgren
> Cc: linux-omap@xxxxxxxxxxxxxxx; Paul Walmsley
> Subject: RE: Patches merged to split OMAP2_IO_ADDRESS
> 
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx]
> > Sent: Thursday, October 08, 2009 11:38 PM
> > To: Shilimkar, Santosh
> > Cc: linux-omap@xxxxxxxxxxxxxxx; Paul Walmsley
> > Subject: Re: Patches merged to split OMAP2_IO_ADDRESS
> >
> > * Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [091008 03:59]:
> > > Tony,
> > >
> > > > -----Original Message-----
> > > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
> > > > owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren
> > > > Sent: Thursday, October 08, 2009 5:55 AM
> > > > To: linux-omap@xxxxxxxxxxxxxxx
> > > > 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.
> 
> Boot tested on OMAP4430 with 512MB and dmesg don't show any overlaps. Will
> run some memory test tomorrow.
> 
Run the memmark benchmark on OMAP4430 and not seen any issue.

Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux