From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Subject: Re: grackle, patches, MMU, ...
Date: Wed, 30 Dec 1998 12:35:59 +0100 [thread overview]
Message-ID: <19981230123559.019295@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.03.9812301219080.15589-100000@mercator.cs.kuleuven.ac.be>
On Wed, Dec 30, 1998, Geert Uytterhoeven
<Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:
>Grackle is the host bridge, right? In that case it's always device 0 / bus 0.
Yep.
>But for user space, we're still stuck with a normal mapping. And there speed
>is
>more important, I think, since most people (R5 installers? :-) run X and
don't
>use the text console that much.
Yes, having a way to use BATs for large user-space mappings would be a
benefit for framebuffer and also for other devices like frame grabbers.
I'm not familiar enough yet with the user-side MM stuff to implement this
now, but if no one does it, I'll try it as soon as I have undersood
enough things there.
BTW. Geert: Since you are working on m68k too, do you know if linux-m68k
uses the same adb code as linux-ppc ? I'm working on a new adb.c/.h,
which cleans up things (especially "hook-like" entry points to the
controller by exporting functions for registering hardware controllers
(via a structure with function pointers)) and for registering devices
(also a structure with function pointers with more entrypoint to allow
proper re-probing when a bus reset is done for example) and I would like
to know if there are risk I break m68k while doing so. Currently,
adb.c/.h is in arch/ppc but I don't know if vger is the main repository
for m68k too or not
--
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-30 11:35 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 [this message]
1998-12-30 13:21 ` Geert Uytterhoeven
1998-12-31 21:52 ` Cort Dougan
1998-12-31 22:24 ` Benjamin Herrenschmidt
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=19981230123559.019295@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--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).