public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-mtd@lists.infradead.org,
	Ryan Underwood <nemesis-lists@icequake.net>
Subject: Re: Toshiba 64M limit and slram (was Toshiba ToPIC developer info)
Date: Wed, 22 Jun 2005 17:27:03 -0500	[thread overview]
Message-ID: <20050622222703.GB362@dbz.icequake.net> (raw)
In-Reply-To: <20050622211013.A26597@flint.arm.linux.org.uk>


On Wed, Jun 22, 2005 at 09:10:13PM +0100, Russell King wrote:
> > 
> > What is the best thing to do then?  Ever since slram was designed, it
> > has assumed that the user would set the mem= option appropriately.  I've
> > had the 'reserve' option pointed to me but not tried it yet.
> 
> Consider what's happening - you're telling the system that you have
> less memory than it actually has, so it only reserves (say) the first
> 512MB of memory.  It then scans the PCI bus and reserves those
> resources.

I see.  I thought the PCI resources were mapped by the BIOS and not by
the kernel, but this makes a bit more sense now.  So you are also saying
that when a PCI device becomes mapped in that region, subsequent
accesses by the CPU in that range go to physical RAM that is located
there instead of to the device's MMIO range, so the device is
inaccessible.  That would seem odd though, since in the low memory area,
certainly there is RAM underneath the range e.g.  F000:0000-FFFF, but
accesses to that area are mapped to the BIOS ROM instead.  Or the same
for the VGA framebuffer at A000:0, etc.

-- 
Ryan Underwood, <nemesis@icequake.net>

      parent reply	other threads:[~2005-06-22 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050613182441.GC23036@dbz.icequake.net>
     [not found] ` <20050613104838.GA23036@dbz.icequake.net>
     [not found]   ` <20050611231733.GA10349@dbz.icequake.net>
     [not found]     ` <1251495.1118575059614.komurojun-mbn@nifty.com>
     [not found]       ` <2687305.1118667124185.komurojun-mbn@nifty.com>
     [not found]         ` <4050205.1118836800033.komurojun-mbn@nifty.com>
     [not found]           ` <8247339.1118928170515.komurojun-mbn@nifty.com>
     [not found]             ` <5186040.1119048110920.komurojun-mbn@nifty.com>
     [not found]               ` <20050622015815.GA22559@dbz.icequake.net>
     [not found]                 ` <20050622101621.B28181@flint.arm.linux.org.uk>
2005-06-22 19:55                   ` Toshiba 64M limit and slram (was Toshiba ToPIC developer info) Ryan Underwood
2005-06-22 20:10                     ` Russell King
2005-06-22 21:21                       ` Jörn Engel
2005-06-22 22:27                       ` Ryan Underwood [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=20050622222703.GB362@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rmk@arm.linux.org.uk \
    /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