From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org,
Cort Dougan <cort@persephone.cs.nmt.edu>
Subject: Re: grackle, patches, MMU, ...
Date: Thu, 31 Dec 1998 23:24:53 +0100 [thread overview]
Message-ID: <19981231232453.013798@smtp.calvacom.fr> (raw)
In-Reply-To: <Pine.LNX.3.96.981231144829.14374A-100000@persephone.cs.nmt.edu>
On Thu, Dec 31, 1998, Cort Dougan <cort@persephone.cs.nmt.edu> wrote:
>The # of free bats depends on the machine. We'd only have all the bats
>free if we map without the BATS entirely. We don't to switch between
>mapping with and without BATS on the kernel depending on the process.
Ok. I knew for the variable number of BATs. So currently, the BATs are
set once
for all for the kernel, and stay this way in user mode. Getting them
beeing switched on a per-process basis would require changes still beyond
my current knowledge about the kernel. I'll try to understand all this
and I'll eventually code some test stuffs. Once BATs are switched, we can
use them for large ioremaps.
>PCI is a lot bigger than one bat. On prep we map all the pci space we use
>with a bat.
Yep, of course, I was thinking about what is currently allocated, and
this is usually fine for one BAT.
For the curious, MacOS uses BATs too, but it can only use BATs for PCI,
no pages :-( This makes things quite funny when trying to use several
cacheable regions on a board.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-31 22:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-30 10:37 grackle, patches, MMU, Benjamin Herrenschmidt
1998-12-30 11:22 ` Geert Uytterhoeven
1998-12-30 11:35 ` Benjamin Herrenschmidt
1998-12-30 13:21 ` Geert Uytterhoeven
1998-12-31 21:52 ` Cort Dougan
1998-12-31 22:24 ` Benjamin Herrenschmidt [this message]
1998-12-31 22:48 ` Cort Dougan
1999-01-02 15:24 ` __init, __openfirmware, etc Benjamin Herrenschmidt
1999-01-02 20:55 ` Geert Uytterhoeven
1999-01-03 9:42 ` Benjamin Herrenschmidt
1999-01-03 15:04 ` Geert Uytterhoeven
1999-01-01 20:45 ` real-root-dev patch for vger Brad Midgley
1999-01-02 20:54 ` Geert Uytterhoeven
1999-01-03 22:24 ` Brad Midgley
1999-01-03 22:38 ` Geert Uytterhoeven
1999-01-04 10:29 ` Andreas Schwab
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=19981231232453.013798@smtp.calvacom.fr \
--to=bh40@calva.net \
--cc=cort@persephone.cs.nmt.edu \
--cc=linuxppc-dev@lists.linuxppc.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).