From: Martin Michlmayr <tbm@cyrius.com>
To: turja@mbnet.fi
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] SGI VINO driver 64-bit fix / V4L ioctl compatibility layer needs fixes
Date: Sat, 18 Mar 2006 01:59:41 +0000 [thread overview]
Message-ID: <20060318015941.GY18750@deprecation.cyrius.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0603171412170.11482@kekkonen.cs.hut.fi>
* turja@mbnet.fi <turja@mbnet.fi> [2006-03-17 14:19]:
> This patch should fix problems with VINO drivers when using a 64-bit
> kernel.
Did you test this?
It looks exactly like the patch you gave me for testing a few days ago
and that did not work...
> There are also other bugs which prevent V4L drivers from functioning
> correctly when using 32-bit userland with a 64-bit kernel as the ioctl
> compatibility layer (in drivers/media/video/compat_ioctl32.c) doesn't seem
> to handle VIDIOC_CROPCAP.
... or did I see this bug?
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-03-18 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 12:19 [PATCH] SGI VINO driver 64-bit fix / V4L ioctl compatibility layer needs fixes turja
2006-03-18 1:59 ` Martin Michlmayr [this message]
2006-03-18 8:58 ` Mikael Nousiainen
2006-03-18 8:58 ` Mikael Nousiainen
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=20060318015941.GY18750@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.org \
--cc=turja@mbnet.fi \
/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