Hello Pavel, Am 19.05.2013 21:06, schrieb Pavel Pisa: > On Sunday 19 May 2013 20:23:55 Andreas Färber wrote: >> Am 18.05.2013 20:24, schrieb Rempel, Cynthia: >>>>> The RTEMS development community is considering having a Google Summer >>>>> of Code student test LinCAN on a simulated RTEMS target board using >>>>> QEMU, and have some questions: >>>>> >>>>> 1. What guidelines should the student follow when writing the device > >>>>> simulation, so the device simulation will be "upstreamed"/accepted by >>>>> the QEMU project? >>>>> 2. Is there additional documentation on how to write a device >>>>> simulation? [...] >>> Would following the guidance in: >>> http://lists.gnu.org/archive/html/qemu-devel/2011-07/msg00842.html >>> increase the probability the device simulation would be committed to >>> qemu? >> >> Unfortunately that is out of date as far as the code goes (QOM is our >> successor to qdev), but it might serve as a good starting point. [...] > 1) I think that for Linux the best option is to implement that as simple > device > -device can-kvasser-pcican-q > or > -device can,model=kvasser-pcican-q [snip]
While using a model property is not wrong per se, "can" seems too generic as type name, since it needs to inherit from a particular base class such as PCIDevice. QOM types can be made abstract to share code between device implementations to the same effect, e.g. PCIHostState. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg