On 22/06/16 09:57, Darshit Shah wrote:
On 06/22, Sebastian Huber wrote:
On 21/06/16 07:29, Sebastian Huber wrote:
On 20/06/16 15:40, Darshit Shah wrote:
Hi,
Last week the clock driver for SMP ARM BSPs was fixed which allowed
me to start executing the SMP tests for my GSoC project. However,
On 06/22, Sebastian Huber wrote:
On 21/06/16 07:29, Sebastian Huber wrote:
On 20/06/16 15:40, Darshit Shah wrote:
Hi,
Last week the clock driver for SMP ARM BSPs was fixed which allowed
me to start executing the SMP tests for my GSoC project. However,
today I seem to be stuck with a clock
On 21/06/16 07:29, Sebastian Huber wrote:
On 20/06/16 15:40, Darshit Shah wrote:
Hi,
Last week the clock driver for SMP ARM BSPs was fixed which allowed
me to start executing the SMP tests for my GSoC project. However,
today I seem to be stuck with a clock driver issue again.
When I try t
On 20/06/16 15:40, Darshit Shah wrote:
Hi,
Last week the clock driver for SMP ARM BSPs was fixed which allowed me
to start executing the SMP tests for my GSoC project. However, today I
seem to be stuck with a clock driver issue again.
When I try to execute SMP tests, the tests exit with no
Hi,
Last week the clock driver for SMP ARM BSPs was fixed which allowed me
to start executing the SMP tests for my GSoC project. However, today I
seem to be stuck with a clock driver issue again.
When I try to execute SMP tests, the tests exit with no output and a
exit code of 0. On trying t
