Andy Walls wrote:
(Sorry, I've probably screwed up the threading on this)
> Dr. David Alan Gilbert wrote:
> > Hi,
> > Sparse pointed me at the following line in ivtv-fileops.c's
> > ivtv_v4l2_write:
> >
> > ivtv_write_vbi(itv, (const struct v4l2_sliced_vbi_data
> > *)user_
Good day,
I would like to volunteer, to bring into the kernel, the support for
Realtek DVB hardware.
I need a word from Realtek about driver that is a direct port of windows
driver.
I need to know that if it is released under GPL compatible licence,
which isn't clear today.
Also I would like t
Hi all,
I would side with Laurent on this. Judging by formats seems to be
enough for this driver and it has great, in my opinion, advantages of
a) not overcomplicating things for applications b) not adding new
pieces to the API...
--
Best regards,
Pawel Osciak
--
To unsubscribe from this list: se
Hi,
please see my comments below.
Also, if I could suggest something, please cut the code between
functions, not inside them, it'll make it easier for others to find
that location in the original code.
On Wed, Dec 1, 2010 at 00:56, Marek Szyprowski wrote:
> Hello,
>
> On Wednesday, December 01, 2
On Fri, Nov 26, 2010 at 6:24 AM, Arnd Bergmann wrote:
> [dri people: please have a look at the KMS discussion way below]
>
> On Thursday 25 November 2010 19:00:26 Marcus LORENTZON wrote:
>> > -Original Message-
>> > From: Arnd Bergmann [mailto:a...@arndb.de]
>> > Sent: den 25 november 2010
'n' may be bigger than MAX_INT*sizeof(int), if so checking of truncated
(int)(n/sizeof(int)) for LIRCBUF_SIZE overflows and then using nontruncated
'count'
doesn't make sense. This is not a security issue as too big 'n' is catched in
kmalloc() in memdup_user() call. However, it's better to preve
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 Dec 4 19:00:14 CET 2010
git master: 59365d136d205cc20fe666ca7f89b1c5001b0d5a
git media-master: gcc version: i6
The selection of 'helper' drivers for peripheral chips can be done
either automatically by the config entry for the controller chip in a
device (default if !EMBEDDED) or manually if the user knows exactly
which peripheral chips are used.
The config entries for these helper drivers are completely h
