All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: "Nayak, Rajendra" <rnayak@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 08/16] OMAP3: Populate scratchpad contents
Date: Wed, 29 Oct 2008 16:35:37 -0700	[thread overview]
Message-ID: <4908F349.2050100@deeprootsystems.com> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE89671620369796DED@dlee02.ent.ti.com>

Woodruff, Richard wrote:
>>> +   arm_context_addr = io_v2p(omap3_arm_context);
> 
>> strange is how the code is still working.
> 
> Probably just corrupts some DDR a bit higher up.

Hmm, "just" corrupting memory?  ;)

I assume memory is being corrupted, but it also given an address in the 
virtual memory map of the kernel.  How is the ROM code halding a virtual 
address?  Just ignoring the upper bits?

>> I believe what is intented is for arm_context_addr to be a physical
>> memory address, right?  I've converted this to virt_to_phys().
> 
> Yes virt_to_phys() should be here.  Current 2.6.24 kernel's do it this way also.

Which begs the question why the patch sent to the list is using io_p2v() 
introducing a bug which was only caught by accident because it also 
introduced a compiler warning.

Kevin

  reply	other threads:[~2008-10-29 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 12:18 [PATCH 08/16] OMAP3: Populate scratchpad contents Rajendra Nayak
2008-10-29 21:14 ` Kevin Hilman
2008-10-29 21:35   ` Woodruff, Richard
2008-10-29 23:35     ` Kevin Hilman [this message]
2008-10-30  0:33       ` Woodruff, Richard

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=4908F349.2050100@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.com \
    --cc=rnayak@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.