From: Steven Toth <stoth@linuxtv.org>
To: Jaap Crezee <jaap@jcz.nl>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] S2API vs Multiproto vs TT 3200
Date: Tue, 07 Oct 2008 11:07:04 -0400 [thread overview]
Message-ID: <48EB7B18.50703@linuxtv.org> (raw)
In-Reply-To: <48EB5A9D.1090609@jcz.nl>
Jaap Crezee wrote:
> Hello everyone,
>
> gimli wrote:
>> Hi All,
>>
>
> <snip>
>
>> was made. Please cool down and bring the pieces together to give the
>> user the widest driver base and support for S2API.
>
> With this in mind, I would like to work on porting the TT S2-3200 driver stuff to S2API. I have done a little bit of
> research and found out that it is hard to find what the differences are between both API's on a source/technical level.
> Can anyone offer some insight into differences or give some starting point (or maybe even an example) of how to port
> Multiproto drivers to the S2API?
Great!
Check the cx24116.c inkernel driver, see the set_frontend callback.
You'll see how it queries a dtv_property_cache held in the frontend.
This is the best place to begin.
Let me know if you have any other questions. If you do plan to port the
drivers, I suggest you create another thread with an appropriate subject
"porting TT3200 to S2API" or something similar, if you want people to
comment and help.
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-10-07 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 12:40 [linux-dvb] S2API vs Multiproto vs TT 3200 gimli
2008-10-07 12:48 ` Jaap Crezee
2008-10-07 14:06 ` Gregoire Favre
2008-10-07 15:07 ` Steven Toth [this message]
2008-10-07 16:59 ` Manu Abraham
2008-10-07 18:52 ` Christophe Thommeret
2008-10-07 20:48 ` hermann pitton
2008-10-07 14:31 ` Igor M. Liplianin
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=48EB7B18.50703@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=jaap@jcz.nl \
--cc=linux-dvb@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.