Any news about this card? Some time ago i read that it was on
development the pinnacle DTV bridge, but i can't find any information
now about this.
lspci -vvnnnx
03:07.0 Multimedia controller [0480]: Pinnacle Systems Inc. Royal TS
Function 1 [11bd:0040]
Subsystem: Pinnacle Systems In
Hi Vladimir,
Am Samstag, den 20.03.2010, 17:58 +0300 schrieb Vladimir Ermakov:
> Hi Hermann.
>
> 1. It's my mistake. Fixed.
> 2. Dead code. Removed.
thanks for looking at it.
We likely need your SOB line again, since it is a new patch.
Here is my
Reviewed-by: hermann pitton
Cheers,
Hermann
Hi,
On 03/20/2010 10:21 AM, Hans Verkuil wrote:
Hi all!
The second phase that needs to be done to remove the v4l1 support from the
kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
I do not know how complete the libv4l1 code is right now. I would like to
know in parti
Hi,
On 03/20/2010 10:53 PM, Hans Verkuil wrote:
On Saturday 20 March 2010 09:58:49 Hans Verkuil wrote:
Kconfig mistakes:
I found four errors in drivers/media/video/Kconfig: the saa7191, meye, mxb
and cpia2 drivers are all marked as V4L1 only, while all support V4L2!
The cpia2 driver supports
Hi,
On 03/20/2010 09:58 AM, Hans Verkuil wrote:
Hi all,
Well, I certainly fired everyone up with my RFC. Based on the replies I got I
do think the time is right to start the removal process.
Phase 1 would be to convert the remaining V4L1 drivers.
To see what needs to be done I decided to anal
On Saturday 20 March 2010 15:12:53 Wolfram Sang wrote:
> Fix I2C-drivers which missed setting clientdata to NULL before freeing the
> structure it points to. Also fix drivers which do this _after_ the structure
> was freed already.
I feel I am missing something here. Why does clientdata have to be
On Saturday 20 March 2010 09:58:49 Hans Verkuil wrote:
>
> Kconfig mistakes:
>
> I found four errors in drivers/media/video/Kconfig: the saa7191, meye, mxb
> and cpia2 drivers are all marked as V4L1 only, while all support V4L2!
> The cpia2 driver supports both v4l1 and v4l2. I can test this driv
On Saturday 20 March 2010 17:14:12 Devin Heitmueller wrote:
> On Sat, Mar 20, 2010 at 10:14 AM, Hans Verkuil wrote:
> > Of course, the best solution is to convert the V4L1 apps to using V4L2.
>
> On that topic, if I wanted to ensure that an application was not using
> any V4L1 functionality, is t
On Saturday 20 March 2010 17:03:01 e9hack wrote:
> Am 20.3.2010 15:20, schrieb Hans Verkuil:
> > Hartmut, is the problem with unloading the module something that my patch
> > caused? Or was that there as well before changeset 14351:2eda2bcc8d6f?
> > Are there any kernel messages indicating why it w
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:Sat Mar 20 19:00:24 CET 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14494:929298149eba
git master:
On Sat, Mar 20, 2010 at 4:58 AM, Hans Verkuil wrote:
> Hans de Goede added support for the quickcam_messenger to gspca, so that
> driver
> is scheduled for removal. Devin has hardware to test the vicam driver. David
> Ellingsworth has hardware to test the ibmcam driver. It would be great if
> Dev
On Sat, 2010-03-20 at 09:58 +0100, Hans Verkuil wrote:
> Hi all,
>
>
> - ov511
> - ovcamchip
> - w9968cf
> - stv680
>
> Conclusion:
>
> These drivers have no hardware to test with: bw-qcam, c-qcam, arv, w9966.
> However, all four should be easy to convert to v4l2, even without hardware.
> Vol
Hello,
Please PULL from
http://kernellabs.com/hg/~dheitmueller/v4l-dvb-em286x-tvp5150 for the
following:
em28xx: add em286x/tvp5150 reference design
Thanks,
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe linux
Dear mailinglist/Tevii,
i have received a new tevii s660 yesterday.
I have tried to use the device with scan but then my system freezes/slows
down and i don't get any channels. Also when i create a channel list with
my nova 2 hd and check if that works with vdr, then i removed the drivers
from the
On Sat, Mar 20, 2010 at 10:14 AM, Hans Verkuil wrote:
> Of course, the best solution is to convert the V4L1 apps to using V4L2.
On that topic, if I wanted to ensure that an application was not using
any V4L1 functionality, is there any easy way to do that? For
example, can I just remove the #inc
Am 20.3.2010 15:20, schrieb Hans Verkuil:
> Hartmut, is the problem with unloading the module something that my patch
> caused? Or was that there as well before changeset 14351:2eda2bcc8d6f?
> Are there any kernel messages indicating why it won't unload?
Changset 14351:2eda2bcc8d6f causes a kernel
Hans Verkuil wrote:
> On Saturday 20 March 2010 15:07:08 Oliver Endriss wrote:
> > e9hack wrote:
> > > Am 13.3.2010 17:27, schrieb Hans Verkuil:
> > > > If there are no further comments, then I'll post a pull request in a
> > > > few days.
> > > >
> > > > Tested with the mxb board. It would be ni
Hi Hermann.
1. It's my mistake. Fixed.
2. Dead code. Removed.
# HG changeset patch
# User Vladimir Ermakov
# Date 1269096094 -10800
# Node ID a91db2cf4f5774866c8c5bf906d9ac4faff9173d
# Parent 929298149eba4b6d0696124b9880113c25cd0788
saa7134: fix GPIO HW-404M7
diff -r 929298149eba -r a91db2cf4f
On Saturday 20 March 2010 15:07:08 Oliver Endriss wrote:
> e9hack wrote:
> > Am 13.3.2010 17:27, schrieb Hans Verkuil:
> > > If there are no further comments, then I'll post a pull request in a few
> > > days.
> > >
> > > Tested with the mxb board. It would be nice if you can verify this with
>
Fix I2C-drivers which missed setting clientdata to NULL before freeing the
structure it points to. Also fix drivers which do this _after_ the structure
was freed already.
Signed-off-by: Wolfram Sang
Cc: Mauro Carvalho Chehab
---
Found using coccinelle, then reviewed. Full patchset is available
Fix I2C-drivers which missed setting clientdata to NULL before freeing the
structure it points to. Also fix drivers which do this _after_ the structure
was freed already.
Signed-off-by: Wolfram Sang
Cc: Mauro Carvalho Chehab
---
Found using coccinelle, then reviewed. Full patchset is available
On Saturday 20 March 2010 14:51:44 Chicken Shack wrote:
> Am Samstag, den 20.03.2010, 13:37 +0100 schrieb Hans Verkuil:
> > On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> > > Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > > > Hi all!
> > > >
> > > > The second phase t
Fix I2C-drivers which missed setting clientdata to NULL before freeing the
structure it points to. Also fix drivers which do this _after_ the structure
was freed already.
Signed-off-by: Wolfram Sang
Cc: Mauro Carvalho Chehab
---
Found using coccinelle, then reviewed. Full patchset is available
e9hack wrote:
> Am 13.3.2010 17:27, schrieb Hans Verkuil:
> > If there are no further comments, then I'll post a pull request in a few
> > days.
> >
> > Tested with the mxb board. It would be nice if you can verify this with the
> > av7110.
>
> Hi hans,
>
> it works with my TT-C2300 perfectly.
Am Samstag, den 20.03.2010, 13:37 +0100 schrieb Hans Verkuil:
> On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> > Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > > Hi all!
> > >
> > > The second phase that needs to be done to remove the v4l1 support from the
> > > kerne
On Saturday 20 March 2010 13:17:15 Chicken Shack wrote:
> Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> > Hi all!
> >
> > The second phase that needs to be done to remove the v4l1 support from the
> > kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
> >
Am Samstag, den 20.03.2010, 10:21 +0100 schrieb Hans Verkuil:
> Hi all!
>
> The second phase that needs to be done to remove the v4l1 support from the
> kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
>
> I do not know how complete the libv4l1 code is right now. I woul
Hi all!
The second phase that needs to be done to remove the v4l1 support from the
kernel is that libv4l1 should replace the v4l1-compat code from the kernel.
I do not know how complete the libv4l1 code is right now. I would like to
know in particular whether the VIDIOCGMBUF/mmap behavior can be
Hi all,
Well, I certainly fired everyone up with my RFC. Based on the replies I got I
do think the time is right to start the removal process.
Phase 1 would be to convert the remaining V4L1 drivers.
To see what needs to be done I decided to analyse the remaining V4L1 drivers:
- usbvideo (really
29 matches
Mail list logo
