From: Gerd Knorr <kraxel@bytesex.org>
To: Mark McClelland <mark@alpha.dyndns.org>
Cc: video4linux-list@redhat.com, Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [V4L] [PATCH/RFC] videodev.[ch] redesign
Date: Mon, 11 Feb 2002 10:55:34 +0100 [thread overview]
Message-ID: <20020211105534.A4745@bytesex.org> (raw)
In-Reply-To: <20020209194602.A23061@bytesex.org> <3C65EFF4.2000906@alpha.dyndns.org> <20020210101130.A28225@bytesex.org> <3C666D98.70600@alpha.dyndns.org>
In-Reply-To: <3C666D98.70600@alpha.dyndns.org>
On Sun, Feb 10, 2002 at 04:54:48AM -0800, Mark McClelland wrote:
> OK, agreed on all points. Thanks for the clarification.
>
> BTW, is there any chance for vmalloc() and pals to be moved to
> videodev.c, or something higher-up?
What do you mean exactly? bttv's memory management code, which has
been copied to various places, and which is now broken in 2.5.x due
to virt_to_bus() being gone finally?
Some of this is work-in-progress. I'm talking to Dave to put some
helper functions to handle DMA to vmalloced memory blocks to some
sensible place within the kernel. If someone wants to have a look
(not final yet): http://bytesex.org/patches/15_pci-2.4.18-pre8.diff
Gerd
--
#define ENOCLUE 125 /* userland programmer induced race condition */
next prev parent reply other threads:[~2002-02-11 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 18:46 [PATCH/RFC] videodev.[ch] redesign Gerd Knorr
2002-02-09 20:53 ` Oliver Neukum
2002-02-09 20:53 ` Oliver Neukum
2002-02-09 20:44 ` Gerd Knorr
2002-02-10 0:32 ` Oliver Neukum
2002-02-10 8:34 ` Gerd Knorr
2002-02-10 2:03 ` [V4L] " Alan Cox
2002-02-10 8:59 ` Gerd Knorr
2002-02-11 21:10 ` [PATCH/RFC] videodev.[ch] redesign -- take #2 Gerd Knorr
2002-02-10 3:58 ` [V4L] [PATCH/RFC] videodev.[ch] redesign Mark McClelland
2002-02-10 9:11 ` Gerd Knorr
2002-02-10 12:54 ` Mark McClelland
2002-02-11 9:55 ` Gerd Knorr [this message]
2002-02-11 11:58 ` Mark McClelland
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=20020211105534.A4745@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@alpha.dyndns.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