Update OpenAMP elevator pitch presentation to 2025-Q1 version

[nathalie-ckc]

A subcommittee of the OpenAMP Board collaborated on revising the pitch deck.

• Members: AMD-Xilinx logo is removed and replaced with AMD logo.
• Virtual devices are now included in the presentation.
• A slide about the OpenAMP technologies is added, so people know OpenAMP is more than openamp-rp
• HW and SW examples are added

The home page was updated to point to the new presentation PDF.

[nathalie-ckc]

@wmamills or @arnopo , I would appreciate if 1 of you could review before I merge.
Website preview is in the All checks have passed > Deploy preview > View details.
Thanks!

[arnopo]

Hi @nathalie-ckc

Here are some comments/proposals. Feel free to adapt or reject them.

• OpenAMP technologies (slide 8):

  • remoteproc
    • remove the linux term, remoteproc frameworks are also present at least in in open-amp/ u-boot/OP-TEE
  • virtio-msg
    • Issue in listing the virtio devices? Or need to remove the '-'.

• HW example: AMP SoC (slide 10):

  • in the picture I would replace
    - A53 with main processor.
    - Linux with main proc Fw and MCU with sec proc fw in DDR box
  • i would replace CPU that are SMP... with main processor that is SMP...
  • I would replace Other CPU are MCU like, used for with secondary processors (MCU, DSP, ...) used for
  • I would put board examples in alphabetic order
  • slide number is missing ( same for some other slides)

• HW example: AMP with PCIe (slide 10):

  • replace Arm with Arm Fw in DDR box

• HW example: Mixed Critical system w/hypervisor (slide 11):

  • replace A53 with CPU in pictures

• Sw examples

  • to report pictures updates

  • AMP SoC:

    • Devices and memory optionally assigned ...
    • Communicate through "RPMsg or VirtIO protocols" and I would remove last bullet.

  • AMP SoC:

    • Insert a bullet after first one: " inter system communication through virtio-msg over PCIe
    • remove over virtio-msg in other bullets

[nathalie-ckc]

Hi @arnopo ,

I'm making the changes in the Google Slides in the OpenAMP Drive. I will wait until we finalize before uploading.

OpenAMP Technologies

• Remoteproc: What do you think of
  "A Linux subsystem for loading and controlling coprocessors" -> "A subsystem for loading and controlling coprocessors, also used in Linux, U-Boot, OP-TEE." ?
• virtio-msg: I think @wmamills was putting the "-" because he didn't want to keep typing virtio, but intended it to be read as virtio-net, virtio-blk, etc.

HW/SW Examples

• I believe @wmamills is referring to a specific example design for each case, which is why it isn't general terms. @wmamills , please let me know if you want to incorporate any of @arnopo 's suggestions that generalize the examples
• I have added the page numbers & put the board examples in alphabetical order

[arnopo]

Hi @arnopo ,

I'm making the changes in the Google Slides in the OpenAMP Drive. I will wait until we finalize before uploading.

OpenAMP Technologies

• Remoteproc: What do you think of
  "A Linux subsystem for loading and controlling coprocessors" -> "A subsystem for loading and controlling coprocessors, also used in Linux, U-Boot, OP-TEE." ?

Linux, U-boot OPTEE are some examples, OpenAMP could be another.
I would just not mention OSes ->"A subsystem for loading and controlling coprocessors"

• virtio-msg: I think @wmamills was putting the "-" because he didn't want to keep typing virtio, but intended it to be read as virtio-net, virtio-blk, etc.

HW/SW Examples

• I believe @wmamills is referring to a specific example design for each case, which is why it isn't general terms. @wmamills , please let me know if you want to incorporate any of @arnopo 's suggestions that generalize the examples

At least the AMP SoC should use general term as it it a generic example. Indeed, we refer several platforms in HW Example: AMP SoC.

• I have added the page numbers & put the board examples in alphabetical order

[nathalie-ckc]

Hi Arnaud,

Linux, U-boot OPTEE are some examples, OpenAMP could be another.

The slides is called OpenAMP technologies, so it is already indicated that it's part of OpenAMP. That's why I omitted it from the "also used in" list.

[wmamills]

I have reviewed the PDF and it looks good to me.

Thanks Nathalie!