From: Bill Davidsen <davidsen@tmr.com>
To: gene.heskett@verizon.net
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc1 report
Date: Mon, 21 Mar 2005 17:34:26 -0500 [thread overview]
Message-ID: <423F4BF2.8050603@tmr.com> (raw)
In-Reply-To: <200503191503.26128.gene.heskett@verizon.net>
Gene Heskett wrote:
> Greetings;
>
> Usually I come looking for a bone when I post here, but today its with
> verbal flowers in hand.
>
> I just built 2.6.12-rc1 and I'm pleased to report that the ieee1394
> problems that required the bk-ieee1394.patch previously are
> apparently alleviated. Kino worked as expected, including the audio
> from the cameras microphones.
>
> tvtime, with my pcHDTV-3000 card, had a miss-cue due to the wrong
> modprobe statement in my rc.local, so I cleaned out those modules
> that it had loaded, and reloaded them with the 'modprobe cx88_dvb'
> statement, which brought that up with working video but raw noise for
> audio at about +40db! Going into its menu's for tv standards I chose
> to 'restart with new values' without changing anything which restored
> the audio to normal. Thats happened before, and Jack tells me there
> will be another coding session this weekend so there will no doubt be
> more patches for that. This FWIW, was without actually installing
> either version of his drivers, so this is nice progress.
>
> My scanner works normally. As does the spca5xx stuffs that I did
> install again after the boot.
What distro are you using with this? Before I report problems I want to
eliminate distro errors of the type you describe.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-03-21 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 20:03 Gene Heskett
2005-03-21 22:34 ` Bill Davidsen [this message]
2005-03-21 23:02 ` 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=423F4BF2.8050603@tmr.com \
--to=davidsen@tmr.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--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®