On Thu, 16 Jun 2011 10:21:31 +0800, Spring Zhang
wrote:
Non-text part: multipart/alternative
> On 16 June 2011 08:59, Michael Hudson-Doyle
> wrote:
>
> > On Thu, 16 Jun 2011 02:12:19 +0200, Zygmunt Krynicki <
> > zygmunt.kryni...@linaro.org> wrote:
> > > W dniu 16.06.2011 00:19, Michael Hudson-
On 16 June 2011 08:59, Michael Hudson-Doyle wrote:
> On Thu, 16 Jun 2011 02:12:19 +0200, Zygmunt Krynicki <
> zygmunt.kryni...@linaro.org> wrote:
> > W dniu 16.06.2011 00:19, Michael Hudson-Doyle pisze:
> > >> I created user forum for the dashboard at:
> > >>
> > >> http://fracture.suxx.pl/pro
On Thu, 16 Jun 2011 02:12:19 +0200, Zygmunt Krynicki
wrote:
> W dniu 16.06.2011 00:19, Michael Hudson-Doyle pisze:
> >> I created user forum for the dashboard at:
> >>
> >> http://fracture.suxx.pl/projects/lava-dashboard/boards
>
> > Is there a way I can subscribe via email?
>
> There's a w
W dniu 15.06.2011 22:49, Paul Larson pisze:
But what about where other non-python packages need to be installed for it
to work properly? That was the main thing I was trying to sort out? Does
the recipe have a rule to do this?
For building this knowledge is contained in the source package.
W dniu 16.06.2011 00:19, Michael Hudson-Doyle pisze:
I created user forum for the dashboard at:
http://fracture.suxx.pl/projects/lava-dashboard/boards
Is there a way I can subscribe via email?
There's a watch icon in each thread/forum. AFAIK you will be notified of
changes in the objec
On Wed, 15 Jun 2011 14:01:03 +0200, Zygmunt Krynicki
wrote:
> Hello everyone.
>
> Since a few people started asking me questions about lava dashboard,
> reports and other things I though I we could benefit from sharing this
> knowledge.
>
> I created user forum for the dashboard at:
>
>h
On 06/15/2011 03:49 PM, Joey Stanford wrote:
>> Can you add a section on bots. I know some people are interested in
>> the meeting bot.
>
> I'll punt that to Fathi. He's become the Bot Master :-)
>
> Fathi, can you add something to the bottom? Or create a new sub page under
This page has lots of
> Can you add a section on bots. I know some people are interested in
> the meeting bot.
I'll punt that to Fathi. He's become the Bot Master :-)
Fathi, can you add something to the bottom? Or create a new sub page under
https://wiki.linaro.org/GettingInvolved/IRC/ ?
Thanks,
J
___
Linus (W),
Some more thoughts on pinmux:
== GPIO/pinmux API interactions
I'd like to understand how the gpio and pinmux subsystems are intended
to interact.
Quoting from Documentation/gpio.txt:
Note that requesting a GPIO does NOT cause it to be configured in any
way; it just marks
On Wed, 15 Jun 2011, Joey Stanford wrote:
> Hi,
>
> I spent some more time today fixing IRC channels and it prompted me to
> write-up a wiki page on how to create channels, including the specific
> commands.
>
> https://wiki.linaro.org/GettingInvolved/IRC/channelsetup
Thanks Joey. Great page.
Hi,
I spent some more time today fixing IRC channels and it prompted me to
write-up a wiki page on how to create channels, including the specific
commands.
https://wiki.linaro.org/GettingInvolved/IRC/channelsetup
Team Leads in particular, please have a look and make sure it's understandable.
Th
On Wed, Jun 15, 2011 at 2:56 PM, Zygmunt Krynicki <
zygmunt.kryni...@linaro.org> wrote:
> I was writing it this morning. It actually pulls all of the branches that
> compose lava and gives you an ability to install them in a managed
> virtualenv instance.
>
> Great!
>
> It seems to me,
>> that
W dniu 15.06.2011 20:30, Paul Larson pisze:
So having those requirements my goals were to build a tool that would be
useful for those two tasks:
1) Daily development helper as a sort of CI tool.
2) Monthly release helper
So for purpose 1, if we wanted to use the same tool to make this easy,
>
> So having those requirements my goals were to build a tool that would be
> useful for those two tasks:
> 1) Daily development helper as a sort of CI tool.
> 2) Monthly release helper
>
> So for purpose 1, if we wanted to use the same tool to make this easy,
could we just do something like 'lava
Hi,
I'll go ahead and setup the channel for you.
We have a bunch of side channels today (more than what Fathi
mentioned). I'm a little worried about activity not happening on
#Linaro but that channel can get quite busy.
J
On Wed, Jun 15, 2011 at 11:02 AM, Kurt Taylor wrote:
> I just read Fath
On 15 June 2011 17:02, Kurt Taylor wrote:
> I just read Fathi's email about the new bots. I didn't want to hijack the
> existing thread, but I have been considering setting up a new official
> Linaro irc channel #linaro-multimedia with the meeting bot, etc.
Here's the list of existing/active Lina
I just read Fathi's email about the new bots. I didn't want to hijack the
existing thread, but I have been considering setting up a new official
Linaro irc channel #linaro-multimedia with the meeting bot, etc.
As per discussions with Ilias, I would also like to set up a new service, an
IRC proxy (
On 15 June 2011 15:40, Nicolas Pitre wrote:
> On Wed, 15 Jun 2011, Peter Maydell wrote:
>> if we want to guarantee
>> that QEMU and the kernel work together I think we really
>> need to pretty much freeze the kernel two weeks before
>> QEMU's release date, in order to have a fighting chance
>> at
Guilherme Salgado wrote:
> Is there a mailing list to which valgrind patches are sent? If we have
> one whenever you send a patch to that list with patches@l.o CCed we'll
> be able to detect it's a valgrind patch and move it to the correct
> project.
No, there isn't. Valgrind patch contribution
On Wed, 2011-06-15 at 16:44 +0200, Ulrich Weigand wrote:
> Guilherme Salgado wrote:
> > And there's a form at the bottom which allows them to be moved to the
> > appropriate project. If we're missing a project just let me know and
> > I'll create it.
>
> It looks like there's no project for valgr
Hi,
My apologies, I forgot to say that I had to use
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- KBUILD_DEBARCH=armel \
deb-pkg
which tells it to build the package for armel.
Thanks,
James
On Wed, 15 Jun 2011 17:24:03 +0530, Deepti Kalakeri
wrote:
> Hello James,
>
> I applied the pat
Guilherme Salgado wrote:
> And there's a form at the bottom which allows them to be moved to the
> appropriate project. If we're missing a project just let me know and
> I'll create it.
It looks like there's no project for valgrind; I have two patches
accepted there ...
Mit freundlichen Gruesse
On Wed, 15 Jun 2011, Peter Maydell wrote:
> The underlying cause here is that QEMU's models are not
> tested in any formal way against a specification or
> against a test suite used for validating the hardware.
> The main test is "does it boot Linux?". So it's inevitable
> that new kernel features
Make some functions static as they are no longer out of the scope of
the display code.
Signed-off-by: Daniel Lezcano
---
display.c | 124 ++--
1 files changed, 62 insertions(+), 62 deletions(-)
diff --git a/display.c b/display.c
index 1ba
The keystroke callback could be moved to the display code.
Signed-off-by: Daniel Lezcano
---
display.c| 48 +++-
display.h|8 +---
powerdebug.c | 45 +
3 files changed, 49 insertions(+), 5
We can use a switch here to check the key which was stroke.
Signed-off-by: Daniel Lezcano
---
powerdebug.c | 43 +--
1 files changed, 25 insertions(+), 18 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index fccc08b..0b25860 100644
--- a/powerdeb
The less we have define for pm blocks the easier is to add more pm blocks.
Signed-off-by: Daniel Lezcano
---
display.c| 24 +++-
display.h|2 ++
powerdebug.h |4
3 files changed, 17 insertions(+), 13 deletions(-)
diff --git a/display.c b/display.c
inde
Make some cleanup around the headers.
Signed-off-by: Daniel Lezcano
---
clocks.c |5 +
display.c|4
powerdebug.c |6 +-
powerdebug.h | 24 +---
regulator.c |2 ++
regulator.h |3 +--
6 files changed, 18 insertions(+), 26 deletions(
Remove the specific cases in the mainloop and encapsulate the
display functions.
Signed-off-by: Daniel Lezcano
---
display.c| 56 ++--
display.h|6 ++
powerdebug.c | 26 +-
powerdebug.h |2 --
4 f
Let's create some ops to be registered by the pm blocks to the display.
Signed-off-by: Daniel Lezcano
---
clocks.c| 53 +++--
display.c | 11 +++
display.h |7 ++-
regulator.c |8
sensor.c|8
Remove unused parameter for the keystroke callback.
Signed-off-by: Daniel Lezcano
---
powerdebug.c | 28 ++--
1 files changed, 10 insertions(+), 18 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index 28b23b4..fccc08b 100644
--- a/powerdebug.c
+++ b/powerdebug.c
Create a pad for each pm blocks, so we can use the same code
to scroll the values on the display.
Signed-off-by: Daniel Lezcano
---
display.c | 141 ++---
1 files changed, 41 insertions(+), 100 deletions(-)
diff --git a/display.c b/displa
Signed-off-by: Daniel Lezcano
---
powerdebug.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index 5109c90..5ff675d 100644
--- a/powerdebug.c
+++ b/powerdebug.c
@@ -192,9 +192,6 @@ int keystroke_callback(bool *enter_hit, struct
powerdebug_
Make the code consistent with the clocks and use the tree to
build the regulators.
Signed-off-by: Daniel Lezcano
---
display.c| 50 ++
powerdebug.c | 50 +
powerdebug.h |4 +-
regulator.c | 322 ++
regulator.h
We don't have anymore a specific case for each pm block as we use
some ops now.
Signed-off-by: Daniel Lezcano
---
powerdebug.c | 12
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index 5ff675d..28b23b4 100644
--- a/powerdebug.c
+++ b/po
Remove some corner cases for the footer display we have the same
display feature for all the pm blocks.
Signed-off-by: Daniel Lezcano
---
display.c| 104 +++--
display.h|2 +-
powerdebug.c |9 ++---
powerdebug.h | 20 ++--
Signed-off-by: Daniel Lezcano
---
display.c | 36 ++--
display.h | 15 +++
2 files changed, 41 insertions(+), 10 deletions(-)
diff --git a/display.c b/display.c
index d55d748..92fc02a 100644
--- a/display.c
+++ b/display.c
@@ -218,6 +218,22 @@ int
Signed-off-by: Daniel Lezcano
---
display.c | 16 +---
1 files changed, 1 insertions(+), 15 deletions(-)
diff --git a/display.c b/display.c
index 5fd14c7..1ba71e5 100644
--- a/display.c
+++ b/display.c
@@ -269,27 +269,15 @@ int display_refresh_pad(int win)
0
That allows to keep track of the different selections from the different
windows.
Signed-off-by: Daniel Lezcano
---
clocks.c | 20 ++--
display.c| 96 --
powerdebug.c |4 +-
powerdebug.h | 18 +-
4 files ch
Remove the old "findparent" code.
Signed-off-by: Daniel Lezcano
---
powerdebug.c | 60 +
1 files changed, 6 insertions(+), 54 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index f73aafe..5109c90 100644
--- a/powerdebug.c
+++ b/po
Use the tree to build a sensor tree and make the code consistent
with the other pm blocks.
Signed-off-by: Daniel Lezcano
---
powerdebug.c |7 ++-
powerdebug.h |2 +-
sensor.c | 261 --
3 files changed, 150 insertions(+), 120 de
Signed-off-by: Daniel Lezcano
---
clocks.c |4 ++--
clocks.h |4 ++--
powerdebug.c |5 +++--
sensor.h |3 +++
4 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/clocks.c b/clocks.c
index c86a39e..db219d8 100644
--- a/clocks.c
+++ b/clocks.c
@@ -332,7 +332,
Signed-off-by: Daniel Lezcano
---
powerdebug.c | 30 --
1 files changed, 8 insertions(+), 22 deletions(-)
diff --git a/powerdebug.c b/powerdebug.c
index e702011..f73aafe 100644
--- a/powerdebug.c
+++ b/powerdebug.c
@@ -154,7 +154,7 @@ int getoptions(int argc, char *
Add the sensor display.
Signed-off-by: Daniel Lezcano
---
display.c|6 +-
powerdebug.c | 33 +
sensor.c | 56
3 files changed, 66 insertions(+), 29 deletions(-)
diff --git a/display.c b/
Signed-off-by: Daniel Lezcano
---
Makefile |2 +-
clocks.c | 62 +-
utils.c | 55 +++
utils.h | 22 ++
4 files changed, 79 insertions(+), 62 deletions(-)
Hi folks,
http://patches.linaro.org/ went live yesterday and we need your help to
set it up and get accurate metrics. It should take only a few minutes!
The first thing we need is the HTTP URL for the upstream master branch
of every project on the front page -- I'll take a git:// URL if that's
al
Hello everyone.
Since a few people started asking me questions about lava dashboard,
reports and other things I though I we could benefit from sharing this
knowledge.
I created user forum for the dashboard at:
http://fracture.suxx.pl/projects/lava-dashboard/boards
Please go there and post
Hello James,
I applied the patch you provided and tried the steps you mentioned. I am
using omap2plus_defconfig, but the make deb-pkg fails with the following
error:
dpkg-gencontrol: error: current host architecture 'armel' does not appear in
package's architecture list ()
make[1]: *** [deb-pkg]
Hi fellow ARM fans,
Linaro Developer Platform team organises every week (Wednesday 14:00 -
18:00 UTC) an ARM porting Jam. The idea is to gather all developers together to
fix userspace portability issues across the board. The list of bugs
being worked on is at launchpad:
https://bugs.launchpad.ne
On 15 June 2011 11:14, Alexander Sack wrote:
> Anyway, I really hope this is unlikely to happen for now
[I should start this email with a disclaimer: this isn't
intended to be finger pointing, just an explanation of why
we should expect and plan for QEMU breakage rather than
hoping it is unlikely
On Mon, Jun 13, 2011 at 2:41 PM, Paul Sokolovsky
wrote:
>
> So, where do we go from here? Unless there's tip export feature
> directly out of remote repo for bzr (bzr export seem to requite local
> working copy), we'd need to play mirror, this time bzr, again %).
For the reason that it is trivial
On Wed, Jun 15, 2011 at 12:00 PM, Peter Maydell
wrote:
> On 15 June 2011 00:47, Nicolas Pitre wrote:
>> On Tue, 14 Jun 2011, Mounir Bsaibes wrote:
>>> Does the kernel have to boot under the latest QEMU release?
>>
>> For device tree support I would think so. An older Linaro release for
>> U-Boot
On 15 June 2011 00:47, Nicolas Pitre wrote:
> On Tue, 14 Jun 2011, Mounir Bsaibes wrote:
>> Does the kernel have to boot under the latest QEMU release?
>
> For device tree support I would think so. An older Linaro release for
> U-Boot should be fine too. Maybe John Crigby could provide more deta
Hi Dajun,
I didn't track the patch series you sent out. Did you receive any review
and feedback and got them all addressed?
Would you please send the updated version if available? And Cc linaro-dev
is more than welcome. We have people eager to get this upstreamed.
Thanks
- eric
On Sun, Jun 12,
Linus Walleij wrote at Tuesday, June 14, 2011 8:26 AM:
> On Tue, Jun 14, 2011 at 1:28 AM, Stephen Warren wrote:
>
> > I'm a little confused by this version.
>
> Sorry, I'll try to clarify.
>
> > In particular:
> >
> > * I don't see some changes that I thought we'd agreed upon during earlier
> >
Just FYI-- for those interested in the ARM porting effort in
libjpeg-turbo, the iOS and Android camps reached a resolution, and the
patches they agreed upon have been committed to trunk. Independent
evaluation by any of you who have an interest in this would be very much
appreciated.
On 6/14/11
Hi Grant,
On Mon, Jun 13, 2011 at 07:32:15AM -0600, Grant Likely wrote:
[...]
> +Linux board support code calls of_platform_populate(NULL, NULL, NULL)
> +to kick of discovery of devices at the root of the tree. The
> +parameters are all NULL because when starting from the root of the
> +tree, the
57 matches
Mail list logo
