From: Dale Pontius <DEPontius@edgehp.net>
To: video4linux-list@redhat.com
Subject: Status of cx18 drivers, mercurial vs in-kernel
Date: Sun, 09 Aug 2009 16:56:51 -0400 [thread overview]
Message-ID: <4A7F3813.3050101@edgehp.net> (raw)
I've been running the cx18 drivers out of mercurial since getting my
HVR-1600 running, almost a year ago. As I see things, the driver is
pretty mature now, and in fact I see commits for cx18 in 2.6.31 that are
some of the last I saw going into the "regular" driver in mercurial.
(I'm not counting the diagnostic work that has been going on in the last
month or two, for one particular user.)
Is it reasonable to go with the in-kernel cx18 driver when 2.6.31 goes
stable, or is there still significant value with sticking with mercurial?
Dale Pontius
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2009-08-10 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 20:56 Dale Pontius [this message]
2009-08-15 13:46 ` Status of cx18 drivers, mercurial vs in-kernel Andy Walls
2009-08-15 19:20 ` Dale Pontius
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=4A7F3813.3050101@edgehp.net \
--to=depontius@edgehp.net \
--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