From: Per Oberg <pero@wolfram.com>
To: xenomai <xenomai@xenomai.org>
Subject: Re: Usage of xenomai-images
Date: Tue, 16 Jun 2020 01:10:12 -0500 (CDT) [thread overview]
Message-ID: <521678817.890223.1592287812570.JavaMail.zimbra@wolfram.com> (raw)
In-Reply-To: <87c60740-7bc5-4790-ff6d-424a325fa871@siemens.com>
----- Den 15 jun 2020, på kl 17:57, Jan Kiszka jan.kiszka@siemens.com skrev:
> On 15.06.20 17:34, Per Oberg via Xenomai wrote:
> > Hi list
>> I thought I'd take the xenomai-images from [1] out for a spin and I think I got
> > it working. However, A few pointers about what is what would have been helpful.
> > E.g.
>> Under "Building Target Images" there could have been a note saying that you need
>> the kas.yml files and board-qemu-amd64.yml available. I feel those instructions
> > are a bit incomplete.
> We are happy to take patches! It's always a bit tricky for the those
> using the tool every day in various projects to document the
> (non-)obvious parts for first-time users.
Thanks, I'll do that. I just need to get back up on Github again.
>> At docker-hub there are no comments/descriptions for the kas-isar and kas images
> > so it's a bit difficult to know what to use.
>> Now it seems to be working when using the provided "kas-docker" script, but then
>> I tried using a bind-mount and bash to get inside the docker and run it from
>> there. 'docker run -it --mount
> > type=bind,source="$HOME"/kas-builder,target=/builder kasproject/kas bash'.
> Such "simple" docker calls are where kas-docker evolved from. If you
> look at the latest version, it can do way more. It's goal is to provide
> the same frontend as kas natively.
>> For the "kas" docker image I get errors related to missing isar, and for the
>> kas-isar docker image i get "mount: /proc/sys/fs/binfmt_misc: permission
>> denied." so i tried adding the --privileged flag which seems to be working.
>> Perhaps there could be a better "Start Here" guide giving some hints about
> > this.
> "kas-docker --isar build ..." is doing that for you. "docker/podman run"
> is for the experts. That's why we documented the former.
>> Also, are there any binary links to -wic files that I can download and run using
> > my own qemu so that I don't have to build them myself?
> So far, there is no public build and, thus, artifacts. We will probably
> have them as catch-by of using xenomai-image for regular testing "soon".
> Jan
Great! I think that would be very helpful for attracting people to xenomai.
> > [1] https://gitlab.denx.de/Xenomai/xenomai-images
> > Per Öberg
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
Per Öberg
prev parent reply other threads:[~2020-06-16 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 15:34 Usage of xenomai-images Per Oberg
2020-06-15 15:57 ` Jan Kiszka
2020-06-16 0:32 ` Meng, Fino
2020-06-16 6:10 ` Per Oberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521678817.890223.1592287812570.JavaMail.zimbra@wolfram.com \
--to=pero@wolfram.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.