Date: Fri, 11 Jul 2003 18:10:34 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Sean_Welch@alum.wofford.org Cc: welchsm@earthlink.net Subject: Re: BSD video capture emulation question Message-ID: <20030711181034.546fa93a.Alexander@Leidinger.net> In-Reply-To: <4339238.1057932704927.JavaMail.nobody@kermit.psp.pas.earthlink.net> References: <4339238.1057932704927.JavaMail.nobody@kermit.psp.pas.earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Jul 2003 07:11:42 -0500 (GMT)
Sean Welch <welchsm@earthlink.net> wrote:
> That's a lot of acronyms -- anyone care to explain to me what
> IOMMU, PIP, DTRT, and ISTM are? And what is a video sink?
PIP: Picture In Picture
DTRT: Do The Right Thing
ISTM: It Seems That Maybe (guessed!)
IOMMU: Input/Output Memory Management Unit (guessed!)
video sink: a "target" which consumes video data (opposed to: video
source, a "thing" which creates video data)
> John-Mark, could you clarify your concept of the kernel/
> userland split for a new video API? More particularly, what
> parts would be handled by the kernel and how do you envision
> the userland interacting with that part? Are we talking about
> creating a new device node (a la v4l) or a new way of interacting
> with existing device nodes?
As I understand the topic: he thinks about something like v4l/v4l2, but
better (and more generic which maybe can be named video4unix...).
The interaction with the device nodes is part of the userland.
Bye,
Alexander.
--
Reboot America.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030711181034.546fa93a.Alexander>