linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Desnoyers <pdesnoyers@chinook.com>
To: Dan Malek <dan@mvista.com>
Cc: "Justin (Gus) Hurwitz" <ghurwitz@dyndns.com>,
	Daris A Nevil <dnevil@snmc.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Non-cacheable memory
Date: Mon, 13 Aug 2001 11:47:16 -0400	[thread overview]
Message-ID: <3B77F684.415638E8@chinook.com> (raw)
In-Reply-To: 3B74AADC.C2CE7B89@mvista.com


Dan Malek wrote:
>
> Peter Desnoyers wrote:
>
> > ..... It returns a virtual address plus a DMA
> > address in an arg ptr - throw away the DMA address, as that's
> > PCI-specific, and run the virtual address through virt_to_phys().
>
> Ummm...damn, that's a tricky one.  On 8xx, the intention is to use
> the DMA address for stuffing into the CPM.

Yow.  So the MBX860 setup, for instance, with PCI_DRAM_OFFSET=2gig, just
won't work.

This seems like another case of either too little abstraction, or too
much.  An embedded PPC system with PCI basically has two buses, with
different DMA addressing, and there's no way to tell consistent_alloc(),
etc. about that.

> The virt_to_* functions
> are on their way out (on all platforms), and everyone should use the
> DMA address returned by the consistent_alloc function.

Jeez, you look the other way for a little while :-)  The last time I was
doing Linux driver development was in 1999, and virt_to_* was still
getting phased in, it seemed...

If you wouldn't mind, could you give me a pointer to the discussion of
this phase-out?

> I guess if you
> have a 8xx/PCI that doesn't map PCI masters to system memory at zero,
> you are kind of hosed at the moment........

I wonder if the proper thing to do is to enhance consistent_alloc to
take an argument indicating the bus type?  There are more elegant ways
of doing things, but this wouldn't involve changes to a lot of code.

--
.....................................................................
 Peter Desnoyers            (781) 457-1165   pdesnoyers@chinook.com
 Chinook Communications     (617) 661-1979   pjd@fred.cambridge.ma.us
 100 Hayden Ave, Lexington MA 02421

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-13 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 18:49 Non-cacheable memory Justin (Gus) Hurwitz
2001-08-07 15:59 ` Tom Roberts
2001-08-07 18:34   ` Daris A Nevil
2001-08-09 22:49     ` Justin (Gus) Hurwitz
2001-08-09 19:27       ` Peter Desnoyers
2001-08-11  3:47         ` Dan Malek
2001-08-13 15:47           ` Peter Desnoyers [this message]
2001-08-14 21:26             ` 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=3B77F684.415638E8@chinook.com \
    --to=pdesnoyers@chinook.com \
    --cc=dan@mvista.com \
    --cc=dnevil@snmc.com \
    --cc=ghurwitz@dyndns.com \
    --cc=linuxppc-embedded@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).