public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Vivek Periaraj <vivek.periaraj@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hauppauge WinTV USB 2
Date: Wed, 23 Feb 2011 19:38:48 -0300	[thread overview]
Message-ID: <4D658C78.2080907@gmail.com> (raw)
In-Reply-To: <AANLkTikNiEKZNVs1DGDvuLR0r+XTWLgi03nbk=272fqj@mail.gmail.com>

Em 23-02-2011 18:26, Devin Heitmueller escreveu:
> On Wed, Feb 23, 2011 at 4:25 PM, Vivek Periaraj
> <vivek.periaraj@gmail.com> wrote:
>> Hi Devin,
>>
>> Thanks for the reply!
>>
>> Like you advised, I took the latest code and started building it as mentioned
>> in this link --> http://linuxtv.org/wiki/index.php/Trident_TM6000 but getting
>> this error:

The information at the wiki page for this device is outdated. Support is now upstream.

Although I know that some Hauppauge devices are supported by tm6010, I'm not sure 
if someone added the tm6010 USB ID's for The model you have to the tm6000 driver.

>>
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-core.c: In function
>> 'tm6000_init_analog_mode':
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-core.c:339: warning: ISO C90
>> forbids mixed declarations and code
>>  CC [M]  /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-i2c.o
>>  CC [M]  /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-video.o
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-video.c: In function
>> 'tm6000_uninit_isoc':
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-video.c:522: error: implicit
>> declaration of function 'usb_free_coherent'
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-video.c: In function
>> 'tm6000_prepare_isoc':
>> /mnt/share1/Debian/Hauppauge/v4l-dvb/v4l/tm6000-video.c:612: error: implicit
>> declaration of function 'usb_alloc_coherent'
> <snip>
> 
> Questions like this should be directed to the mailing list and not me
> personally, where any number of people can help you out with basic
> build problems.
> 
> Regards,
> 
> Devin
> 


  reply	other threads:[~2011-02-23 22:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 19:46 Hauppauge WinTV USB 2 Vivek Periaraj
2011-02-23 20:00 ` Devin Heitmueller
     [not found]   ` <201102240255.00946.Vivek.Periaraj@gmail.com>
2011-02-23 21:26     ` Devin Heitmueller
2011-02-23 22:38       ` Mauro Carvalho Chehab [this message]
2011-02-24 20:49         ` Vivek Periaraj
2011-03-08  0:26           ` Vivek Periaraj
2011-03-09  6:00             ` Vivek Periaraj
2011-02-24 14:43       ` Vivek Periaraj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D658C78.2080907@gmail.com \
    --to=maurochehab@gmail.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=vivek.periaraj@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox