From: Gerd Hoffmann <kraxel@novell.com>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: [patch] Fix bttv and friends on 64bit machines with lots of memory.
Date: Wed, 10 Jan 2007 09:58:12 +0100 [thread overview]
Message-ID: <45A4AAA4.4040606@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
Hi,
We have a DMA32 zone now, lets use it to make sure the card
can reach the memory we have allocated for the video frame
buffers.
please apply,
Gerd
[-- Attachment #2: v4l-dma32 --]
[-- Type: text/plain, Size: 870 bytes --]
Fix bttv and friends on 64bit machines with lots of memory.
We have a DMA32 zone now, lets use it to make sure the card
can reach the memory we have allocated for the video frame
buffers.
Signed-off-by: Gerds Hoffmann <kraxel@suse.de>
---
drivers/media/video/video-buf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.18/drivers/media/video/video-buf.c
===================================================================
--- linux-2.6.18.orig/drivers/media/video/video-buf.c
+++ linux-2.6.18/drivers/media/video/video-buf.c
@@ -1224,7 +1224,7 @@ videobuf_vm_nopage(struct vm_area_struct
vaddr,vma->vm_start,vma->vm_end);
if (vaddr > vma->vm_end)
return NOPAGE_SIGBUS;
- page = alloc_page(GFP_USER);
+ page = alloc_page(GFP_USER | __GFP_DMA32);
if (!page)
return NOPAGE_OOM;
clear_user_page(page_address(page), vaddr, page);
next reply other threads:[~2007-01-10 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 8:58 Gerd Hoffmann [this message]
2007-01-10 23:41 ` [patch] Fix bttv and friends on 64bit machines with lots of memory hermann pitton
2007-01-13 0:42 ` Mauro Carvalho Chehab
2007-01-13 1:37 ` hermann pitton
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=45A4AAA4.4040606@novell.com \
--to=kraxel@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=video4linux-list@redhat.com \
/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