On 13 July 2016 at 16:30, goremykin <goremy...@ispras.ru> wrote: > We are developing automatic boards and device templates creation tools. It > would be better if I get DeviceClass hierarchy without QEMU running, but > it's unachievable due to implementation of QEMU device registration. > External Python script is bad because it requires connection with QEMU. This > script should establish the connection and follow the QMP protocol. In my > opinion, it's quite complicated way and brings a lot of overhead. Unlike > QMP/HMP command dt-printf option terminates before creation of board. It > requires only start QEMU with this option.
The thing is, we already have a more-or-less standard setup for "how do you start QEMU and interrogate it for details of its config", and that is to use QMP. I'm not sure "it happens to be more convenient for my specific use case" really justifies having this particular kind of query be done with a different mechanism. thanks -- PMM