Hi Dmitry :)
Am Donnerstag, den 14.05.2009, 10:17 +1000 schrieb Dmitri Belimov:
> Hi
>
> > Hi Dmitry,
> >
> > Am Mittwoch, den 13.05.2009, 07:37 +1000 schrieb Dmitri Belimov:
> > > Hi hermann
> > >
> > > > Am Sonntag, den 10.05.2009, 08:52 +1000 schrieb Dmitri Belimov:
> > > > > Hi All.
> > > >
Hi Dmitry,
Am Mittwoch, den 13.05.2009, 07:37 +1000 schrieb Dmitri Belimov:
> Hi hermann
>
> > Am Sonntag, den 10.05.2009, 08:52 +1000 schrieb Dmitri Belimov:
> > > Hi All.
> > >
> > > > [snip]
> > > > > >
> > > > > > Channel designations I dug out of ivtv-tune:
> > > > > >
> > > > > > S38 439
On Wed, May 13, 2009 at 6:26 PM, Vanessa Ezekowitz
> Devin, does this license/bundle arrangement also cover the firmware for
> xc3028-based devices?
Unfortunately, it does not. Once I get the xc5000 stuff in though, I
am planning on approaching them about getting firmware licensing under
the same
On Wed 13 May 2009 2:24:53 pm Devin wrote:
> On Wed, May 13, 2009 at 3:04 PM, Timothy D. Lenz wrote:
> > So when this goes main, next time we update from v4l we need the new
> > firmware right?
>
> Yes.
>
> Now that we have the licensing straightened out, I'll also be working
> on getting it bundl
Hi,
it seems there is a bug in av7110_vbi_write() (av7110_v4l.c). If an user mode
application
tries to write more bytes than the size of the structure v4l2_slices_vbi_data,
copy_from_user() will overwrite parts of the kernel stack.
Regards,
Hartmut
--
To unsubscribe from this list: send the line
Now that the ir-kbd-i2c driver has been converted to a new-style i2c
driver, we can instantiate the ir_video I2C device by default. The
pvr2_disable_ir_video is kept to disable the IR receiver, either
because the user doesn't use it, or for debugging purpose.
Signed-off-by: Jean Delvare
Cc: Mike
Probe I2C addresses 0x71 and 0x6b for IR receiver devices (for the
PVR150 and Adaptec cards, respectively.)
Signed-off-by: Jean Delvare
Cc: Hans Verkuil
---
linux/drivers/media/video/ivtv/ivtv-i2c.c|7 ++-
linux/drivers/media/video/pvrusb2/pvrusb2-i2c-core.c |2 +-
2 fil
Now that we instantiate I2C IR devices explicitly, we can skip probing
altogether on boards where the I2C IR device address is known. The
AVerMedia Cardbus E506R is one of these boards.
Signed-off-by: Jean Delvare
Tested-by: Oldrich Jedlicka
---
linux/drivers/media/video/saa7134/saa7134-input.c
Now that we instantiate I2C IR devices explicitly, we can skip probing
altogether on boards where the I2C IR device address is known. The MSI
t...@nywhere Plus is one of these boards.
Signed-off-by: Jean Delvare
---
linux/drivers/media/video/saa7134/saa7134-input.c | 28 +++--
The code in ir_probe makes the dangerous assumption that all IR
receivers are supported by the driver. The new i2c model makes it
possible for bridge drivers to instantiate IR devices before they are
supported, therefore the ir-kbd-i2c drivers must be made more robust
to not spam the logs or even c
For specific boards, pass initialization data to ir-kbd-i2c instead
of modifying the settings after the device is initialized. This is
more efficient and easier to read.
Signed-off-by: Jean Delvare
---
linux/drivers/media/video/cx231xx/cx231xx-cards.c |3
linux/drivers/media/video/cx231xx/c
Let card drivers probe for IR receiver devices and instantiate them if
found. Ultimately it would be better if we could stop probing
completely, but I suspect this won't be possible for all card types.
There's certainly room for cleanups. For example, some drivers are
sharing I2C adapter IDs, so t
In the standard device driver binding model, the name field of
struct i2c_client is used to match devices to their drivers, so we
must stop using it for internal purposes. Define a separate field
in struct IR_i2c as a replacement, and use it.
Signed-off-by: Jean Delvare
---
linux/drivers/media/v
Hi all,
Here comes an update of my conversion of ir-kbd-i2c to the new i2c
binding model. I've split it into 8 pieces for easier review. Firstly
there is 1 preliminary patch:
01-ir-kbd-i2c-dont-abuse-client-name.patch
Then 3 patches doing the actual conversion:
02-ir-kbd-i2c-convert-to-new-styl
On Wed, May 13, 2009 at 3:04 PM, Timothy D. Lenz wrote:
> So when this goes main, next time we update from v4l we need the new firmware
> right?
Yes.
Now that we have the licensing straightened out, I'll also be working
on getting it bundled into the distros so that users don't have to
download
- Original Message -
From: "Devin Heitmueller"
To: "Britney Fransen"
Cc: "Devin Heitmueller" ; "Linux Media Mailing
List"
Sent: Tuesday, May 12, 2009 1:56 PM
Subject: Re: XC5000 improvements: call for testers!
> On Tue, May 12, 2009 at 4:50 PM, Britney Fransen
> wrote:
> > I finall
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:Wed May 13 19:00:03 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 11758:8d37e8505664
gcc version: gcc
Hello,
On Wed, May 13, 2009 at 12:39 AM, wrote:
> From: Alessio Igor Bogani
>
> radio-mr800.c uses struct mutex, so while seems to be
> pulled in indirectly by one of the headers it already includes, the right
> thing is to include it directly.
>
> Signed-off-by: Alessio Igor Bogani
> Cc: Mau
On Wed, May 13, 2009 at 12:29 PM, Oliver Endriss wrote:
> What are you talking about?
>
> This patch does not have any impact on the reception path (from tuner to
> application). It just discards bogus data which might crash the av7110
> or cause chirping sound during replay.
>
>> Like I said abov
Devin Heitmueller wrote:
> On Wed, May 13, 2009 at 2:52 AM, Trent Piepho wrote:
> > On Wed, 13 May 2009, Oliver Endriss wrote:
> >> 02/05: dvb-ttpci: Check transport error indicator flag
> >> http://endr...@linuxtv.org/hg/~endriss/v4l-dvb?cmd=changeset;node=8a742338523d
> >
> > Are you sure this i
Trent Piepho wrote:
> On Wed, 13 May 2009, Oliver Endriss wrote:
> > 02/05: dvb-ttpci: Check transport error indicator flag
> > http://endr...@linuxtv.org/hg/~endriss/v4l-dvb?cmd=changeset;node=8a742338523d
>
> Are you sure this is a good idea? The cx88 driver doesn't do this.
Of course, for the
On Wed, May 13, 2009 at 2:13 AM, kenny wang wrote:
>
> Hi, Devin
>
> I found another problem for my WinTV-HVR-950Q, but I am not sure if it's
> caused by the device driver: my tvtime sometimes (not often) lost all
> channels and shows a blue window. Switching channel doesn't take the channel
> bac
On Wed, May 13, 2009 at 2:52 AM, Trent Piepho wrote:
> On Wed, 13 May 2009, Oliver Endriss wrote:
>> 02/05: dvb-ttpci: Check transport error indicator flag
>> http://endr...@linuxtv.org/hg/~endriss/v4l-dvb?cmd=changeset;node=8a742338523d
>
> Are you sure this is a good idea? The cx88 driver doesn
On 05/13/2009 03:27 AM, Peter Forstmeier wrote:
Hi,
i tried to build v4l and did tho following:
pe...@linux-d9lb:~> hg clone http://linuxtv.org/hg/v4l-dvb
destination directory: v4l-dvb
requesting all changes
adding changesets
adding manifests
adding file changes
added 11759 changesets with 297
Hi
> >> 1. AGC TOP of RF part - I think need support for MK3
> >> 2. Changing to 441MHz is not critical. We can write some
> >> information about this case to Wiki or docs.
> >
> > for 2.: Discussed to the end if you stay at 441MHz. If you still
> > want to have it in, just send a patch and no
Em Tue, 12 May 2009 01:36:17 -0500 (CDT)
Mike Isely escreveu:
> On Mon, 11 May 2009, Mauro Carvalho Chehab wrote:
>
> > Em Mon, 11 May 2009 22:09:26 -0300
> > Mauro Carvalho Chehab escreveu:
> >
> > > Em Sat, 9 May 2009 16:49:31 -0500 (CDT)
> > > Mike Isely escreveu:
> > >
> > > >
> > > > M
I have TT-C 1501 DVB card. it work fine under kernel 2.6.26 (32bit). but
when I use the same kernel but 64bit then
I got very bad receiving. picture and tone are not to identifing.
Is it a driver problem?
I use the latest v4l HG.
-Amir
--
To unsubscribe from this list: send the line "unsubscr
Hi,
i tried to build v4l and did tho following:
pe...@linux-d9lb:~> hg clone http://linuxtv.org/hg/v4l-dvb
destination directory: v4l-dvb
requesting all changes
adding changesets
adding manifes
28 matches
Mail list logo
