linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: ext Steve Sakoman <sakoman@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: DSS2 failure with current linux-omap head
Date: Tue, 25 May 2010 15:46:31 -0700	[thread overview]
Message-ID: <20100525224630.GK9645@atomide.com> (raw)
In-Reply-To: <1274429232.4246.65.camel@tubuntu.research.nokia.com>

* Tomi Valkeinen <tomi.valkeinen@nokia.com> [100521 01:03]:
> On Thu, 2010-05-20 at 00:33 +0200, ext Steve Sakoman wrote:
> > I did a quick test build of the current linux-omap head and get a
> > failure very early on in the boot process in
> > drivers/video/omap2/vram.c code:
> > 
> > 	Illegal SDRAM size for VRAM
> > 
> > It is generated by the following code:
> > 
> > 	bdata = NODE_DATA(0)->bdata;
> > 	sdram_start = bdata->node_min_pfn << PAGE_SHIFT;
> > 	sdram_size = (bdata->node_low_pfn << PAGE_SHIFT) - sdram_start;
> > 
> > 	if (paddr) {
> > 		if ((paddr & ~PAGE_MASK) || paddr < sdram_start ||
> > 				paddr + size > sdram_start + sdram_size) {
> > 			pr_err("Illegal SDRAM region for VRAM\n");
> > 			return;
> > 		}
> > 
> > 		if (reserve_bootmem(paddr, size, BOOTMEM_EXCLUSIVE) < 0) {
> > 			pr_err("FB: failed to reserve VRAM\n");
> > 			return;
> > 		}
> > 	} else {
> > 		if (size > sdram_size) {
> > 			pr_err("Illegal SDRAM size for VRAM\n");
> > 			return;
> > 		}
> > 
> > 		paddr = virt_to_phys(alloc_bootmem_pages(size));
> > 		BUG_ON(paddr & ~PAGE_MASK);
> > 	}
> > 
> > 
> > I modified the error pr_error to display the two values that are
> > compared to generate this error:
> > 
> > Illegal SDRAM size for VRAM: size=0xc00000 sdram_size=0x0
> > 
> > So it appears that the method used to get the sdram size no longer
> > works since it returns a size of 0!
> 
> I copied the method from the older omapfb driver, and I have to say that
> I've never looked at what it actually does. Perhaps there's a proper way
> to get the RAM starts and sizes somewhere...

FYI, Russell has several interesting omapfb patches in his lmb branch.
Please take a look at that, might make your life easier :)

Regards,

Tony

      parent reply	other threads:[~2010-05-25 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 22:33 DSS2 failure with current linux-omap head Steve Sakoman
2010-05-21  8:07 ` Tomi Valkeinen
2010-05-24 21:38   ` Raghu
2010-05-25 22:46   ` Tony Lindgren [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=20100525224630.GK9645@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@gmail.com \
    --cc=tomi.valkeinen@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).