From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Jun Sun" <jsun@mvista.com>, "Jim Paris" <jim@jtan.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"Linux/MIPS Development" <linux-mips@oss.sgi.com>
Subject: Re: ISA
Date: Tue, 1 Jan 2002 14:34:24 -0500 [thread overview]
Message-ID: <016d01c192fb$518a9dd0$5601010a@prefect> (raw)
In-Reply-To: 20020101112223.A14847@mvista.com
----- Original Message -----
From: "Jun Sun" <jsun@mvista.com>
To: "Jim Paris" <jim@jtan.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>; "Geert Uytterhoeven"
<Geert.Uytterhoeven@sonycom.com>; "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>;
"Linux/MIPS Development" <linux-mips@oss.sgi.com>
Sent: Tuesday, January 01, 2002 2:22 PM
Subject: Re: ISA
> 1. each address space has an id.
> 2. kernel pre-defines a couple of well-known ones, 0 for CPU physical,
> 1 for virtual, etc.
> 3. When drivers discover the devices, they get the address and also
> the address space id where the address resides.
> 4. there are a set of macro's that converts/maps an address or an
> address region from one space to another.
The first thing that jumps out at me is that now every bus access has an
added switch in it.
Either that or drivers would get back access function pointers, but that
eliminates the chance to inline trivial bus accesses.
Regards,
Brad
next prev parent reply other threads:[~2002-01-01 20:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 20:04 ISA Jim Paris
2001-12-18 20:27 ` ISA Bradley D. LaRonde
2001-12-18 20:27 ` ISA Bradley D. LaRonde
2001-12-18 21:44 ` ISA Jim Paris
2001-12-18 22:01 ` ISA Maciej W. Rozycki
2001-12-18 22:24 ` ISA Jim Paris
2001-12-19 1:17 ` ISA Jun Sun
2001-12-19 1:50 ` ISA Maciej W. Rozycki
2001-12-19 2:05 ` ISA Bradley D. LaRonde
2001-12-19 2:05 ` ISA Bradley D. LaRonde
2001-12-19 2:09 ` ISA Jun Sun
2001-12-19 2:30 ` ISA Maciej W. Rozycki
2001-12-19 9:52 ` ISA Geert Uytterhoeven
2001-12-19 13:59 ` ISA Alan Cox
2001-12-19 13:59 ` ISA Alan Cox
2001-12-19 14:06 ` ISA Geert Uytterhoeven
2001-12-20 13:09 ` ISA Maciej W. Rozycki
2001-12-20 13:14 ` ISA Geert Uytterhoeven
2001-12-20 13:39 ` ISA Maciej W. Rozycki
2001-12-20 13:45 ` ISA Geert Uytterhoeven
2001-12-20 14:06 ` ISA Maciej W. Rozycki
2001-12-21 16:12 ` ISA Alan Cox
2001-12-21 16:12 ` ISA Alan Cox
2001-12-21 18:44 ` ISA Jim Paris
2002-01-01 19:22 ` ISA Jun Sun
2002-01-01 19:34 ` Bradley D. LaRonde [this message]
2002-01-02 1:03 ` ISA M. Warner Losh
2002-01-02 9:41 ` ISA Geert Uytterhoeven
2002-01-02 14:36 ` ISA Bradley D. LaRonde
2002-01-01 20:13 ` ISA Alan Cox
2002-01-01 20:13 ` ISA Alan Cox
2001-12-19 1:28 ` ISA Maciej W. Rozycki
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='016d01c192fb$518a9dd0$5601010a@prefect' \
--to=brad@ltc.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jim@jtan.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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.