From: Ed Sweetman <safemode@speakeasy.net>
To: hogger@mushworld.dnsart.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: bttv recording problems with kernel 2.2.21
Date: 01 Jun 2002 01:20:56 -0400 [thread overview]
Message-ID: <1022908856.10826.1.camel@psuedomode> (raw)
In-Reply-To: <Pine.LNX.4.33.0205312021180.729-100000@mushworld.dnsart.com>
it's not a problem with the kernel or bttv, your program needs to be
updated to utilize new drivers for the hardware that come out. that or
stay with the driver version that it supports (like you've been doing).
email those who make realproducer and have them support something
current.
prev parent reply other threads:[~2002-06-01 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 3:31 PROBLEM: bttv recording problems with kernel 2.2.21 hogger
2002-06-01 5:20 ` Ed Sweetman [this message]
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=1022908856.10826.1.camel@psuedomode \
--to=safemode@speakeasy.net \
--cc=hogger@mushworld.dnsart.com \
--cc=linux-kernel@vger.kernel.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