From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: "need4weed@gmail.com" <need4weed@gmail.com>,
Elmar Kleijn <elmar_kleijn@hotmail.com>,
video4linux-list@redhat.com, spca50x-devs@lists.sourceforge.net
Subject: v4l1 compat wrapper version 0.2
Date: Fri, 06 Jun 2008 13:17:37 +0200 [thread overview]
Message-ID: <48491CD1.700@hhs.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hi All,
Changes:
* When mmap gets passed an fd of -1 (anonymous map) don't look for it in our
list of managed fds, as we use -1 to mark unused entries (fixes ekiga
crashing). Also check for an fd of -1 in the other calls we intercept.
* In close() start with removing the fd from our list of managed fds, this must
be done first, because as soon as we've done the actual close syscall, the
fd maybe returned by an open in another thread and we don't want to intercept
calls to this new fd.
* Make unknown v4l1 palette types a normal level log messages instead of an
error.
* When an applicaiton changes the width / height through the CMCAPTURE ioctl
remember the new width and height.
* If the devices initial v4l2 pixformat has no corresponding v4l1 palette, try
setting a format which does (and which we emulate when necessary) so that
applicactions which just query the current format (GPICT) and then take
whatever they get will work (partially fixes camorama)
* Implement our own SWIN instead of using kernel compat layer, for more
flexibility and better error checking
If you want to test please use this version, the previous version had a nasty
bug in the mmap wrapping causing all kinda problems (brown paper bag bug).
New version attached.
Regards,
Hans
[-- Attachment #2: v4l1-compat-0.2.tar.gz --]
[-- Type: application/x-gzip, Size: 30663 bytes --]
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
reply other threads:[~2008-06-06 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48491CD1.700@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=elmar_kleijn@hotmail.com \
--cc=need4weed@gmail.com \
--cc=spca50x-devs@lists.sourceforge.net \
--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