linux-kernel - Re: permission to move definition of struct rpmsg_channel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 8 Sep 2013 14:27:11 +0200
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	Arjun Gopalan <agopalan@...dia.com>
Cc:	Brian Swetland <swetland@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Paul Walmsley <pwalmsley@...dia.com>
Subject: Re: permission to move definition of struct rpmsg_channel_info

Hi Arjun,

On Fri, Aug 30, 2013 at 9:20 PM, Arjun Gopalan <agopalan@...dia.com> wrote:
>
> Hi Ohad/Brian,
>
> I have been working on rpmsg and I need to be able to create static rpmsg channels. Channel information needs to be specified by other drivers and for this, the drivers need access to struct rpmsg_channel_info.

I'm not convinced how useful it is for other Linux drivers to create
static rpmsg channels?

Usually these channels reflect the existence of services running on
the remote processor, and their creation (or lack thereof) should be
specified in the remote image. This way an rpmsg channel is published
iff there is a matching remote service.

The way we were planning to add static channels functionality (I
should still have preliminary patches doing this somewhere but the
entire work was put on hold since TI changed its focus) is by
statically publishing them in the resource table, which is coupled
with a specific remote image.

Best,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/