examples: linux: add rpmsg udev rules and scripts#101
examples: linux: add rpmsg udev rules and scripts#101tnmysh wants to merge 1 commit intoOpenAMP:mainfrom
Conversation
Linux userspace apps can't use rpmsg devices without root access. Introduce udev rules to modify rpmsg device permissions so that userspace apps can use these devices. Also, create symlink to rpmsg device with channel name, src ept and dest ept. Apps can use these symlinks directly without going through sysfs to find out which rpmsg device to use. This makes apps to use rpmsg devices very easy. It is also required to add current user to "rpmsg" group for apps to use rpmsg devices now. This also makes sure rpmsg communication is secure. Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
tnmysh
force-pushed
the
rpmsg_udev_rules
branch
from
f211025 to
572a775
Compare
arnopo
left a comment
arnopo
left a comment
There was a problem hiding this comment.
I'm not an udev expert, I need to play with it but look nice in a first approach.
In addition of the licensing, I wonder if it should not be a sub-folder of examples/linux/rpmsg-utils. Indeed there is a dependency with rpmsg_utils
what about putting it in examples/linux/rpmsg-utils/udev ?
| # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN | ||
| # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) | ||
| # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE | ||
| # POSSIBILITY OF SUCH DAMAGE. |
There was a problem hiding this comment.
can we use BSD-3-Clause license instead?
I am still unsure if these scripts will work only for xlnx platform or it will be vendor agnostic ? If it works for all the vendors, then we can keep it under rpmsg-utils. If not, then probably create vendor directory and each vendor can have their own udev rules and directories. |
3 participants
Linux userspace apps can't use rpmsg devices without root access. Introduce udev rules to modify rpmsg device permissions so that userspace apps can use these devices. Also, create symlink to rpmsg device with channel name, src ept and dest ept. Apps can use these symlinks directly without going through sysfs to find out which rpmsg device to use. This makes apps to use rpmsg devices very easy. It is also required to add current user to "rpmsg" group for apps to use rpmsg devices now. This also makes sure rpmsg communication is secure.