mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J. Scott Kasten" <jscottkasten@yahoo.com>
To: veerasena reddy <veerasena_b@yahoo.co.in>
Cc: "linux-kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: how to use TLB to prevent Linux accessing a particular memory region
Date: Tue, 16 Oct 2007 10:13:38 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710161001550.21385@pixie.tetracon-eng.net> (raw)
In-Reply-To: <431051.14949.qm@web8408.mail.in.yahoo.com>


Really, it sounds more like you want a custom driver that "owns" that 
region of memory so it's marked as used and this driver is the gate 
keeper.  I wonder if the console frame buffer driver for the mips ip32 
arch might be a good example for you as it swallows a several meg chunk of 
memory for the display.

-S-

On Tue, 16 Oct 2007, veerasena reddy wrote:

> Hi,
>
> I have a board, which has two processors ( one is MIPS
> on which Linux-2.6.18 kernel runs and another is DSP
> based processor) and 32MB DDR.
>
> Out of 32MB of DDR 8MB is reserved for use by DSP
> processor. But the MIPS processor downloads firmware
> into this reserved memory for the DSP.
>
> Now, is it possible to use the TLB to prevent Linux
> from accessing the reserved memory after the firmware
> has been downloaded?
>
> Also we'd need to remove those TLB entries if the
> firmware would ever need to be reloaded to the DSP'
> memory region.
>
> What are the APIs to be used to achieve the above?
>
>
> Thanks in advance.
>
> Regards,
> Veerasena.
>
>
>      5, 50, 500, 5000 - Store N number of mails in your inbox. Go to http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html
>
>

  reply	other threads:[~2007-10-16 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 13:36 veerasena reddy
2007-10-16 14:13 ` J. Scott Kasten [this message]
2007-10-16 14:53 ` linux-os (Dick Johnson)
2007-10-20  0:27 Jim Brooks

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=Pine.LNX.4.64.0710161001550.21385@pixie.tetracon-eng.net \
    --to=jscottkasten@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=veerasena_b@yahoo.co.in \
    /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

all inboxes | Powered by JetHome®