This patch supports i2c interface of si470x. The i2c specific part
exists in radio-si470x-i2c.c file and the common part uses
radio-si470x-common.c file. The '#if defined' is inserted inevitably
because of parts used only si470x usb in the common file.
The current driver version doesn't support th
The si470x_disconnect_check is function to check disconnect state of
radio in common file. The function is implemented in each interface
file.
Signed-off-by: Joonyoung Shim
---
.../media/radio/si470x/radio-si470x-common.c | 40 +--
.../drivers/media/radio/si470x/radio-si4
This patch is for using dev_* macro instead of printk.
Signed-off-by: Joonyoung Shim
---
.../media/radio/si470x/radio-si470x-common.c | 50 +-
.../drivers/media/radio/si470x/radio-si470x-usb.c | 58 +---
2 files changed, 52 insertions(+), 56 deletions(-
Hi, all
I send the radio-si470x patches worked on http://linuxtv.org/hg/v4l-dvb.
The patches is updated to version 2.
I have a board with Silicon Labs si4709 chip using the i2c interface,
but the radio-si470x is only support usb interface currently. I posted
about separating usb and i2c interface
On Sat, Jul 11, 2009 at 01:49:46, Mauro Carvalho Chehab wrote:
> Em Mon, 6 Jul 2009 20:24:44 +0200
> Hans Verkuil escreveu:
>
> > Hi Mauro,
> >
> > Please pull from http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-vpfe-cap
for the following:
> >
> > - tvp514x: Migration to sub-device framework
> > -
Hi, Alexey.
>> diff --git a/linux/drivers/media/radio/si470x/radio-si470x-common.c
>> b/linux/drivers/media/radio/si470x/radio-si470x-common.c
>> index d2dc1ff..77f79e7 100644
>> --- a/linux/drivers/media/radio/si470x/radio-si470x-common.c
>> +++ b/linux/drivers/media/radio/si470x/radio-si470x-c
There is a bug in DvbStream::gotoX in Kaffeine 0.8.8,
which is fixed by the attached patch.
Look for example at what happens when azimuth = 15.951. The
motor should be driven to 16.0 degrees, but when 15.951 is
rounded up with
if (USALS>0.5) ++rd;
the carries into the upper nibble of CMD2 and the
Hans,
>> #define VIDIOC_S_EXT_CTRLS _IOWR('V', 72, struct v4l2_ext_controls)
>> #define VIDIOC_TRY_EXT_CTRLS _IOWR('V', 73, struct
>v4l2_ext_controls)
>>
>> Currently they are implemented using proprietary ioctls.
>
>Do you mean proprietary ioctls or proprietary controls? Here you talk about
>
On Monday 13 July 2009 20:21:20 Karicheri, Muralidharan wrote:
> Hi,
>
> I need to implement some controls for my driver and would like to
> understand the control ioctl framework available today. I am not very
> sure how the control ioctls are to be implemented and it is not well
> defined in the
Hei Mauro,
Please pull from http://linuxtv.org/hg/~anttip/af9013/
for the following:
af9013: auto-detect parameters in case of garbage given by app
I marked it as Priority: high ; it is rather small change and fixes
compatibility issue with MPlayer.
regards
Antti
--
http://palosaari.fi/
--
On 07/11/2009 09:02 AM, Nils Kassube wrote:
Antti Palosaari wrote:
I need your signed off by tag in order to forward this mainline.
Patch is correct and I tested it also.
OK, here it is again with the requested line. And thanks for taking care
of the issue.
Signed-off-by: Nils Kassube
Patch
Hello all
On 7/13/09, Joonyoung Shim wrote:
> This patch supports i2c interface of si470x. The i2c specific part
> exists in radio-si470x-i2c.c file and the common part uses
> radio-si470x-common.c file. The '#if defined' is inserted inevitably
> because of parts used only si470x usb in the commo
Hi Hermann,
On Monday 13 of July 2009 at 03:06:41, hermann pitton wrote:
> Hi Oldřich,
>
> this needs to be looked up during day time, preferably with the register
> settings for all involved saa713x devices, which I do not have ...
You can respond the next day, no need to stay awake :-)
> Am So
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:Mon Jul 13 19:00:22 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 12238:a57e555da12a
gcc version: gcc
Hi,
I need to implement some controls for my driver and would like to understand
the control ioctl framework available today. I am not very sure how the control
ioctls are to be implemented and it is not well defined in the specification. I
have provided below my understanding of the below set
Hi,
I need to implement some controls for my driver and would like to understand
the control ioctl framework available today. I am not very sure how the control
ioctls are to be implemented and it is not well defined in the specification. I
have provided below my understanding of the below set
On 13 July 2009 03:50:05 Mark Zimmerman wrote:
> Greetings:
>
> Is the TBS 8920 card supported? It is not present in the supported
> cards list in the wiki, but I saw it mentioned in an article about
> S2API. I just wanted to check before I bought one.
>
> Thanks,
> -- Mark
> --
> To unsubscribe
On Fri, Jul 10, 2009 at 04:32:07PM -0500, Karicheri, Muralidharan wrote:
> Hello Russell,
>
> This patch is part of the vpfe capture driver (V4L) that adds platform
> code for the driver on DM355 which is an ARM based SoC. I have attached
> the original pull request to this email. Please review th
Am Montag, 13. Juli 2009 schrieben Sie:
> Am Montag 13 Juli 2009 14:13:50 schrieben Sie:
> > On Sonntag, 12. Juli 2009, Boris Cuber wrote:
> > > Hi kernel folks!
> > >
> > > Problem:
> > > Since kernel-2.6.31-rc* my dvb-s adapter (Technisat SkyStar2 DVB card)
> > > refuses to work (worked fine in e
Hi Hermann,
On Sun, 12 Jul 2009 23:33:06 +0200, hermann pitton
wrote:
[snip]
Hm, if I get it right, without using windows previously the XCeive at
0x61 is not found and then it is tried in vain to use the qt1010 at
0x62.
Also, after using windows gpio20 seems to be high.
Maybe that is the
On Mon, Jul 13, 2009 at 4:08 PM, Devin
Heitmueller wrote:
> On Mon, Jul 13, 2009 at 9:51 AM, Markus Rechberger
> wrote:
>> On Mon, Jul 13, 2009 at 5:23 AM, Devin
>> Heitmueller wrote:
>>> Hello Mauro,
>>>
>>> Please pull from
>>> http://kernellabs.com/hg/~dheitmueller/pinnacle_hybrid_2881 for the
On Mon, Jul 13, 2009 at 9:51 AM, Markus Rechberger wrote:
> On Mon, Jul 13, 2009 at 5:23 AM, Devin
> Heitmueller wrote:
>> Hello Mauro,
>>
>> Please pull from
>> http://kernellabs.com/hg/~dheitmueller/pinnacle_hybrid_2881 for the
>> following:
>>
>> em28xx: set GPIO properly for Pinnacle Hybrid Pro
Hey cyber.bogh,
besides the fact that you MAY be right in your zhinking about such usage of
drivers and kernel elements ...
This is not the right way to complain about users/developers not so deeply
into the materia than you.
If you know more about special things in the area you work in - fine.
On Mon, Jul 13, 2009 at 5:23 AM, Devin
Heitmueller wrote:
> Hello Mauro,
>
> Please pull from
> http://kernellabs.com/hg/~dheitmueller/pinnacle_hybrid_2881 for the
> following:
>
> em28xx: set GPIO properly for Pinnacle Hybrid Pro analog support
> em28xx: make support work for the Pinnacle Hybrid P
Am Montag 13 Juli 2009 14:13:50 schrieben Sie:
> On Sonntag, 12. Juli 2009, Boris Cuber wrote:
> > Hi kernel folks!
> >
> > Problem:
> > Since kernel-2.6.31-rc* my dvb-s adapter (Technisat SkyStar2 DVB card)
> > refuses to work (worked fine in every kernel up to 2.6.30.1).
> > So anything pulled in
On Sonntag, 12. Juli 2009, Boris Cuber wrote:
> Hi kernel folks!
>
> Problem:
> Since kernel-2.6.31-rc* my dvb-s adapter (Technisat SkyStar2 DVB card)
> refuses to work (worked fine in every kernel up to 2.6.30.1).
> So anything pulled into the new kernel seems to have broken
> something (at least
2009/7/13 Andy Walls :
> On Mon, 2009-07-13 at 20:17 +0900, Dongsoo, Nathaniel Kim wrote:
>
>
>> Well arranged thanks to you. BTW, can you tell me about
>> "s_crystal_freq" in detail? I can see that ivtv and saa7115 are using
>> that but can't figure out what is exactly for. At the earlier mail, I
On Mon, 2009-07-13 at 20:17 +0900, Dongsoo, Nathaniel Kim wrote:
> Well arranged thanks to you. BTW, can you tell me about
> "s_crystal_freq" in detail? I can see that ivtv and saa7115 are using
> that but can't figure out what is exactly for. At the earlier mail, I
> considered that as a functio
This patch supports i2c interface of si470x. The i2c specific part
exists in radio-si470x-i2c.c file and the common part uses
radio-si470x-common.c file. The '#if defined' is inserted inevitably
because of parts used only si470x usb in the common file.
The current driver version doesn't support th
Hi, all
I send the radio-si470x patches worked on http://linuxtv.org/hg/v4l-dvb.
I have a board with Silicon Labs si4709 chip using the i2c interface,
but the radio-si470x is only support usb interface currently. I posted
about separating usb and i2c interface in radio-si470x the past.
http://www
2009/7/13 Hans Verkuil :
> On Monday 13 July 2009 10:19:57 Dongsoo, Nathaniel Kim wrote:
>> 2009/7/12 Hans Verkuil :
>> > On Saturday 11 July 2009 13:02:33 Dongsoo, Nathaniel Kim wrote:
>> >> Hi,
>> >>
>> >> The thing is - Is it possible to make the subdev device not to be
>> >> turned on in regist
On Monday 13 July 2009 10:19:57 Dongsoo, Nathaniel Kim wrote:
> 2009/7/12 Hans Verkuil :
> > On Saturday 11 July 2009 13:02:33 Dongsoo, Nathaniel Kim wrote:
> >> Hi,
> >>
> >> The thing is - Is it possible to make the subdev device not to be
> >> turned on in registering process using any of v4l2_i
2009/7/12 Hans Verkuil :
> On Saturday 11 July 2009 13:02:33 Dongsoo, Nathaniel Kim wrote:
>> Hi,
>>
>> The thing is - Is it possible to make the subdev device not to be
>> turned on in registering process using any of v4l2_i2c_new_subdev*** ?
>> You can say that I can ignore the i2c errors in boot
33 matches
Mail list logo
