From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] what is a suitable type for /dev/media0
Date: Tue, 27 Sep 2011 08:55:10 -0400 [thread overview]
Message-ID: <4E81C7AE.80003@tresys.com> (raw)
In-Reply-To: <1317031809.9488.25.camel@x220.mydomain.internal>
On 09/26/11 06:10, Dominick Grift wrote:
>
> /dev/media0 character device node is currently labeled type device_t:
>
>> # matchpathcon /dev/media0
>> /dev/media0 system_u:object_r:device_t:s0
>
> What would be a suitable type for this device? v4l_device_t?
>
>> Media Device
>> A Media device is the umbrella device under which multiple
>> sub-entities called Media entities can be accessed, modified and
>> worked upon. The Media Device is exposed to the user in form of a
>> device file, which can be opened to enumerate, set and get the
>> parameters of each of the media entities. For example, in DM365
>> implementation the entire VPFE capture device with its IPIPE, IPIPEIF,
>> CCDC etc is exposed as a Media Device - /dev/media0. If there were a
>> display driver, it would be exposed as a Media device too.
It seems like that would be a reasonable label, but the description you provided isn't so helpful. Do you know what kernel module handles support for this device? Is it something under drivers/media? Alternatively, do you have examples of devices that are accessed through this node? From what I can google, it seems to support v4l_device_t, but I'd like a little more assurance.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-09-27 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 10:10 [refpolicy] what is a suitable type for /dev/media0 Dominick Grift
2011-09-27 12:55 ` Christopher J. PeBenito [this message]
2011-09-27 16:06 ` Dominick Grift
2011-10-04 12:26 ` Christopher J. PeBenito
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=4E81C7AE.80003@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.