[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] VxWorks 5.5.1 on qemu powerpc

From: Alexander Graf
Subject: Re: [Qemu-ppc] VxWorks 5.5.1 on qemu powerpc
Date: Tue, 01 Apr 2014 15:16:38 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130910 Thunderbird/17.0.9

On 04/01/2014 03:12 PM, Fabien Chouteau wrote:
On 04/01/2014 02:14 PM, Alexander Graf wrote:
On 04/01/2014 12:27 PM, Fabien Chouteau wrote:
On 04/01/2014 12:07 PM, Alexander Graf wrote:
On 04/01/2014 11:54 AM, Fabien Chouteau wrote:
Hi Maxime, Alex,

On 04/01/2014 11:16 AM, Alexander Graf wrote:
On 04/01/2014 11:04 AM, FOURNIER Maxime wrote:
Did someone managed to make this OS boot on qemu-powerpc ?
Yes, Fabien Chouteau had VxWorks running on e500 IIRC.

We actually have many products for vxWorks now, vxWorks6 and
vxworks6-cert on ppc604 and e500v2, vx653 on e500v2. No vxworks5 for the

Did we miss something or did we make wrong assumptions ?

   From experience I can tell you that vxWorks will not work out of the box
on QEMU. First because QEMU doesn't emulate the boards supported by
vxWorks, and also because QEMU is focused on Linux.

There's different way to deal with this, you can either create a custom
BSP in vxWorks that support one of QEMU's board, or you can support a
new board in QEMU (that's what we do).
Hrm, any plans to move these upstream? :)

Yes of course, we want them upstream eventually. During the last few
years you've seen some of our patches (booke timers and eTSEC for
examples). For boards it think it's not that easy, what would you say
about a complete board that you cannot test because only vxWorks runs on
As long as I have a (vxworks) image I can verify with that it still works 
that's a perfectly desirable thing to have.

That's precisely the problem, I can't give you a vxWorks image...

So why don't we start off with a platform that doesn't need vxworks then? You seem to have SBC834x board support in your tree. That one does seem to be available in Linux:



reply via email to

[Prev in Thread] Current Thread [Next in Thread]