mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: volodya@mindspring.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm question
Date: Mon, 10 Dec 2001 12:38:38 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.20.0112101230440.17940-100000@node2.localnet.net> (raw)
In-Reply-To: <E16DUAv-0002hY-00@the-village.bc.nu>



On Mon, 10 Dec 2001, Alan Cox wrote:

> > "AGP addressable" memory which is ~64meg less than the total amount on my
> > machine. However, looking around in AGP driver or AGP specs does not seem
> > to indicate any restriction of the sort and, moreover, I do not need AGP
> > for this DMA transfer (it is PCI only).
> 
> Can the transfer go to pages mapped into the AGP gart, using their gart
> side mapping ?

Yes, but agpgart will not let more then one driver use it. So it will be
_either_ 3d or video capture with switching upon Xserver restart. Sucks !

> 
> > Better than giving up.. Unfortunately looking around in
> > linux/Documentation and drivers did not yield much in terms of
> > explanation. I know I can use mem_map_reserve to reserve a page but I
> > don't know how to get page struct from a physical address nor which lock
> > to use when messing with this.
> 
> You have to grab them at boot time via bootmem to get them in a range of

Does this imply that the driver must be compiled into the kernel ? In that
case I'll need to allocate at least 2meg of ram for each capture card..

> your choice. Otherwise you can use
> 
> 	get_free_page		-	grab a page
> 	virt_to_page		-	page struct of page
> 	virt_to_bus		-	bus addr of page
> 
> virt_to_bus isnt portable because real world pci bus mapping on non x86 is
> deeply murky and mysterious. But you probably want to worry about that
> after it works.

Yes, I almost went all the way rewriting the code in accordance with
DMA-mapping.txt thinking I am using "non-DMAable" memory or something 
until I noticed that all the functions are inlined to trivial for x86.

                           Vladimir Dergachev

> 
> Alan
> 


  reply	other threads:[~2001-12-10 17:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 13:25 volodya
2001-12-10 13:46 ` Alan Cox
2001-12-10 13:47   ` volodya
2001-12-10 14:07     ` Alan Cox
2001-12-10 15:03       ` volodya
2001-12-10 15:21         ` Alan Cox
2001-12-10 15:40           ` Rik van Riel
2001-12-10 16:14             ` volodya
2001-12-10 16:48               ` Rik van Riel
2001-12-10 17:02                 ` volodya
2001-12-10 17:16               ` Alan Cox
2001-12-10 17:29                 ` volodya
2001-12-10 18:05                   ` Rik van Riel
2001-12-10 18:08                     ` volodya
2001-12-10 18:17                       ` Rik van Riel
2001-12-10 21:30                         ` volodya
2001-12-10 18:26                       ` Alan Cox
2001-12-10 21:27                         ` volodya
2001-12-10 21:42                           ` Alan Cox
2001-12-11  1:52                             ` volodya
2001-12-11  8:47                               ` Eric W. Biederman
2001-12-11 11:07                                 ` volodya
2001-12-11 18:39                                   ` Daniel Phillips
2001-12-10 16:05           ` volodya
2001-12-10 17:09             ` Martin J. Bligh
2001-12-10 17:16               ` Martin J. Bligh
2001-12-10 17:26               ` volodya
2001-12-10 17:25             ` Alan Cox
2001-12-10 17:38               ` volodya [this message]
2001-12-10 17:51                 ` Alan Cox
2001-12-10 17:43                   ` volodya
2001-12-10 18:12                     ` Alan Cox

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=Pine.LNX.4.20.0112101230440.17940-100000@node2.localnet.net \
    --to=volodya@mindspring.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®