From: Andrew Morton <akpm@osdl.org>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.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: Tue, 8 Mar 2005 22:44:41 -0800 [thread overview]
Message-ID: <20050308224441.2e29f895.akpm@osdl.org> (raw)
In-Reply-To: <200503082326.28737.gene.heskett@verizon.net>
Gene Heskett <gene.heskett@verizon.net> wrote:
>
> Greetings Andrew;
g'day.
> 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?
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:362:
> error: unknown field `id' specified in initializer
> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.c:362:
> warning: missing braces around initializer
> /usr/pcHDTV3000/linux/pcHDTV-1.6/kernel-2.6.x/driver/bttv-i2c.c:362:
> 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.
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.
CC'ed sensors@Stimpy.netroedge.com
next prev parent reply other threads:[~2005-03-09 6:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 4:26 2.6.11-mm2 vs audio for kino and tvtime Gene Heskett
2005-03-09 6:44 ` Andrew Morton [this message]
2005-03-09 7:43 ` Gene Heskett
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=20050308224441.2e29f895.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=gene.heskett@verizon.net \
--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