All of lore.kernel.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Workshop requirements
Date: Wed, 9 Aug 2017 14:43:07 +0100	[thread overview]
Message-ID: <598B116B.3020904@codethink.co.uk> (raw)
In-Reply-To: <598B0E1D.3050901@codethink.co.uk>

Hi,

On 09/08/17 14:29, Agustin Benito Bethencourt wrote:
> Hi,
>
> I would like to share this idea of an activity for the workshop at ELCE.
>
> Title: B at D 101: how to test the CIP kernel using B at D
>
> Goal: learn the basics of B at D in order to test the CIP kernel and CIP
> system.
>
> Description: B at D is a testing environment based on LAVA + KernelCI that
> allows you to test a kernel or a simple system in a board set up
> locally, like for example, connected to your own laptop. The workshop
> will guide you on the installation and configuration of the environment.
> Using the CIP kernel and system, those participating in the training
> session will learn how to execute tests on the board, get the results
> and interpret them.
>
> Number of participants: 8 - 10
>
> Pre-requisites:
>
> Participants:
> * A laptop with enough space to install B at D (I will provide on time
> exactly how much)
> * BBB and cables to connect it to the laptop (I will provide more
> details when the time comes)
> * We should have CIP reference boards for those who cannot take theirs.
> The idea would be to have 3 to 5. I am in discussion with Chris to
> evaluate the possibility of having some Renesas boards and basic support
> there to set them up.
>
> Room:
> * A power strip per participant (2 power sockets per participant, 1 for
> the laptop and one for the board). 4 power sockets for the trainer.
> * Wifi
> * Projector
>
> Duration: 90 or 120 min
> Date: Sunday Oct 22nd in the afternoon
>
> Considerations:
> * Robert Marshall from Codethink would be the trainer.
> * The room needs to afford the power strips required. We will need
> confirmation about this specific point. (Annie?)
> * CIP would have to assume the material costs:
> ** Power strips
> ** Some serial cables
> ** USB sticks to have the needed software pre-loaded
> * Codethink can take care of buying and bringing this material if there
> is no other alternative. We would provide an invoice later on to CIP.

- * If we go for this activity, maybe we can somehow re-use it to 
another activity related with kernel maintenance of Project X.
+ * If we go for this activity, maybe we can somehow re-use the set up 
for an additional activity related with kernel maintenance or Project X.
>
> What do you think about this? It is something Members and wider CIP
> community consider as of value? Is it worth the effort? Will we have
> enough audience the day before ELCE?
>
> I will create the wiki page for coordinating the workshop in the coming
> days.
>
>
> Best regards
>

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

      reply	other threads:[~2017-08-09 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 13:29 [cip-dev] Workshop requirements Agustin Benito Bethencourt
2017-08-09 13:43 ` Agustin Benito Bethencourt [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=598B116B.3020904@codethink.co.uk \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.