From: Ralph Blach <rcblach@raleigh.ibm.com>
To: frowand@mvista.com
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: kernel mapping
Date: Tue, 16 Jan 2001 06:37:39 -0500 [thread overview]
Message-ID: <3A643283.A20200E8@raleigh.ibm.com> (raw)
In-Reply-To: 3A63BAFB.80E3980C@mvista.com
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Why do we need simulated bat registers.
Chip
Frank Rowand wrote:
>
> Dan Malek wrote:
> >
> > How come we don't use iopa() and friends for all kernel mapping
> > information? It is only defined for CONFIG_APUS, but is the right
> > thing to use on 8xx and 4xx, and probably all processors. The
> > virt_to_bus/bus_to_virt contain the quickie arithmetic hack with
> > KERNELBASE, but that isn't the right thing to do for any kmalloc()
> > or valloc() space or if you don't have BAT mapping.
> >
> > I am considering making these functions more generic, removing the
> > #ifdefs, and implementing "simulated" BAT mapping for processors
> > like the 8xx and 4xx that don't have BATs (not for 2.4, of course :-).
> >
> > Why shouldn't I do this?
> >
> > -- Dan
>
> For the 405 I had to use iopa() for virt_to_bus() because there are
> cases where I create a virtual address for IO buffers that is
> uncached, and that virtual address is not (physical address + KERNELBASE).
> I also have the beginnings of simulated BAT mapping for the 405
> (not quite there, but part way).
>
> -Frank
> --
> Frank Rowand <frank_rowand@mvista.com>
> MontaVista Software, Inc
>
[-- Attachment #2: Card for Ralph Blach --]
[-- Type: text/x-vcard, Size: 247 bytes --]
begin:vcard
n:Blach;Ralph
tel;work:919-543-1207
x-mozilla-html:TRUE
url:www.ibm.com
org:IBM MicroElectronics
adr:;;3039 Cornwallis ;RTP;NC;27709;USA
version:2.1
email;internet:rcblach@raleigh.ibm.com
x-mozilla-cpt:;15936
fn:Ralph Blach
end:vcard
next prev parent reply other threads:[~2001-01-16 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 23:13 kernel mapping Dan Malek
2001-01-16 3:07 ` Frank Rowand
2001-01-16 3:55 ` Dan Malek
2001-01-16 11:37 ` Ralph Blach [this message]
2001-01-16 16:50 ` Dan Malek
2001-01-16 17:10 ` Ralph Blach
2001-01-16 17:47 ` David Edelsohn
2001-01-16 21:57 ` Dan Malek
2001-01-17 10:51 ` Gabriel Paubert
2001-01-17 17:45 ` David Edelsohn
2001-01-16 19:56 ` Frank Rowand
2001-01-16 22:13 ` Dan Malek
2001-01-17 0:04 ` Frank Rowand
2001-01-17 7:02 ` Dan Malek
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=3A643283.A20200E8@raleigh.ibm.com \
--to=rcblach@raleigh.ibm.com \
--cc=frowand@mvista.com \
--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).