All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/9 v3][PULL] Hob: bitbake related changes
Date: Fri, 13 Jan 2012 16:30:34 +0800	[thread overview]
Message-ID: <cover.1326442655.git.dongxiao.xu@intel.com> (raw)

Hi Richard,

This is the third pull request for Hob bitbake related changes.

Please help to review and pull.

Changes from v2:
1. Fix parameter checking issue on --bind and --server-only.
2. Add a new command triggerEvent(), which enables the client to request triggering specific event from bitbake server.
3. Add a specific event 'RequestPackageInfo' to get available package information.
4. Change the way to get the CPU information on server side.

Thanks,
Dongxiao

The following changes since commit 9d8f45407c67ed0d3c4f820cf646de3c385067c7:
  Lianhao Lu (1):
        bitbake: Automatically start local PR service.

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib dxu4/hob-bitbake-changes-v3
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/hob-bitbake-changes-v3

Dongxiao Xu (7):
  cache: Use configuration's hash value to validate cache
  command.py: add resolve option for generateTargetsTree API
  event.py: Add new events RequestPackageInfo and PackageInfo
  bitbake: add -B option to bind with interface
  bitbake: Add client socket info for BitBakeServerConnection
  command.py: Add a new API triggerEvent()
  runqueue: fire sceneQueueTaskStarted event when a setscene queue
    starts

Shane Wang (2):
  bitbake: change for adding progress bar in Hob2.
  command.py: add new API to get the cpu count on the server

 bin/bitbake             |   17 +++++++-
 lib/bb/cache.py         |   34 ++++++----------
 lib/bb/command.py       |   23 ++++++++++-
 lib/bb/cooker.py        |   74 ++++++++++++++++++++++++++++--------
 lib/bb/data_smart.py    |   21 ++++++++++
 lib/bb/event.py         |   96 +++++++++++++++++++++++++++++++++++-----------
 lib/bb/runqueue.py      |   10 +++++
 lib/bb/server/xmlrpc.py |   10 ++--
 lib/bb/ui/knotty.py     |    5 ++-
 lib/bb/ui/uievent.py    |    7 ++-
 lib/bb/utils.py         |    4 ++
 11 files changed, 227 insertions(+), 74 deletions(-)




             reply	other threads:[~2012-01-13  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  8:30 Dongxiao Xu [this message]
2012-01-13  8:30 ` [PATCH 1/9] cache: Use configuration's hash value to validate cache Dongxiao Xu
2012-01-16  3:27   ` Lu, Lianhao
2012-01-13  8:30 ` [PATCH 2/9] command.py: add resolve option for generateTargetsTree API Dongxiao Xu
2012-01-13  8:30 ` [PATCH 3/9] event.py: Add new events RequestPackageInfo and PackageInfo Dongxiao Xu
2012-01-13  8:30 ` [PATCH 4/9] bitbake: change for adding progress bar in Hob2 Dongxiao Xu
2012-01-13  8:30 ` [PATCH 5/9] bitbake: add -B option to bind with interface Dongxiao Xu
2012-01-13  8:30 ` [PATCH 6/9] bitbake: Add client socket info for BitBakeServerConnection Dongxiao Xu
2012-01-13  8:30 ` [PATCH 7/9] command.py: add new API to get the cpu count on the server Dongxiao Xu
2012-01-13  8:30 ` [PATCH 8/9] command.py: Add a new API triggerEvent() Dongxiao Xu
2012-01-13  8:30 ` [PATCH 9/9] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts Dongxiao Xu

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=cover.1326442655.git.dongxiao.xu@intel.com \
    --to=dongxiao.xu@intel.com \
    --cc=bitbake-devel@lists.openembedded.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.