From: Manu Abraham <abraham.manu@gmail.com>
To: Peter Paul <abnominales@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is saa716x abandoned?
Date: Fri, 4 Dec 2009 11:06:34 +0400 [thread overview]
Message-ID: <1a297b360912032306i57d62509k7e2aeba7916fc63d@mail.gmail.com> (raw)
In-Reply-To: <467878267@web.de>
On Fri, Dec 4, 2009 at 4:33 AM, Peter Paul <abnominales@web.de> wrote:
> Hello,
> I was wondering about the future of the saa716x [1] driver that handles DVB hardware that uses either the saa7160, saa7161, saa1762 or saa1763 chip.
> Has development ceased or was it just moved somewhere else? The driver does not even compile with the latest kernel anymore as of API changes.
I didn't have really much free time the past 2 - 3 months. Development
became slow and still using the same kernel version for development:
2.6.25. The tree had been a minimal tree to have a minimal tree for
ease of handling during the development process (minimal download
time), will be migrating to the standard build this week.
Regards,
Manu
prev parent reply other threads:[~2009-12-04 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 0:33 Is saa716x abandoned? Peter Paul
2009-12-04 7:06 ` Manu Abraham [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=1a297b360912032306i57d62509k7e2aeba7916fc63d@mail.gmail.com \
--to=abraham.manu@gmail.com \
--cc=abnominales@web.de \
--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