On Thu, Jun 10, 2010 at 10:20 PM, Rohan Carly wrote:
> Hi, I had success with some TV tuner hardware that wasn't listed on the
> linuxtv.org V4L-DVB wiki. Could you please update it?
The Wiki is open to anyone's contributions. If you have found an
inaccuracy or some missing info, you should feel
Hi, I had success with some TV tuner hardware that wasn't listed on the
linuxtv.org V4L-DVB wiki. Could you please update it?
The relevant section is here:
http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#Compro
My device is a Compro DVD-T300 (purchased in Australia):
lime:~# lspci | grep
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Thu Jun 10 19:00:22 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14974:023a0048e6a8
git master:
Hi,
2010/6/10 Jiajun Zhu :
> Thanks for the discussion.
> Based on my testing, the image timestamps or ktime is the system uptime in
> nanosecond, is this correct?
> For my application, I need to synchronize the camera image with other data
> which are all timestamped by gettimeofday().
Like I ex
Hello,
I've got a Technotrend Budget 3200 installed in my Kubuntu Lucid (10.04)
machine. It worked fine out of the box. Because I want to watch a broadcast and
record another one at the same time I bought another DVB-Card. This time I
bought a Technisat Skystar HD2 because with the TT Budget I'
Hi Steven,
> This and your other two patches are in
> http://www.kernellabs.com/hg/~stoth/saa7164-dev
>
> They look good to me.
What is the proper process to see the patches accepted and integrated ? I
want to be aligned with the way of working before sending other
corrections or improvements.
T
On Thursday 10 June 2010 11:25:41 Paulo Assis wrote:
> PLEASE NO,
> The current use of ktime is much better, timestamps are perfectly in
> sync and will not suffer from time shifts if the clock value changes.
>
> PLEASE just leave it like it is now.
Agreed. The V4L2 spec should be modified.
--
PLEASE NO,
The current use of ktime is much better, timestamps are perfectly in
sync and will not suffer from time shifts if the clock value changes.
PLEASE just leave it like it is now.
Best Regards,
Paulo
2010/6/10 Jean-Francois Moine :
> Hi Mauro,
>
> The following changes since commit e411f2
2010/6/10 Jean-Francois Moine :
> On Thu, 10 Jun 2010 03:24:05 + (UTC)
> jiajun wrote:
>
>> I'm currently using the V4L-DVB driver to control a few logitech
>> webcams and playstation eye cameras on a Gubuntu system.
>>
>> Everything works just fine except one thing: the buffer timestamp
>> v
Hi Mauro,
The following changes since commit e411f2dda48c81c556c802d4430717950cf088fd:
Merge branch 'for-linus' of git://git.monstr.eu/linux-2.6-microblaze
(2010-06-09 08:52:03 -0700)
are available in the git repository at:
git://linuxtv.org/jfrancois/gspca.git for_2.6.35
Jean-François Mo
On Thu, 10 Jun 2010 03:24:05 + (UTC)
jiajun wrote:
> I'm currently using the V4L-DVB driver to control a few logitech
> webcams and playstation eye cameras on a Gubuntu system.
>
> Everything works just fine except one thing: the buffer timestamp
> value seems wrong.
[snip]
> this s
Hi
I have regression with our TV cards + I2C r/c and new IR subsystem.
modules crashed
[ 148.461819] Linux video capture interface: v2.00
[ 148.462768] IR NEC protocol handler initialized
[ 148.482886] saa7130/34: v4l2 driver version 0.2.16 loaded
[ 148.482925] saa7134 :04:01.0: PCI INT A
12 matches
Mail list logo
