From: Manu Abraham <abraham.manu@gmail.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ?
Date: Mon, 03 Mar 2008 16:03:09 +0400 [thread overview]
Message-ID: <47CBE8FD.9030303@gmail.com> (raw)
In-Reply-To: <20080303112610.GC6419@paradigm.rfc822.org>
Florian Lohoff wrote:
> On Mon, Mar 03, 2008 at 03:09:23PM +0400, Manu Abraham wrote:
>>> As i already wrote - SET_PARAMS is _NOT_ enough. Please try yourself.
>>> Unload/Load the module and simple issue a DVBFE_SET_PARAMS (NOT
>>> GET_INFO) and it doesnt tune/lock at least for STB0899 and it also
>>> complains in the dmesg with:
>>>
>>> stb0899_search: Unsupported delivery system 0
>>> stb0899_read_status: Unsupported delivery system 0
>>> stb0899_search: Unsupported delivery system 0
>>> stb0899_read_status: Unsupported delivery system 0
>>> stb0899_search: Unsupported delivery system 0
>>> stb0899_read_status: Unsupported delivery system 0
>>>
>>> although i set
>>>
>>> dvbfe_params.delivery=DVBFE_DELSYS_DVBS2;
>> Yep, it isn't supposed to work that way with simply issuing SET_PARAMS.
>
> Okay - So either
>
> - remove the "delivery" in the dvbfe_params because it is unnecessary,
> confusing and broken, and rename the GET_INFO call to SET_DELIVERY
> or something which implies that its not a _GET_ call
As you can see, removing delivery is not an option, since GET_PARAMS
operates
on the same data structure. Removal of which will require the application to
issue an additional ioctl call.
> or
>
> - make SET_PARAMS the call to honor delivery in dvbfe_params and remove
> the setting of the delivery of GET_INFO
>
> I'd prefere the 2nd option because currently the usage and naming
> is an incoherent mess which should better not get more adopters ..
Your 2nd option won't work at all. It is completely broken when you have
to query statistics, before a SET_PARAMS.
Additionally, this was quite discussed in a long discussion a while
back. You
might like to read through those as well.
Maybe DVBFE_GET_INFO can probably be renamed to DVBFE_INFO if it really
itches so much.
HTH,
Manu
_______________________________________________
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-03-03 12:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:14 [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ? Florian Lohoff
2008-03-02 22:43 ` Manu Abraham
2008-03-02 23:36 ` Florian Lohoff
2008-03-03 0:22 ` Manu Abraham
2008-03-03 8:52 ` Florian Lohoff
2008-03-03 11:09 ` Manu Abraham
2008-03-03 11:26 ` Florian Lohoff
2008-03-03 12:03 ` Manu Abraham [this message]
2008-03-03 13:21 ` Florian Lohoff
2008-03-03 13:41 ` Manu Abraham
2008-03-03 13:44 ` Florian Lohoff
2008-03-03 13:55 ` Manu Abraham
2008-03-03 14:00 ` Florian Lohoff
2008-03-03 13:49 ` Manu Abraham
2008-03-03 13:48 ` Florian Lohoff
2008-03-03 14:04 ` Manu Abraham
2008-03-03 14:03 ` Florian Lohoff
2008-03-03 14:17 ` Manu Abraham
2008-03-03 14:13 ` Florian Lohoff
2008-03-03 14:24 ` Manu Abraham
2008-03-03 14:23 ` Florian Lohoff
2008-03-03 21:13 ` Christoph Pfister
2008-03-04 0:52 ` hermann pitton
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=47CBE8FD.9030303@gmail.com \
--to=abraham.manu@gmail.com \
--cc=flo@rfc822.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox