All,
We have our normal meeting today in ~3.25 hours.
https://zoom.us/j/717134356
We have our standing items:
* Linux patch status
* Lib-openamp and lib-metal status
* openci update if any
Other items suggested by the group.
(I had some questions / comments about the remoteproc char driver if nothing else)
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
All,
We have our normal meeting tomorrow.
Standing Agenda Items:
* Linux patch activity
* Open-amp & Libmetal activity
* OpenAMP CI activity?
Suggestions for other topics (won't get to all of this)
* Deeper discussion of Mathieu's "MCU" sync patch set?
* Low Level implementation from Application Services call
* Enhancement to rpmsg name service
* Add endpoint description
* capabilities/feature flags per end-point
* VID:PID?
* Add optional endpoint description blobs
* expose to userspace (read via sysfs?)
* In-kernel API for request-response pattern
* More general binding for userspace API's (currently only rpmsg-char)
* rpmsg-char driver currently requires [unbind &] bind from userspace
* subtractive decode ? (bind to every name not found in kernel)
* bind to everything (in addition to in-kernel bind)
* bind via ctrl device?
* Socket interface in addition to rpmsg-char?
* bind to which?
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
All,
We have our meeting tomorrow.
We have our standing agenda:
* Linux Kernel pending patch status
* open-amp lib and libmetal status
* OpenAMP CI status
Anything else?
I have not sent the doodle pool for meeting at a conference in the next few months.
I think a lot of our companies have shutdown travel since we last talked.
I would like to get a verbal feel if a face to face meeting is practical in the next 3 to 6 months.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
All,
We have our meeting tomorrow.
We have our standing agenda:
* Linux Kernel pending patch status
* open-amp lib and libmetal status
* OpenAMP CI status
Anything else?
I have not sent the doodle pool for meeting at a conference in the next
few months.
I think a lot of our companies have shutdown travel since we last
talked.
I would like to get a verbal feel if a face to face meeting is
practical in the next 3 to 6 months.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
All,
We have our normal meeting tomorrow. Please think about agenda items.
On addition, I am collecting links to public git repos that contain carried or in-progress patches for all things remote proc.
I will round up the TI links.
If everyone else could send links to this list that would be great.
I will try to collect and correlate.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
All,
We have our normal meeting tomorrow. Please think about agenda items.
On addition, I am collecting links to public git repos that contain
carried or in-progress patches for all things remote proc.
I will round up the TI links.
If everyone else could send links to this list that would be great.
I will try to collect and correlate.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
Hi all,
One of the difficulties I have encountered while trying to get OpenAMP into the Linaro continuous integration loop, as well as while trying to test the GitHub OpenAMP repository code, has been the need to use proprietary tools and environments to build the OpenAMP firmware.This is what I think is needed to solve this problem. Feedback will be welcomed.
Goal: A complete open-source development environment for OpenAMP on
Linux for Cortex A and bare metal/FreeRTOS on Cortex R.
The first use for this is for Jenkins/LAVA testing. Just using a slightly
customized version of the Xilinx Yocto build for Linux and OpenAMP turns
out to be impractical due to the use of a Xilinx-specific toolchain
and the huge size of the resulting image.
The second use is for developers who want to work with OpenAMP and the
Linux kernel without needing to use a proprietary SDK or tool chain. In
fact, with the QEMU Docker container, they wouldn't even need real
hardware.
To do this requires:
Toolchains for the ARM Cortex A and Cortex R. I intend to use the
toolchains provided by ARM by default, but the eventual setup should allow
the user to switch to other toolchains, such as LLVM or a proprietary one.
A Linux root filesystem. I will create this using Yocto and a
stripped-down image recipe.
The necessary header files and libraries to compile and link
the Cortex R5 firmware for Xilinx first (the BSP). Later I
want to support other manufacturers as well.
A mechanism to update the root file system when the Linux kernel
or the OpenAMP binaries and firmware are updated.
A way of building bootable images, either for hardware or QEMU.
The above two items are part of the standard image build
process and will use available open source tools.
Something to run the resulting image. This will default to the
QEMU Docker image.
This should be easier to use for newcomers and facilitate the CI loop.
Steps:
1) Shrink the image. This can be done in two stages:
a. Build less stuff. The OpenAMP tests don't need full Perl and Python
installs, among other things.
b. Tune the kernel. There are a lot of modules we don't need.
This will also speed up build times considerably. It might even be
enough to get the CI loop started.
2) Set up the tooling to create root file systems
3) Set up the tooling to create images
4) Document all the steps required to create and boot an image.
5) Automate all of the above.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
[copy-pasted from the Google group]
This is to announce the release of OpenAMP 2020.01. It's a
"catch up" release that incorporates the low-risk changes
proposed for OpenAMP/libmetal since the last release. See
https://github.com/OpenAMP/open-amp/releases/tag/v2020.01.0 and
https://github.com/OpenAMP/libmetal/releases/tag/v2020.01.0
With the transition of the OpenAMP project to a Linaro open source project (https://openampproject.org), we anticipate a return to the normal 6-month release cycle in (approximately) April and October.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Bill and friends,
I would like to talk about the various patchsets floating on the
mailing list that I'm keeping an eye on. More specifically where I
think the work is at and what the next steps are. I came up with the
following list (not in order of priority) along with some comments
that we can expand on tomorrow.
1) "V5 remoteproc: updates for omap remoteproc support" [1]
Comments: I am waiting on the people at TI that commented on V5 to
provide their ACK/comments before doing another review.
2) "remoteproc: Add support for predefined notifyids" [2]
Comments: Consensus was to wait for a new resource table definition -
anyone working on this? If not I will.
3) "V3 rpmsg: core: add API to get MTU [3]
Comments: Bjorn said he wouldn't merge the set without a client.
Arnaud pointed to that client [4] in the thread. A new set with both
feature (MTU and RPMSG tty driver) needs to be published for 5.6-rc1
and I will review/test it.
4) "V4 remoteproc: add support for co-processor loaded and booted
before kernel" [5]
Comments: Please send a 5th version when 5.6-rc1 comes out. Tero or
Suman will have to ack it before it is eventually merged. On my side
I will look at how TI has implemented that feature.
5) "V2 remoteproc: Add elf64 support in elf loader" [6]
Comments: Good conversation, please comment or ack next version.
6) "V2 remoteproc: qcom: post mortem debug support" [7]
Comments: Good conversation with Bjorn and Arnaud, waiting for Bjorn
to release another version.
Those take us back to around the September timeframe, which is about
the time I started perusing around this project. If there is a set
you've been waiting on that dates before September, please send
another revision when 5.6-rc1 is released and I will review it.
See you all tomorrow,
Mathieu
[1]. https://patchwork.kernel.org/project/linux-remoteproc/list/?series=229249
[2]. https://patchwork.kernel.org/project/linux-remoteproc/list/?series=228473
[3]. https://patchwork.kernel.org/patch/11333509/
[4]. https://patchwork.kernel.org/cover/11130213/
[5]. https://patchwork.kernel.org/patch/11265869/
[6]. https://patchwork.kernel.org/project/linux-remoteproc/list/?series=182999
[7]. https://patchwork.kernel.org/project/linux-remoteproc/list/?series=221715
On Wed, 29 Jan 2020 at 12:16, Mills, William via Openamp-rp
<openamp-rp(a)lists.openampproject.org> wrote:
>
> Hello all,
>
>
> A reminder that we have normal meeting of openamp-rp sub-project
> tomorrow.
>
> Please think about agenda topics or it will be a short meeting.
>
>
> Thanks,
>
> Bill
>
>
> ---------------------------------------------------
>
> William A. Mills
>
> Chief Technologist, Open Source
>
> Texas Instruments, Processors
>
> 20250 Century Blvd, Suit 300
>
> Germantown MD, 20874
>
> (work/mobile) +1-240-643-0836
> --
> Openamp-rp mailing list
> Openamp-rp(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/openamp-rp
Hello all,
A reminder that we have normal meeting of openamp-rp sub-project tomorrow.
Please think about agenda topics or it will be a short meeting.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
Hello all,
A reminder that we have normal meeting of openamp-rp sub-project
tomorrow.
Please think about agenda topics or it will be a short meeting.
Thanks,
Bill
---------------------------------------------------
William A. Mills
Chief Technologist, Open Source
Texas Instruments, Processors
20250 Century Blvd, Suit 300
Germantown MD, 20874
(work/mobile) +1-240-643-0836
