linux-kernel - Re: [RFC 0/8] Introducing a generic AMP/IPC framework

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 for Android: free password hash cracker in your pocket

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

Message-ID: <BANLkTimn-THKipuQVHLA9i3QSoO5RTqMtA@mail.gmail.com>
Date:	Tue, 21 Jun 2011 10:50:10 +0300
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Cc:	akpm@...ux-foundation.org, Brian Swetland <swetland@...gle.com>,
	Arnd Bergmann <arnd@...db.de>,
	Grant Likely <grant.likely@...retlab.ca>,
	davinci-linux-open-source 
	<davinci-linux-open-source@...ux.davincidsp.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [RFC 0/8] Introducing a generic AMP/IPC framework

On Tue, Jun 21, 2011 at 10:18 AM, Ohad Ben-Cohen <ohad@...ery.com> wrote:
> * I will be replying to this email with an attachment of the M3 firmware
>  image I work with, so anyone with a panda board can take the code for a
>  ride (put the image in /lib/firmware, and tell me if stuff doesn't work
>  for you: there are a few omap iommu fixes that are circulating but not
>  merged yet).

Attaching an OMAP4 M3 firmware.

Below is a simple session with it:

root@...p4430-panda:~# cat /debug/remoteproc/omap-rproc.1/name
ipu
root@...p4430-panda:~# cat /debug/remoteproc/omap-rproc.1/state
offline (0)

root@...p4430-panda:~# modprobe omap_rpmsg
[  222.245758] omap_device: omap-mailbox.-1: new worst case activate
latency 0: 30517
[  222.254669] omap-rproc omap-rproc.1: powering up ipu
[  222.263580] virtio_rpmsg_bus virtio0: rpmsg backend virtproc probed
successfully
[  222.272033] virtio_rpmsg_bus virtio1: rpmsg backend virtproc probed
successfully
[  222.325317] omap-rproc omap-rproc.1: Loaded fw image ducati-m3.bin,
size 161736
[  222.333068] omap-rproc omap-rproc.1: BIOS image version is 2
[  222.346099] omap-iommu omap-iommu.0: ducati: version 2.1
[  222.352661] omap_device: omap-rproc.1: new worst case activate
latency 0: 30517
[  222.360351] omap-rproc omap-rproc.1: remote processor ipu is now up
[  222.709411] omap_rpmsg_mbox_callback: received echo reply from ipu !
[  222.716156] omap_rpmsg_mbox_callback: received echo reply from ipu !
[  222.722869] omap_rpmsg_mbox_callback: received echo reply from ipu !
[  222.729583] omap_rpmsg_mbox_callback: received echo reply from ipu !
[  222.736419] virtio_rpmsg_bus virtio0: creating channel
rpmsg-client-sample addr 0x32
[  222.745361] virtio_rpmsg_bus virtio0: creating channel
rpmsg-client-sample addr 0x33
[  222.753814] virtio_rpmsg_bus virtio0: creating channel rpmsg-omx addr 0x3c
[  222.761535] virtio_rpmsg_bus virtio1: creating channel
rpmsg-client-sample addr 0x32
[  222.769989] virtio_rpmsg_bus virtio1: creating channel
rpmsg-client-sample addr 0x33
[  222.778411] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c

root@...p4430-panda:~# cat /debug/remoteproc/omap-rproc.1/state
running (2)

root@...p4430-panda:~# modprobe rpmsg_server_sample
[  509.860748] rpmsg_server_sample rpmsg0: new channel: 0x89 -> 0xffffffff!
[  509.871307] rpmsg_server_sample rpmsg0: incoming msg 1 (src: 0x32)
[  509.879608] rpmsg_server_sample rpmsg0: incoming msg 2 (src: 0x32)
[  509.887451] rpmsg_server_sample rpmsg0: incoming msg 3 (src: 0x32)
...

Download attachment "ducati-m3.bin" of type "application/octet-stream" (161736 bytes)