Well, the good news are that, with your help, I got it working. Turns out
it was not working ealier because:
a) the struct in bmaster.c file is specific to the example,
in particular, the name of the fields is way off.
b) VIPH is only for transfers to/from VIP
On Sun, 14 Oct 2001, Keith Whitwell wrote:
> On Sun, 14 Oct 2001 14:31, [EMAIL PROTECTED] wrote:
> > On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> > > > On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > > > > Are you sure ? I am asking bec
On Sun, 14 Oct 2001 14:31, [EMAIL PROTECTED] wrote:
> On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> > > On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > > > Are you sure ? I am asking because there are newer cards with
> > > > > 64megs of RAM
On Sun, 14 Oct 2001, Keith Whitwell wrote:
> On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> > On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > > Are you sure ? I am asking because there are newer cards with 64megs of
> > > > RAM and they way AGP was marketed is to allow to extend the amo
On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > Are you sure ? I am asking because there are newer cards with 64megs of
> > > RAM and they way AGP was marketed is to allow to extend the amount of
> > > offscreen memory..
> >
> > The agp apertu
On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > Are you sure ? I am asking because there are newer cards with 64megs of
> > > RAM and they way AGP was marketed is to allow to extend the amount of
> > > offscreen memory..
> >
> > The agp apertu
On Sun, 14 Oct 2001 12:59, [EMAIL PROTECTED] wrote:
> On Sun, 14 Oct 2001, Keith Whitwell wrote:
> > > Are you sure ? I am asking because there are newer cards with 64megs of
> > > RAM and they way AGP was marketed is to allow to extend the amount of
> > > offscreen memory..
> >
> > The agp apertu
On Sun, 14 Oct 2001, Keith Whitwell wrote:
>
> >
> > Are you sure ? I am asking because there are newer cards with 64megs of
> > RAM and they way AGP was marketed is to allow to extend the amount of
> > offscreen memory..
>
> The agp aperture is implemented on the motherboard, nothing to do w
> >
> > I hope I've explained a little better above. You map the agp region into
> > the process virtual address space useing drmAddMap/drmMap, then just get
> > a regular old pointer that you can write to and read from (but reads are
> > very slow because agp is uncached)
>
> Wait a moment - I
>
> Are you sure ? I am asking because there are newer cards with 64megs of
> RAM and they way AGP was marketed is to allow to extend the amount of
> offscreen memory..
The agp aperture is implemented on the motherboard, nothing to do with which
video card you plug in. Some newer chipsets appa
On Sun, 14 Oct 2001, Keith Whitwell wrote:
>
> > Yep. What I was trying to understand is that, since I already setup my own
> > region, what can I do to it ? For example, how do I get to "AGP
> > space" addresses (as oppposed to physical or virtual).
>
> Userspace programs always deal in virt
> Yep. What I was trying to understand is that, since I already setup my own
> region, what can I do to it ? For example, how do I get to "AGP
> space" addresses (as oppposed to physical or virtual).
Userspace programs always deal in virtual addresses. You need to map the
section of agp space
On Sat, 13 Oct 2001, Keith Whitwell wrote:
>
> > Well, this explains some things - but not all of them. Perhaps you can
> > point out to me where I am wrong ?
> >
> > First of all, how PCI scatter-gather works: instead of having one
> > physically contiguous buffer to DMA in/out, we have a l
> Well, this explains some things - but not all of them. Perhaps you can
> point out to me where I am wrong ?
>
> First of all, how PCI scatter-gather works: instead of having one
> physically contiguous buffer to DMA in/out, we have a list of page-sized
> buffers and a table (not more than a f
On Sat, 13 Oct 2001, Keith Whitwell wrote:
> On Sat, 13 Oct 2001 17:32, [EMAIL PROTECTED] wrote:
> > On Sat, 13 Oct 2001, Keith Whitwell wrote:
> > > > That's what I am trying to do. With not much luck so far. The reason
> > > > (at least to me) is that the 3d driver is the interaction of 3 par
On Sat, 13 Oct 2001 17:32, [EMAIL PROTECTED] wrote:
> On Sat, 13 Oct 2001, Keith Whitwell wrote:
> > > That's what I am trying to do. With not much luck so far. The reason
> > > (at least to me) is that the 3d driver is the interaction of 3 parts:
> > > kernel drm module, XFree driver (like radeon
On Sat, 13 Oct 2001, Keith Whitwell wrote:
>
> >
> > That's what I am trying to do. With not much luck so far. The reason (at
> > least to me) is that the 3d driver is the interaction of 3 parts: kernel
> > drm module, XFree driver (like radeon_dri.c) and the dri part (whatever
> > goes into ra
-- Forwarded Message --
Subject: Re: [Dri-devel] Using drm (fwd)
Date: Sat, 13 Oct 2001 16:42:59 -0600
From: Keith Whitwell <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
> That's what I am trying to do. With not much luck so far. The reason (at
> least to m
dimir Dergachev
-- Forwarded message --
Date: Wed, 10 Oct 2001 18:08:50 -0400 (EDT)
From: [EMAIL PROTECTED]
To: Keith Whitwell <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: [Dri-devel] Using drm (fwd)
On Wed, 10 Oct 2001, Keith Whitwell wrote:
> On Wed, 10 Oct 2001 15:45, [EMAIL
On Wed, 10 Oct 2001, Keith Whitwell wrote:
>
> >
> > Finally, someone who knows the stuff :)) No, there is no such variable,
> > but this phrase I plucked from the comment. Here is an example from
> > radeon.h:
> >
> > /* CP vertex/indirect buffer data */
> > un
>
> Finally, someone who knows the stuff :)) No, there is no such variable,
> but this phrase I plucked from the comment. Here is an example from
> radeon.h:
>
> /* CP vertex/indirect buffer data */
> unsigned long bufStart;/* Offset into AGP space */
On Wed, 10 Oct 2001, Keith Whitwell wrote:
> On Wed, 10 Oct 2001 15:45, [EMAIL PROTECTED] wrote:
> > On Wed, 10 Oct 2001, Daryll Strauss wrote:
> > > On Wed, Oct 10, 2001 at 05:13:40PM -0400, [EMAIL PROTECTED] wrote:
> > > > So, can anyone answer any of the questions below, or do I have to writ
On Wed, 10 Oct 2001 15:45, [EMAIL PROTECTED] wrote:
> On Wed, 10 Oct 2001, Daryll Strauss wrote:
> > On Wed, Oct 10, 2001 at 05:13:40PM -0400, [EMAIL PROTECTED] wrote:
> > > So, can anyone answer any of the questions below, or do I have to write
> > > drm for multimedia ?
> >
> > The DRM is an arc
On Wed, 10 Oct 2001, Daryll Strauss wrote:
> On Wed, Oct 10, 2001 at 05:13:40PM -0400, [EMAIL PROTECTED] wrote:
> > So, can anyone answer any of the questions below, or do I have to write
> > drm for multimedia ?
>
> The DRM is an architecture for accessing hardware directly.
>
> What functio
On Wed, Oct 10, 2001 at 05:13:40PM -0400, [EMAIL PROTECTED] wrote:
> So, can anyone answer any of the questions below, or do I have to write
> drm for multimedia ?
The DRM is an architecture for accessing hardware directly.
What functions are implemented in any given kernel module is driven by
t
So, can anyone answer any of the questions below, or do I have to write
drm for multimedia ?
thanks
Vladimir Dergachev
> interface of doing captures. I'm currently working on a new Xv function
> (XvShmGetImage) that will do this, and
> > With Capture:
> > Allocate video memory for frames
> > Set the capture to use this video memory
> > Use the DRM to map these into client memory
> > After a frame is captured the client reads the data and stores it
> > to disk. The client then does an XvMCPutSurface to display the
> > frame on
On Mon, 8 Oct 2001, Sottek, Matthew J wrote:
>
> Vladimir,
> As Peter pointed out to me you were speaking of a video card
> with built-in capture. This _does_ require, as you stated a
> way to get the video, out of the video ram and into system ram,
> my apologies for the misunderstanding.
>
On Mon, 8 Oct 2001, Gareth Hughes wrote:
> [EMAIL PROTECTED] wrote:
>
> > After reading documentation (and confirming that I already know all the
> > acronyms) and sifting thru driver code I decided to ask on the list, while
> > the people who wrote this stuff can still answer ;)
> >
> > Ba
On Mon, Oct 08, 2001 at 06:31:24PM -0700, Gareth Hughes wrote:
> I think it'll be hard to set up and initiate DMA transfers without
> proper hardware documentation. Do you have Radeon specs?
Yes, all the developers working on this (volodya, RC and I) have docs from ATI
under NDA (well I don't ha
On Mon, Oct 08, 2001 at 06:14:13PM -0700, Sottek, Matthew J wrote:
> my apologies for the misunderstanding.
np, the point is we all learned something new :-)
> My point should still hold. The DRM should allow you to map
> an video area into a client accessible memory location.
You don't need DR
[EMAIL PROTECTED] wrote:
> After reading documentation (and confirming that I already know all the
> acronyms) and sifting thru driver code I decided to ask on the list, while
> the people who wrote this stuff can still answer ;)
>
> Basically I want to DMA a chunk of video ram into plain RAM.
On Tue, 9 Oct 2001, Peter Surda wrote:
> On Mon, Oct 08, 2001 at 03:54:14PM -0700, Sottek, Matthew J wrote:
> > The drm _does_ allow the client to mmap the video ram.
> I am not completely sure about this, but as I'm also working on the same thing
> as Vladimir, capturing for ATI AIWs, I think
Vladimir,
As Peter pointed out to me you were speaking of a video card
with built-in capture. This _does_ require, as you stated a
way to get the video, out of the video ram and into system ram,
my apologies for the misunderstanding.
My point should still hold. The DRM should allow you to ma
On Mon, Oct 08, 2001 at 03:54:14PM -0700, Sottek, Matthew J wrote:
> The drm _does_ allow the client to mmap the video ram.
I am not completely sure about this, but as I'm also working on the same thing
as Vladimir, capturing for ATI AIWs, I think he is talking about mmap-ing DMA
buffers, not the
On Mon, 8 Oct 2001, Sottek, Matthew J wrote:
> Vladimir,
> The drm _does_ allow the client to mmap the video ram. Of course
I don't want video ram. I want to transfer data from video ram into plain
memory and then access it there - pci reads are way slow.
> there are security reasons to limi
On Mon, Oct 08, 2001 at 03:54:14PM -0700, Sottek, Matthew J wrote:
> > Basically I want to DMA a chunk of video ram into plain RAM. This
> >is useful for: video capture, VBI/closed captioning, taking screen
> >snapshots.
>
> I think you are going about this the wrong way. Video capture does
> no
Vladimir,
The drm _does_ allow the client to mmap the video ram. Of course
there are security reasons to limit this behavior. The X server
handles the memory management and then sets up drm maps which are
areas of video memory that can be mapped by a drm client.
Take a look at the xc/lib/XvMC/h
38 matches
Mail list logo
