From: Brice Dubost <dubost@crans.org>
To: Benedict bdc091 <bdc091@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: how to get a registered adapter name
Date: Fri, 27 Nov 2009 15:08:38 +0100 [thread overview]
Message-ID: <4B0FDD66.9090903@crans.org> (raw)
In-Reply-To: <746d58780909140842o8952bf1g8f7851eee9ec0093@mail.gmail.com>
Benedict bdc091 wrote:
> Hi list,
>
> I'd like to enumerate connected DVB devices from my softawre, based on
> DVB API V3.
> Thank to ioctl FE_GET_INFO, I'm able to get frontends name, but they
> are not "clear" enough for users.
>
> After a "quick look" in /var/log/messages I discovered that adapters
> name are much expressives:
>
>> ...
>> DVB: registering new adapter (ASUS My Cinema U3000 Mini DVBT Tuner)
>> DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
>> ...
>
> So, I tried to figure out a way to get "ASUS My Cinema U3000 Mini DVBT
> Tuner" string from adapter, instead of "DiBcom 7000PC" from adapter's
> frontend...
> Unsuccefully so far.
>
> Any suggestions?
>
Hello,
I have the same issue, I look a bit to the code of the DVB drivers, it
seems not obvious to recover this name as it is written now
It is stored in the "struct dvb_adapter". and printed by
dvb_register_adapter, but doesn't seems to be available by other functions
I don't think changing the v3 API or adding a new IOCTL for this is a
good idea.
What about using the new DVB API (v5) to do this? Since I'm not an
expert with this API, is there some people familiar with it which can
give me advices about the good way to do it (and if it is a good idea)
so that I can start to write some code.
Thank you
Regards
next prev parent reply other threads:[~2009-11-27 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 15:42 how to get a registered adapter name Benedict bdc091
2009-11-27 14:08 ` Brice Dubost [this message]
2009-11-27 17:56 ` Matthias Schwarzott
2009-11-28 11:45 ` DUBOST Brice
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=4B0FDD66.9090903@crans.org \
--to=dubost@crans.org \
--cc=bdc091@gmail.com \
--cc=linux-media@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 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.