linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Sakoman <sakoman@gmail.com>
To: linux-omap@vger.kernel.org
Subject: DSS2 failure with current linux-omap head
Date: Wed, 19 May 2010 15:33:41 -0700	[thread overview]
Message-ID: <AANLkTimwJFtTcL-V8cpXAflw0Qt0y7DOBmLd2HLManBK@mail.gmail.com> (raw)

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

             reply	other threads:[~2010-05-19 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 22:33 Steve Sakoman [this message]
2010-05-21  8:07 ` DSS2 failure with current linux-omap head Tomi Valkeinen
2010-05-24 21:38   ` Raghu
2010-05-25 22:46   ` Tony Lindgren

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=AANLkTimwJFtTcL-V8cpXAflw0Qt0y7DOBmLd2HLManBK@mail.gmail.com \
    --to=sakoman@gmail.com \
    --cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).