From: Thomas Kaiser <linux-dvb@kaiser-linux.li>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>
Subject: Re: [GIT PATCHES FOR 2.6.37] Remove V4L1 support from the pwc driver
Date: Mon, 13 Sep 2010 18:34:31 +0200 [thread overview]
Message-ID: <4C8E5297.5000208@kaiser-linux.li> (raw)
In-Reply-To: <1284384634.2031.71.camel@morgan.silverblock.net>
On 09/13/2010 03:30 PM, Andy Walls wrote:
> On Mon, 2010-09-13 at 08:27 -0300, Mauro Carvalho Chehab wrote:
>> Em 12-09-2010 18:28, Andy Walls escreveu:
>>> On Sun, 2010-09-12 at 17:12 -0400, Andy Walls wrote:
>>>> On Sun, 2010-09-12 at 22:26 +0200, Hans Verkuil wrote:
>>>>
>>>>> And other news on the V4L1 front:
>>>>
>>>>> I'm waiting for test results on the cpia2 driver. If it works, then the V4L1
>>>>> support can be removed from that driver as well.
>>>>
>>>> FYI, that will break this 2005 vintage piece of V4L1 software people may
>>>> still be using for the QX5 microscope:
>>>
>>> Sorry, that is of course, if there is no V4L1 compat layer still in
>>> place.
>>>
>>> BTW, qx5view uses a private ioctl() to change the lights on a QX5 and
>>> not the V4L2 control.
>>
>> The better would be to port qx5view to use libv4l and implement the new
>> illuminator ctrl on the driver and on the userspase app. Do you have
>> hardware for testing this?
>
> No. I did check Amazon.com and eBay and saw a QX5 for about US$75 after
> shipping costs:
>
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=380262406989&rvr_id=139147359954&crlp=1_263602_263622&UA=L*F%3F&GUID=0b3b537412b0a0e203e63006ff9becb0&itemid=380262406989&ff4=263602_263622
>
> I'm not sure if I want to buy one at that price, since I already have a
> QX3.
>
> Regards,
> Andy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Andy, Mauro
I own a USB Microscope which looks quite the same as the one in your
link, but I don't know if it is similar to the QX3 or QX5.
It is called "Traveler USB-Mikroskop" and model number is "SU 1071".
One of this two:
http://www.traveler-service.de/cms/index.php?id=traveler-optische-geraete-de
USB ID: 1871:01b0 Aveo Technology Corp.
It is not working in Ubuntu 10.04, kernel AMD64 2.6.32-24-generic.
If it is a QX5, I can help testing.
Regards,
Thomas
next prev parent reply other threads:[~2010-09-13 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 20:26 [GIT PATCHES FOR 2.6.37] Remove V4L1 support from the pwc driver Hans Verkuil
2010-09-12 21:12 ` Andy Walls
2010-09-12 21:28 ` Andy Walls
2010-09-12 21:34 ` Andy Walls
2010-09-13 11:27 ` Mauro Carvalho Chehab
2010-09-13 13:30 ` Andy Walls
2010-09-13 16:34 ` Thomas Kaiser [this message]
2010-09-13 7:02 ` Hans Verkuil
2010-09-13 12:56 ` Andy Walls
2010-09-13 13:03 ` Hans Verkuil
2010-09-15 17:51 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2010-09-13 17:07 Andy Walls
2010-09-13 17:40 Andy Walls
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=4C8E5297.5000208@kaiser-linux.li \
--to=linux-dvb@kaiser-linux.li \
--cc=awalls@md.metrocast.net \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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