linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* DSS2 failure with current linux-omap head
@ 2010-05-19 22:33 Steve Sakoman
  2010-05-21  8:07 ` Tomi Valkeinen
  0 siblings, 1 reply; 4+ messages in thread
From: Steve Sakoman @ 2010-05-19 22:33 UTC (permalink / raw)
  To: linux-omap

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 won't be able to spend more time on this till tomorrow.  Perhaps
someone else can take a look in the meantime.

Steve

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-05-25 22:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).