On Mon, 10 Dec 2001, Alan Hourihane wrote:
> On Sun, Dec 09, 2001 at 03:29:35PM -0500, [EMAIL PROTECTED] wrote:
> >
> > Hi, I am the maintainer of V4L capture module for All-in-Wonder cards.
> > I need some help figuring out how to interface with drm.
> >
> > The problem: the module works fine, except that (at least Radeons) want
> > physical memory from AGP addressable range. So I can either write my own
> > memory allocation routines or interface with drm to do this. The second
> > being the more preferable.
> >
> > The problem is that
> > a) drm does not export headers to other modules (nothing in
> > /usr/include/linux/drmxxxx.h
> > b) looking at drm.h and drmP.h in the driver source does not yield
> > immediate answer either. All I want is to obtain an agp addressable memory
> > chunk of a certain size.
> > ba) What are those DRM() wrappers ?
> > bb) can I simply call DRM(alloc) or do I need to "acquire" drm in a
> > certain way ?
> >
> Take a look at the driver specific *_dri.c files. You can then use
> drmAddBufs with DRM_RESTRICTED (so 3D apps don't use it) and later use
> drmMap to map your area.
Thanks for replying :))
Unfortunately this wont work as I need to do this from inside a kernel
module so it is able to expose v4l interface.
Some more questions: I've looked around drm and agpgart sourcecode and
as far as I understand (at least on x86) the memory drm allocates is
obtained anywhere with alloc_page(GFP_KERNEL). And the intel specification
for AGP3.0 explicitly states that any physical address should be
accessible. So, where does the "maximum agp addressable
memory" calculation comes from ?
thanks
Vladimir Dergachev
>
> Alan.
>
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
