All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: fuego@lists.linuxfoundation.org
Subject: [Fuego] Board setup
Date: Tue, 11 Apr 2017 11:17:54 +0200	[thread overview]
Message-ID: <00467eb7-31d8-baff-8b12-f1175712fcac@monstr.eu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1241 bytes --]

Hi,

I have started to play with fuego with one arm64 board I have here.
I have a question about handling board itself. I have multiple
boards(home boardfarm) connected to my PC and every board needs to get
certain configuration before starts. At least power on.
And when test is done power off too.
How is this handled? I didn't find any hint how to do it.


Also default docker is not supporting /dev/serial/* which is elegant way
how to handle connecting to multiple boards connected to one PC.

Because what you need to really do is to connect to board via this link
SERIAL="/dev/serial/by-path/pci-0000:00:1d.0-usb-0:1.7.1.2.4.4:1.0-port0"
instead of just
SERIAL="/dev/ttyUSB10"
which is changing all the time.

Do you know what to do?

I am playing with serial setup and can you please tell me how tests are
moved from container to target? Is there any tree structure expected on
the target which should be followed?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2017-04-11  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  9:17 Michal Simek [this message]
2017-04-11 18:25 ` [Fuego] Board setup Bird, Timothy
2017-04-12  9:22   ` Michal Simek
2017-04-12 18:01     ` Bird, Timothy
2017-04-12 20:42       ` Michal Simek
2017-04-12 23:44     ` Frank Rowand
2017-04-13  5:05       ` Michal Simek

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=00467eb7-31d8-baff-8b12-f1175712fcac@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=fuego@lists.linuxfoundation.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.