On Mon, Feb 14, 2011 at 12:01 PM, Jamie Iles [off-list ref] wrote:
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
quoted
=A0 =A0 1. Hardware specific bits somewhere under '.../arch/*'. =A0Drive=
rs
quoted
=A0 =A0 =A0 =A0for the MPIC message registers on Power and OMAP4 mailbox=
es, for
quoted
=A0 =A0 =A0 =A0example.
=A0 =A0 2. A higher level driver under '.../drivers/mailbox/*'. =A0That =
the
quoted
=A0 =A0 =A0 =A0pieces in (1) would register with. =A0This piece would ex=
pose the
quoted
=A0 =A0 =A0 =A0main kernel API.
=A0 =A0 3. Userspace interfaces for accessing the mailboxes. =A0A
=A0 =A0 =A0 =A0'/dev/mailbox1', '/dev/mailbox2', etc... mapping, for exa=
mple.
How about using virtio for all of this and having the mailbox as a
notification/message passing driver for the virtio backend?
This is exactly what we are doing now, and it looks promising. expect
patches soon.