From: DUBOST Brice <dubost@crans.ens-cachan.fr>
To: Matthias Schwarzott <zzam@gentoo.org>
Cc: linux-media@vger.kernel.org, Benedict bdc091 <bdc091@gmail.com>
Subject: Re: how to get a registered adapter name
Date: Sat, 28 Nov 2009 12:45:28 +0100 [thread overview]
Message-ID: <4B110D58.40304@crans.ens-cachan.fr> (raw)
In-Reply-To: <200911271856.48877.zzam@gentoo.org>
Matthias Schwarzott a écrit :
> On Freitag, 27. November 2009, Brice Dubost wrote:
>> Benedict bdc091 wrote:
>>> Hi list,
>>>
>>> I'd like to enumerate connected DVB devices from my softawre, based on
>>> DVB API V3.
>
>>> 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 think putting it somewhere into sysfs is a good idea (along with frontend
> name).
> Best is to move all dvb sysfs-devices into a per adapter subdirectory.
>
Hello
Is there already parts of the DVB code that use explicitely sysfs ?
I pehraps missed something, but it seems that everything in sysfs
concerning DVB is coming from the subsystems (PCI, or USB) or the
modules parameters but no DVB wide information
Am I wrong ?
Is there a reason for this ?
--
Brice
A: Yes.
>Q: Are you sure?
>>A: Because it reverses the logical flow of conversation.
>>>Q: Why is top posting annoying in email?
prev parent reply other threads:[~2009-11-28 11:45 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
2009-11-27 17:56 ` Matthias Schwarzott
2009-11-28 11:45 ` DUBOST Brice [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=4B110D58.40304@crans.ens-cachan.fr \
--to=dubost@crans.ens-cachan.fr \
--cc=bdc091@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=zzam@gentoo.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