public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: George Czerw <gczerw@comcast.net>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Michael Krufky <mkrufky@linuxtv.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [linux-dvb] Hauppauge HVR-1800 not working at all
Date: Tue, 30 Jun 2009 17:49:05 -0400	[thread overview]
Message-ID: <200906301749.05168.gczerw@comcast.net> (raw)
In-Reply-To: <829197380906301256w2f0a701ak2332d9ec2cfae35e@mail.gmail.com>

On Tuesday 30 June 2009 15:56:08 Devin Heitmueller wrote:
> On Tue, Jun 30, 2009 at 3:48 PM, George Czerw<gczerw@comcast.net> wrote:
> > Devin, thanks for the reply.
> >
> > Lsmod showed that "tuner" was NOT loaded (wonder why?), a "modprobe
> > tuner" took care of that and now the HVR-1800 is displaying video
> > perfectly and the tuning function works.  I guess that I'll have to add
> > "tuner" into modprobe.preload.d????  Now if only I can get the sound
> > functioning along with the video!
> >
> > George
>
> Admittedly, I don't know why you would have to load the tuner module
> manually on the HVR-1800.  I haven't had to do this on other products?
>
> If you are doing raw video capture, then you need to manually tell
> applications where to find the ALSA device that provides the audio.
> If you're capturing via the MPEG encoder, then the audio will be
> embedded in the stream.
>
> Devin

I don't understand why the audio/mpeg ports of the HVR-1800 don't show up in 
output of lspci:

03:00.0 Multimedia video controller: Conexant Systems, Inc. Device 8880 (rev 
0f)
        Subsystem: Hauppauge computer works Inc. Device 7801                    
        Flags: bus master, fast devsel, latency 0, IRQ 17                       
        Memory at f9c00000 (64-bit, non-prefetchable) [size=2M]                 
        Capabilities: [40] Express Endpoint, MSI 00                             
        Capabilities: [80] Power Management version 2                           
        Capabilities: [90] Vital Product Data                                   
        Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable-                  
        Capabilities: [100] Advanced Error Reporting                            
        Capabilities: [200] Virtual Channel <?>                                 
        Kernel driver in use: cx23885                                           
        Kernel modules: cx23885


even though the dmesg output clearly shows this:

tveeprom 0-0050: decoder processor is CX23887 (idx 37) 
tveeprom 0-0050: audio processor is CX23887 (idx 42)



  parent reply	other threads:[~2009-06-30 21:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 17:01 [linux-dvb] Hauppauge HVR-1800 not working at all George Czerw
2009-06-30 17:43 ` Michael Krufky
     [not found]   ` <200906301451.52933.gczerw@comcast.net>
2009-06-30 19:18     ` Michael Krufky
2009-06-30 19:27       ` Devin Heitmueller
2009-06-30 19:48         ` George Czerw
2009-06-30 19:56           ` Devin Heitmueller
2009-06-30 20:29             ` George Czerw
2009-06-30 21:49             ` George Czerw [this message]
2009-06-30 21:50               ` Michael Krufky
2009-06-30 23:02                 ` George Czerw
2009-07-02 16:31                 ` George Czerw

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=200906301749.05168.gczerw@comcast.net \
    --to=gczerw@comcast.net \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mkrufky@linuxtv.org \
    /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