Em Wed, 19 Aug 2009 10:32:07 -0500
"Karicheri, Muralidharan" escreveu:
> Mauro,
>
> Kevin has approved the architecture part of this patch. When can I expect
> these to be merged to linux-next?
>
> Thanks.
>
> Murali Karicheri
> Software Design Engineer
> Texas Instruments Inc.
> Germantown,
Am Dienstag, den 18.08.2009, 10:07 -0400 schrieb Devin Heitmueller:
> On Tue, Aug 18, 2009 at 7:00 AM, Johannes Stezenbach wrote:
> > I would be interested to know if someone _actually_ managed
> > to break their hardware by using buggy drivers.
>
> The short answer is *absolutely*.
>
> /me take
With the recent improvements we don't need to probe anymore, if we know
the i2c address of the receiver.
The address of the receiver for the remote with the gray buttons is not
confirmed anywhere, but it is very unlikely to see it on something else.
We want to have that information anyway.
BTW,
On Monday 17 August 2009, m-kariche...@ti.com wrote:
> static struct i2c_board_info dm355evm_i2c_info[] = {
> { I2C_BOARD_INFO("dm355evm_msp", 0x25),
> .platform_data = dm355evm_mmcsd_gpios,
> },
> + {
> + I2C_BOARD_INFO("PCA9543A", 0x73),
On Wed, 2009-08-19 at 16:36 -0700, Greg KH wrote:
> On Wed, Aug 19, 2009 at 11:38:03PM +0200, Rafael J. Wysocki wrote:
> > On Wednesday 19 August 2009, Stephen Rothwell wrote:
> > > Hi Rafael,
> >
> > Hi,
> >
> > > Today's linux-next build (x86_64 allmodconfig) produced these warnings:
> > >
> >
On Wed, Aug 19, 2009 at 11:38:03PM +0200, Rafael J. Wysocki wrote:
> On Wednesday 19 August 2009, Stephen Rothwell wrote:
> > Hi Rafael,
>
> Hi,
>
> > Today's linux-next build (x86_64 allmodconfig) produced these warnings:
> >
> > drivers/media/dvb/frontends/dib7000p.c: In function
> > ‘dib7000
On Thu, 20 Aug 2009 06:50:25 +0800
treblid wrote:
> On Wed, Aug 19, 2009 at 3:02 PM, Bob Hepple wrote:
> > 2.6.27 worked for me - exact same board (ignoring revisions - mine is
> > an older board, rev.1, I think)
> Mine is rev 1 too, I think.. :p
>
> > 2.6.28 and up failed for me in exactly this
On Wed, 2009-08-19 at 07:12 -0700, s...@cyberseth.com wrote:
> >> I'd really appreciate any help or guidance on this problem as i'm fully
> >> perplexed by it.
> >
> > Hey Seth,
> >
> > I ran the same tests on my cable system (channel 103) on 669Mhz and had no
> > issue, and my snr's reported as (0
The scan of the image packets of the sensor ov772x was broken when
the sensor ov965x was added.
[ Based on upstream c874f3aa, modified slightly for v2.6.30.5 ]
Signed-off-by: Jim Paris
Acked-by: Jean-Francois Moine
---
Hi,
Commit 84fbdf87ab8eaa4eaefb317a7eb437cd4d3d0ebf:
"V4L/DVB (11105): g
On Wed, Aug 19, 2009 at 5:35 PM, Stefano De Dionigi wrote:
> Hello Devin,
>
> I own a HVR-900 R2 and if you need help in testing i'd be more than
> happy to help.
> It's nice to see that for this device could there finally be light at
> the end of the tunnel.
Hello Dedioste,
Fortunately, in this
On Wednesday 19 August 2009, Stephen Rothwell wrote:
> Hi Rafael,
Hi,
> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
>
> drivers/media/dvb/frontends/dib7000p.c: In function
> ‘dib7000p_i2c_enumeration’:
> drivers/media/dvb/frontends/dib7000p.c:1315: warning: the frame
On Wed, Aug 19, 2009 at 3:42 PM, Devin
Heitmueller wrote:
> On Wed, Aug 19, 2009 at 7:01 AM, Miguel wrote:
>>
>> Hello,
>>
>> I am trying to set up the dvb-t device in my ubuntu 9.04.
>> As far as i can see , this device has tm6000 chipset but I don't get it
>> works. I have followed the guide of t
Hello,
I'm having some problems with my Terratec Cinergy C PCI DVB-C card. I
installed the mantis driver via DKMS, following the instructions at
http://www.linuxtv.org/wiki/index.php/Mantis_with_DKMS
The card is recognized, and it even works, but after a while
(typically 5 to 20 minutes) the car
fix: GPIO initialization for TBS 6920
fix: wrong I2C address for demod on TBS 6920
fix: wrong I2C bus number for demod on TBS 6920
fix: wrong "gen_ctrl_val" value for TS1 port on TBS 6920 (and some other cards)
add: module_param "lnb_pwr_ctrl" as option to choose between "type 0" and "type
1" of
Hello Jens,
I'm also looking into the CT-3650. I posted a few days back about the
support for this device for dvb-c. Are you trying to get dvb-c working
or dvb-t?
Can anyone else answer if dvb-c is indeed working with current linux?
Regards,
Bert
> Wed, Aug 19, 2009 at 8:01 PM, Jens Kjellerup
This patch removes an unneeded power management primitive.
Power management is automatically enabled as probe ends.
Signed-off-by: Oliver Neukum
Hi,
please accept this patch for the next merge window, as this
patch changes no functionality and removes a primitive that
won't be supported in the
On Wednesday 19 August 2009 19:44:24 Karicheri, Muralidharan wrote:
> Hans,
>
> You have done a great job in putting up a quick proposal. I was just trying
> to understand the intentions/rational behind your proposal to be on the same
> page. Thanks for the education. I think this will help othe
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 Aug 19 19:00:02 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 12458:3f7e382dfae5
gcc version: gcc
Hans,
You have done a great job in putting up a quick proposal. I was just trying to
understand the intentions/rational behind your proposal to be on the same page.
Thanks for the education. I think this will help others as well.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
On Wed, Aug 19, 2009 at 1:02 PM, Miguel wrote:
> oh, what a shame, :-s
>
> The USB id is:
>
> Bus 001 Device 011: ID 2040:6600 Hauppauge
>
>
> is this the version you commented that is not supported?
Ah, ok. So you really do have an HVR-900H and not an HVR-900 (either
R1 or R2). Since this is th
On Wed, Aug 19, 2009 at 12:19 PM, Lou Otway wrote:
> Hi there,
>
> I have a Hauppauge Nova-T 500 that is displaying some odd behaviour.
>
> Often the device fails to tune after rebooting the host machine, due to a
> failure to load firmware.
>
> when the firmware fails to load, dmesg shows:
>
> dib
Hi there,
I have a Hauppauge Nova-T 500 that is displaying some odd behaviour.
Often the device fails to tune after rebooting the host machine, due to
a failure to load firmware.
when the firmware fails to load, dmesg shows:
dib0700: loaded with support for 9 different device-types
dvb-usb:
Mauro,
Kevin has approved the architecture part of this patch. When can I expect these
to be merged to linux-next?
Thanks.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
>-Original Message-
>From: Karicheri, Muralidharan
Hi,
we are experiencing a problem with the V4L-DVB drivers.
It seems that when the system has over 4Gb the drivers
do no longer work properly. Either nothing or rubbish
comes out of them, although tuning using szap seems to
work. If we force the system to use only 4Gb by appending
mem=4GB as a
>> I'd really appreciate any help or guidance on this problem as i'm fully
>> perplexed by it.
>
> Hey Seth,
>
> I ran the same tests on my cable system (channel 103) on 669Mhz and had no
> issue, and my snr's reported as (0x172 and 0x17c).
>
> One possibility is that you're overwhelming the fronte
On Wed, Aug 19, 2009 at 7:01 AM, Miguel wrote:
>
> Hello,
>
> I am trying to set up the dvb-t device in my ubuntu 9.04.
> As far as i can see , this device has tm6000 chipset but I don't get it
> works. I have followed the guide of tvlinux.org:
> http://www.linuxtv.org/wiki/index.php/Trident_TM6000
On Mon, Aug 17, 2009 at 7:09 PM, Guennadi
Liakhovetski wrote:
> Hi Hans, all
>
> In soc-camera since its first version we have a parameter "y_skip_top",
> which the sensor uses to tell the host (bridge) driver "I am sending you
> that many lines more than what is requested, and you should drop thos
Hello,
I am trying to set up the dvb-t device in my ubuntu 9.04.
As far as i can see , this device has tm6000 chipset but I don't get it
works. I have followed the guide of tvlinux.org:
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6000_based_Devices
I have compile v4l-dvb, make, and ma
On 08/19/2009 10:42 AM, Pásztor Szilárd wrote:
Thierry Lelegard:
Stream type 0x1B precisely means AVC / H.264 video stream (cf. ISO
138181-1:2000/FDAM 3)
Try VLC instead of mplayer. VLC does render H.264 HD video, provided you
have a (very) good CPU.
Thanks for the info. Anyway, mplayer also
Thierry Lelegard:
> Stream type 0x1B precisely means AVC / H.264 video stream (cf. ISO
> 138181-1:2000/FDAM 3)
>
> Try VLC instead of mplayer. VLC does render H.264 HD video, provided you
> have a (very) good CPU.
Thanks for the info. Anyway, mplayer also does render H.264 of course, it's
the str
> Pásztor Szilárd:
> With scan -vv I could find the video PIDs
> for the HD channels and indeed they were missing in my channels.conf (values
> were 0) as scan detected them as "OTHER", but with a "type 0x1b" addition with
> which I don't know what to do for the time being...
Stream type 0x1B prec
2.6.27 worked for me - exact same board (ignoring revisions - mine is
an older board, rev.1, I think)
2.6.28 and up failed for me in exactly this manner. Same with a
head-of-tree v4l-dvb 'hg clone'
AFAICT it's a v4l-dvb driver problem - at least no-one here refutes it
since I reported it here on
32 matches
Mail list logo
