From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
linux1394-devel@lists.sourceforge.net,
video4linux-list@redhat.com, sensors@stimpy.netroedge.com
Subject: Re: 2.6.11-mm2 vs audio for kino and tvtime
Date: Wed, 09 Mar 2005 02:43:04 -0500 [thread overview]
Message-ID: <200503090243.06270.gene.heskett@verizon.net> (raw)
In-Reply-To: <20050308224441.2e29f895.akpm@osdl.org>
On Wednesday 09 March 2005 01:44, Andrew Morton wrote:
>Gene Heskett <gene.heskett@verizon.net> wrote:
>> Greetings Andrew;
>
>g'day.
>
g'day to you, sir.
>> 2.6.11-mm2 seems to work, mostly.
>>
>> First, the ieee1394 stuff seems to have fixed up that driver, and
>> kino can access my movie cameras video over the firewire very
>> nicely without applying the bk-ieee1394-patch. The camera has
>> builtin stereo mics in it, but nary a peep can be heard from it
>> thru the firewire. Am I supposed to be able to hear that?
>
>Was it working with 2.6.11+bk-ieee1394.patch? Or with anything
> else?
It did work previously with the svn download from the ieee1394 site
for the kernels in the series of RT stuff that Ingo Molnar was
working on. Also, since I posted this, I tried catting a .wav file
to /dev/dsp, which is the output that kino is expecting to use, and
that sort of worked, playing the file at half speed and pitch. So I
believe its the upload from the camera, and the stripping of the
audio data from the stream from the camera thats at fault. But thats
just a SWAG on my part, & I probably should not have used the S
there. :)
>Cc'ed linux1394-devel@lists.sourceforge.net
>
>> Second, I have a pdHDTV-3000 card, and up till now I've been
>> overwriting the bttv stuffs with the drivers in pcHDTV-1.6.tar.gz
>> by doing a make clean;make;make install. But now thats broken,
>> and the error message doesn't seem to make sense to this old K&R C
>> guy.
>>
>> The error exit:
>> make[1]: Entering directory `/usr/src/linux-2.6.11-mm2'
>> CC
>> [M]
>> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.o
>> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.c:36
>>2: error: unknown field `id' specified in initializer
>> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.c:36
>>2: warning: missing braces around initializer
>> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.c:36
>>2: warning: (near initialization for
>> `bttv_i2c_client_template.released')
>> make[2]: ***
>> [/usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.o]
>> Error 1
>> make[1]: ***
>> [_module_/usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver]
>> Error 2
>> make[1]: Leaving directory `/usr/src/linux-2.6.11-mm2'
>> make: *** [modules] Error 2
>>
>> The braces are indeed there.
>
>What's pcHDTV-1.6.tar.gz? If it was merged up then these things
> wouldn't happen.
>
This is the latest driver set for this card, downloadable from the
pcHDTV site. It overwrites, when it builds and installs, the bttv
and cx88xx stuffs in the modules dir. And it has worked up to
2.6.11-mm2, but I didn't get around to trying mm1. It worked with the
last of the RT's from Ingo, and for 2.6.11(.1).
>CC'ed video4linux-list@redhat.com
>> Third, somewhere between 2.6.11-rc5-RT-V0.39-02 and 2.6.11, I've
>> lost my sensors except for one on the motherboard called THRM by
>> gkrellm-2.28. Nothing seems to be able to bring the w83627hf back
>> to life.
I'm back on 2.6.11-rc5 and thats working as expected now.
>CC'ed sensors@Stimpy.netroedge.com
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2005-03-09 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 4:26 Gene Heskett
2005-03-09 6:44 ` Andrew Morton
2005-03-09 7:43 ` Gene Heskett [this message]
2005-03-09 19:33 ` Jean Delvare
2005-03-10 0:27 ` Gene Heskett
2005-03-10 8:52 ` Jean Delvare
2005-03-10 12:43 ` Gene Heskett
2005-03-10 0:37 ` Gene Heskett
2005-03-10 1:04 ` Gene Heskett
2005-03-10 23:02 ` Gene Heskett
[not found] ` <20050321153728.2f239b49.akpm@osdl.org>
2005-03-22 2:35 ` 2.6.11-mm2 vs audio for kino and tvtime, now 2.6.12-rc1-mm1 Gene Heskett
2005-03-22 2:56 ` Andrew Morton
2005-03-22 3:20 ` Gene Heskett
[not found] ` <200503212033.59753.gene.heskett@verizon.net>
[not found] ` <20050321174507.6113be4e.akpm@osdl.org>
2005-03-24 4:49 ` 2.6.11-mm2 vs audio for kino and tvtime Gene Heskett
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=200503090243.06270.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sensors@stimpy.netroedge.com \
--cc=video4linux-list@redhat.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
all inboxes | Powered by JetHome®