[linux-dvb] [RFC] Should a DVB frontend report the board name?

Peter D. peter_s_d at fastmail.com.au
Wed Feb 7 06:03:10 CET 2007


On Wednesday 07 February 2007 09:15, Manu Abraham wrote:
> On 2/7/07, Hartmut Hackmann <hartmut.hackmann at t-online.de> wrote:
> > Manu Abraham schrieb:
> > > On 2/6/07, Christophe Thommeret <hftom at free.fr> wrote:
> > >> Le mardi 06 février 2007 01:34, Markus Rechberger a écrit:
> > >> > > The name of a frontend should be that of the frontend itself and
> > >> > > not the board, if it reports the board name then it is wrong,
> > >> > > since the board is not the frontend.
> > >> >
> > >> > not that this is very important but I've seen that some people
> > >> > were confused because of displaying the name of the demodulator,
> > >> > they stated out that they own product xy and not a ZL10353, MT352,
> > >> > etc.
> > >>
> > >> Indeed, i think that for a user
> > >> "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
> > >> makes more sense than
> > >> "ST STV0299 DVB-S"
> > >> but in the latter case, the board name
> > >> "Philips Semiconductors SAA7146 (rev 01)"
> > >> is also somewhat "mysterious" when the user would expect
> > >> "WinTV Nova CI"
> > >> ;)
> > >
> > > The issue is that the board name shouldn't be the name of the
> > > frontend. I did have the issue taht which you mentioned, but that i
> > > did have a fix to it by using the adapter device that i mentioned
> > > sometime back in another thread on a mantis bridge.
> > >
> > > With this it gives the bridge name, Generic name and the frontend
> > > name, all in it's own relevant place and not in the frontend. it will
> > > be just messing up the frontend to a state where it will be hopeless.
> > >
> > > for example:
> > > bridge name = "Mantis PCI rev 1.0"
> > > Generic name = "VP-1034"
> > > frontend name = "MB86A16 DVB-S/DSS DC receiver"
> > >
> > > It additionally fixes some other issues as well, such as handling
> > > bridge reset 's etc.
> > >
> > > Will post the changes after i have cleaned it up, most probably will
> > > push it along with the multiproto/stb0899 tree.
> > >
> > > Manu
> >
> > Hm, we technical guys tend to associate "frontend" with the channel
> > decoder / tuner combination but the average user can can easily assume
> > that the frontend is the entire card. He has no idea what the functions
> > of the chips are.
>
> frontend = demod name (that's what we have currently), Tuner is
> unimportant in this case as it doesn't have much of ops.
>
> for the average person, frontend = RF module, inclusive of the demod
>
> the problem comes when you have 2 different frontends on one bridge.
> The user get's even more confused. Tune to board frontend 0 /1 ? which
> is frontend 0 which is frontend 1 ?
>
> There needs to be clear distinction when multiple devices exists.
>
> So in your case you are always tuning to your board name, irrespective
> of the number of frontends. IMHO, in the case where you had one
> frontend (with demod as name) is not as  confusing compared to this
> scenario.
>
> Assuming that a board has multiple demods.

I feel qualified to comment for the ignorant user.  ;-)  

My guess is that they would expect something like; "MSI TV at nywhere A/D, 
using analogue tuner" or "MSI TV at nywhere A/D, using digital tuner".  I 
would also guess that the the people reading this list would expect much 
more detailed information, such as, SAA7134 etc.  

> > But ack, we should be as precise as possible.
> > So the next question is: If we have the entries you propose, how do
> > these get reported to user space? Currently, the API only reports the
> > frontend type.
>
> In multiproto, there is DVBFE_GET_INFO, working with that as a base.
> It is extendable to the adapter object.
>
> Currrently playing around with a bit with some devices on the same in
> that aspect
>
>
> manu
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

-- 
sig goes here...
Peter D.



More information about the linux-dvb mailing list