openbmc qemu vs Cedric qemu is different

C├ędric Le Goater clg at
Fri Jul 15 19:27:44 AEST 2016

On 07/15/2016 03:42 AM, Joel Stanley wrote:
> Hello Chris,
> On Thu, 2016-07-14 at 13:27 -0500, Chris Austen wrote:
>> Hi Joel, 
>> last night you indicated that our openbmc/qemu had enough for
>> networking the palmetto-bmc. I don't think that is 100% true. I
>> believe Cedric's repo has some additional changes that should be
>> integrated back in to openbmc/qemu. Hopefully you two can figure out
>> what commits are needed to get us back to one working repo. 

Here is a quick summary of the differences, my branch compared to 

* qemu base 

  closer to mainline.

* smc

  adds some minor code clean ups (merged in mainline now)

* vic

  misses some nice-to-have properties. 

* watchdog

  adds a fix for uboot (linux still needs fixing)
* timer

  in sync
* scu

  adds minor fixes

* ast2500

  adds more support (can boot uboot with the vbar hack)

* ftgmac100

  adds a new 'aspeed' property to change the end of ring buffer bit 
  in the network adpater model for aspeed socs. This is needed for 
  the linux 4.6 ftgmac100 network driver which uses the 'correct'
  bits. the ast2500 flash images will be fine but there is a problem 
  for older ast2400 flash images which have a 4.4 kernel using the 
  old bits definition. 

  We could need to make the 'aspeed' property configurable from the 
  qemu command line to support these. to be discussed 

So, qemu should behave the same in both branches. 

Support for ast2400/linux 4.6 is broken in my branch and a quick 
would be :

That will drop support for the images with a 4.4 kernel. Can we ?

qemu-2.7-rc0 will have some more of our code merged. we will update
the openbmc/qemu branch at that time. 

I am mostly disconnected next week, so expect latency in the answers :)



More information about the openbmc mailing list