All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: Michael_E_Brown@Dell.com, diego.sueiro@gmail.com, sbabic@denx.de
Cc: yocto@yoctoproject.org
Subject: Re: Deploying Yocto build images
Date: Thu, 21 Nov 2013 19:49:40 +0100	[thread overview]
Message-ID: <528E55C4.3040805@denx.de> (raw)
In-Reply-To: <DB6E482E89290547898851B8CC9D8110012FAE31A0@AUSX7MCPS302.AMER.DELL.COM>

Hi Michael,

On 21/11/2013 19:20, Michael_E_Brown@Dell.com wrote:
> Thanks for posting this. It’s very timely for a project I am in the
> initial stages of designing. I have looked over the docs and some of the
> code, and am interested in using this.
> 
>  
> 
> I would make a couple suggestions:
> 

Thanks !

> 1)      As you mention, documentation is important. Unless this is very
> well documented, it’s difficult for other people to take up and use
> effectively, or to advocate for its use in a group

I know, and I am understand there are a lot of things that I have not
explained. Documentation is first priority.

> 2)      Progress indications: it’s going to be fairly important to build
> in some way to notify other process about the state of the update.
> A
> flexible framework for sharing progress would be very much appreciated.

There is an interface using Unix Domain Socket to communicate with the
installer. There is only a couple of implemented messages (start
installer - get status). It is quite rudimentary, but it can be extended.

This interface is also used by the AJAX interface (see in ./www) to
report the current status to the operator's browser when a downloaded is
started from network. Another use case is to output the status on a LCD:
a separate process can ask the installer and render the output for the
operator.

> There are a couple scenarios I have, but the main one is a network
> notification where one device is being updated by another. The updated
> device should be able to signal update progress to the updater device in
> a flexible fashion. I haven’t looked at the code hard enough to see how
> difficult this would be to add.

I think it is should be not very difficult. As I said, there is already
an interface that can be easy extended.

Regards,
Stefano


-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


  reply	other threads:[~2013-11-21 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 12:10 Deploying Yocto build images Stefano Babic
2013-11-21 12:34 ` Diego Sueiro
2013-11-21 13:15   ` Stefano Babic
2013-11-21 18:20   ` Michael_E_Brown
2013-11-21 18:49     ` Stefano Babic [this message]
2013-11-21 15:48 ` Bryan Evenson
2013-11-21 17:08   ` Stefano Babic

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=528E55C4.3040805@denx.de \
    --to=sbabic@denx.de \
    --cc=Michael_E_Brown@Dell.com \
    --cc=diego.sueiro@gmail.com \
    --cc=yocto@yoctoproject.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.