All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Konstantinos Papagiannopoulos <hello@konputer.net>,
	yocto@yoctoproject.org, Jim Kosem <jim@halfman.com>
Subject: Re: Web HOB planning discussion
Date: Wed, 13 Jun 2012 17:34:37 +0100	[thread overview]
Message-ID: <10306994.IBNakgMNPp@helios> (raw)
In-Reply-To: <4FD8BAF0.5090405@linux.intel.com>

On Wednesday 13 June 2012 09:08:16 Darren Hart wrote:
> The group/project concept is very interesting.
> 
> One thing I didn't see in the video, and perhaps you just couldn't cover
> it, is how do you specify settings in local.conf? LICENSE settings for
> example?

Some of these settings should be available under "Settings" which isn't really 
covered in the video other than the button being at the top right. I'm not 
sure the current design can cover every possible setting you can set via 
local.conf, but it should cover the basics (the settings currently configurable 
in Hob v2 that make sense in the context of a central server - i.e. it may be 
that the admin is the one that sets parallel make / threads dependent on the 
hardware resources they have assigned). We can always add additional settings 
in the future where they make sense.
 
> As for the image writer, it really should not be limited to USB devices.

Indeed, but it's worth noting that the whole "deploy" section is a little 
tricky anyway. In the design it's shown within the web interface but I'm not 
sure how it can work there, given that it requires root privileges on the 
client machine to write an image to the media. It's more likely that this will 
be implemented in the form of an executable that is available for download 
from the web interface, but we won't know for sure until it reaches 
implementation. (I've talked to Jim about this already, what is there in the 
design is a stand-in for the fact that the capability should be there in some 
form, eventually at least.)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-06-13 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0FABE48C74734648B69F641A84298A59190B8A98@IRSMSX104.ger.corp.intel.com>
     [not found] ` <0FABE48C74734648B69F641A84298A59190B9CF9@IRSMSX104.ger.corp.intel.com>
2012-06-11 14:20   ` Web HOB planning discussion Jim Kosem
2012-06-13 16:08     ` Darren Hart
2012-06-13 16:34       ` Paul Eggleton [this message]
2012-06-13 17:39     ` Stewart, David C
2012-06-13 18:00       ` Osier-mixon, Jeffrey
2012-06-14  8:37         ` Barros Pena, Belen
2012-06-21  5:19           ` 答复: " Lv, XiaotongX
2012-06-21 10:44             ` Barros Pena, Belen

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=10306994.IBNakgMNPp@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=hello@konputer.net \
    --cc=jim@halfman.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.