Messages in this thread | | | From | Paul Sargent <> | Subject | RE: Address spaces on a i386 - Getting Confused | Date | Tue, 30 Mar 1999 14:22:19 +0100 |
| |
Well, I wasn't that bothered about doing HW access to user space, but you picqued my interest :-) This is all 3D texture mapper based.
If I was to go this route I would want to have a buffer that a user process could write to, and then have that DMA'd to the HW. It's just that things like texture maps can get pretty big, and I can forsee instances where the User->Kernel space copy will take a appreciable amount of time to copy the data across.
I have to admit I was thinking along the lines of Kernel Space allocation and then a user space mmap(). Reading your mails it looks like this could work, I'll have to read up a bit more (translation: dive into the source).
Thanks
Paul
> -----Original Message----- > From: David Miller [SMTP:davem@twiddle.net] > Sent: Tuesday, March 30, 1999 1:18 PM > To: Paul.Sargent@3dlabs.com > Cc: linux-kernel@vger.rutgers.edu > Subject: Re: Address spaces on a i386 - Getting Confused > > Since you're so adament about DMA'ing directly into user space, you've > piqued my interest, what does this card do and what is the > application? Video capture or 3d texture mapping? > > Later, > David S. Miller > davem@redhat.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |