If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Cheers,
[1] https://wiki.linaro.org/Platform/Infrastructure/Specs/RemoteDevelopmentBoard... [2] https://blueprints.launchpad.net/lava/+spec/linaro-platforms-o-remote-develo...
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The environment can change over time as these are generally development benchmarks so you can run a baseline first.
-- Michael -- Michael
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
Cheers,
I've got another user story.
As an developer using a remote target to debug I would like to be able to 'see' the video out and hear the audio.
On 4 May 2011 15:15, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
Cheers,
-- Guilherme Salgado https://launchpad.net/~salgado
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories: * A developer benchmarking their latest changes. They can run a baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week * The continuous build recording benchmark results with every build. The environment should always stay the same so that the numbers can be compared
-- Michael
Hmm...actually I was thinking a little more interactive and less batch. Having a remote system that I could do live debug and development one.
On 4 May 2011 15:26, Michael Hope michael.hope@linaro.org wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories: * A developer benchmarking their latest changes. They can run a baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week * The continuous build recording benchmark results with every build. The environment should always stay the same so that the numbers can be compared
-- Michael
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Wed, 2011-05-04 at 15:32 -0500, Zach Pfeffer wrote:
Hmm...actually I was thinking a little more interactive and less batch. Having a remote system that I could do live debug and development one.
That's one of the user stories on the wiki page.
On 4 May 2011 15:26, Michael Hope michael.hope@linaro.org wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories:
- A developer benchmarking their latest changes. They can run a
baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week
- The continuous build recording benchmark results with every build.
The environment should always stay the same so that the numbers can be compared
-- Michael
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hmm... I took a look at:
https://wiki.linaro.org/Platform/Infrastructure/Specs/RemoteDevelopmentBoard...
..and there nothing about multimedia live debug.
-Zach
On 4 May 2011 15:43, Guilherme Salgado guilherme.salgado@linaro.org wrote:
On Wed, 2011-05-04 at 15:32 -0500, Zach Pfeffer wrote:
Hmm...actually I was thinking a little more interactive and less batch. Having a remote system that I could do live debug and development one.
That's one of the user stories on the wiki page.
On 4 May 2011 15:26, Michael Hope michael.hope@linaro.org wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories: * A developer benchmarking their latest changes. They can run a baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week * The continuous build recording benchmark results with every build. The environment should always stay the same so that the numbers can be compared
-- Michael
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
-- Guilherme Salgado https://launchpad.net/~salgado
On Wed, 2011-05-04 at 15:49 -0500, Zach Pfeffer wrote:
Hmm... I took a look at:
https://wiki.linaro.org/Platform/Infrastructure/Specs/RemoteDevelopmentBoard...
..and there nothing about multimedia live debug.
I meant the bit about live debug and development, which is what you mentioned in your previous message. The one there is not specific to multimedia, but we can either change it or add one that is.
On 4 May 2011 15:43, Guilherme Salgado guilherme.salgado@linaro.org wrote:
On Wed, 2011-05-04 at 15:32 -0500, Zach Pfeffer wrote:
Hmm...actually I was thinking a little more interactive and less batch. Having a remote system that I could do live debug and development one.
That's one of the user stories on the wiki page.
On 4 May 2011 15:26, Michael Hope michael.hope@linaro.org wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote: > If you do, I need to know more about how you'd like to use them, to make > sure we provide something that is suitable to everyone. > > At this point I'm interested in drafting some user stories so if you > have any, please do add them to the RemoteDevelopmentBoards[1] wiki > page. Also, if you'd like to participate in the discussion at LDS, don't > forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories:
- A developer benchmarking their latest changes. They can run a
baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week
- The continuous build recording benchmark results with every build.
The environment should always stay the same so that the numbers can be compared
-- Michael
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
-- Guilherme Salgado https://launchpad.net/~salgado
I think the email thread crossed at some point. Anyway the user story could be:
As a developer I want a target that I can interactively control and see graphical/video output and hear audio output, so that I can develop multimedia features.
-Zach
On 4 May 2011 16:02, Guilherme Salgado guilherme.salgado@linaro.org wrote:
On Wed, 2011-05-04 at 15:49 -0500, Zach Pfeffer wrote:
Hmm... I took a look at:
https://wiki.linaro.org/Platform/Infrastructure/Specs/RemoteDevelopmentBoard...
..and there nothing about multimedia live debug.
I meant the bit about live debug and development, which is what you mentioned in your previous message. The one there is not specific to multimedia, but we can either change it or add one that is.
On 4 May 2011 15:43, Guilherme Salgado guilherme.salgado@linaro.org wrote:
On Wed, 2011-05-04 at 15:32 -0500, Zach Pfeffer wrote:
Hmm...actually I was thinking a little more interactive and less batch. Having a remote system that I could do live debug and development one.
That's one of the user stories on the wiki page.
On 4 May 2011 15:26, Michael Hope michael.hope@linaro.org wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote: > On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado > guilherme.salgado@linaro.org wrote: > > If you do, I need to know more about how you'd like to use them, to make > > sure we provide something that is suitable to everyone. > > > > At this point I'm interested in drafting some user stories so if you > > have any, please do add them to the RemoteDevelopmentBoards[1] wiki > > page. Also, if you'd like to participate in the discussion at LDS, don't > > forget to subscribe to the blueprint[2] on Launchpad. > > Hi Guilherme. We currently have a Versatile Express and three > PandaBoards in the London data centre: > https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware > > There's also a bunch of hardware in my home office that is slowly > being replaced by the data centre boxes. > > These are set up as porter boxes. Toolchain people are a bit unique > as we're very much an end user: a board which is reliable and > consistent is more important than the latest and greatest. They're > used for building GCC (~5 hours), testing it (~7 hours), building > packages, debugging, and all the usuals. > > One tricky thing is benchmarking. If you run a benchmark you want the > same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
> environment can change over time as these are generally development > benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories: * A developer benchmarking their latest changes. They can run a baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week * The continuous build recording benchmark results with every build. The environment should always stay the same so that the numbers can be compared
-- Michael
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
-- Guilherme Salgado https://launchpad.net/~salgado
-- Guilherme Salgado https://launchpad.net/~salgado
On Thu, 2011-05-05 at 08:26 +1200, Michael Hope wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories:
- A developer benchmarking their latest changes. They can run a
baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week
Ok, I understand it now, although I can't think of a way to write this nicely using the 'As <role> I want to <perform task> so that <value it brings>' format. Maybe
As a Toolchain engineer, I want to have a system with a stable environment allocated to me for a week so that I can benchmark the toolchain with my changes against a baseline.
?
- The continuous build recording benchmark results with every build.
The environment should always stay the same so that the numbers can be compared
How does
As a Toolchain engineer, I want to continuously build the toolchain against a stable environment and record the benchmark results, so that they can be compared.
Sound as a user story for the above, using our preferred format?
On Thu, May 5, 2011 at 8:55 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
On Thu, 2011-05-05 at 08:26 +1200, Michael Hope wrote:
On Thu, May 5, 2011 at 8:15 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Michael,
On Thu, 2011-05-05 at 03:12 +1200, Michael Hope wrote:
On Wed, May 4, 2011 at 7:50 AM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Hi Guilherme. We currently have a Versatile Express and three PandaBoards in the London data centre: https://wiki.linaro.org/WorkingGroups/ToolChain/Hardware
There's also a bunch of hardware in my home office that is slowly being replaced by the data centre boxes.
These are set up as porter boxes. Toolchain people are a bit unique as we're very much an end user: a board which is reliable and consistent is more important than the latest and greatest. They're used for building GCC (~5 hours), testing it (~7 hours), building packages, debugging, and all the usuals.
One tricky thing is benchmarking. If you run a benchmark you want the same environment as last time and some type of exclusive access. The
I've added a user story with this requirement.
environment can change over time as these are generally development benchmarks so you can run a baseline first.
Do you mean that when the environment changes you want to run the baseline benchmark against the old environment?
There's two stories: * A developer benchmarking their latest changes. They can run a baseline, bring in the change, then run to show the improvement. The environment should stay the same over that week
Ok, I understand it now, although I can't think of a way to write this nicely using the 'As <role> I want to <perform task> so that <value it brings>' format. Maybe
As a Toolchain engineer, I want to have a system with a stable environment allocated to me for a week so that I can benchmark the toolchain with my changes against a baseline.
?
* The continuous build recording benchmark results with every build. The environment should always stay the same so that the numbers can be compared
How does
As a Toolchain engineer, I want to continuously build the toolchain against a stable environment and record the benchmark results, so that they can be compared.
Sound as a user story for the above, using our preferred format?
Change 'stable' for 'consistent'. Sounds good.
-- Michael
Its kind of an aside, but I find the remote power supplies from Synaccess really nice to use, especially for remote debugging.
-Zach
On 3 May 2011 14:50, Guilherme Salgado guilherme.salgado@linaro.org wrote:
If you do, I need to know more about how you'd like to use them, to make sure we provide something that is suitable to everyone.
At this point I'm interested in drafting some user stories so if you have any, please do add them to the RemoteDevelopmentBoards[1] wiki page. Also, if you'd like to participate in the discussion at LDS, don't forget to subscribe to the blueprint[2] on Launchpad.
Cheers,
[1] https://wiki.linaro.org/Platform/Infrastructure/Specs/RemoteDevelopmentBoard... [2] https://blueprints.launchpad.net/lava/+spec/linaro-platforms-o-remote-develo...
-- Guilherme Salgado https://launchpad.net/~salgado
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hey
This is not a specific use case, but more of a proposed design feature: Linaro might sometimes offer the possibility to run/build something on boards to untrusted third parties. For instance building a package, running a testsuite, or doing a test build of a proposed GCC branch or an Android image. It might be worth considering some security sandboxing for some of the boards for some of the use cases.
Cheers,
-
Guilherme Salgado -
Loïc Minier -
Michael Hope -
Zach Pfeffer