Re: [Qemu-devel] CMSIS SVD based peripheral definitions

> On 17 Jan 2017, at 13:09, Peter Maydell wrote: > > losing the license info and attribution inside the SVD files there is no license info or attribution. the files themselves were created by the silicon vendors, but are distributed by ARM, inside the CMSIS Packs.

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

On 17 January 2017 at 10:42, Dr. David Alan Gilbert wrote: > Being able to read a machine description from a file at run time > sounds reasonable, as do tools to manipulate those descriptions. > I don't see why such a description file would be any different > from a firmware

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

* Peter Maydell (peter.mayd...@linaro.org) wrote: > On 9 January 2017 at 17:47, Liviu Ionescu wrote: > > I can't dispute this, but does't the GPLv2 requirements apply to > > the qemu executable only? my JSON files are not compiled into the > > binary, but are data files, read by

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

> On 16 Jan 2017, at 21:23, Peter Maydell wrote: > > doing that is somewhere between "grey area" and > "GPL violation". too bad for GPL. :-( the fact is that I'll continue to improve support for Cortex-M in my branch of QEMU, and the SVD definitions are part of it.

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

On 16 January 2017 at 18:59, Liviu Ionescu wrote: > >> On 16 Jan 2017, at 20:17, Peter Maydell wrote: >> >> "reading data that shipped with QEMU >> and where QEMU won't work at all without it" (the data files >> are clearly part of the program as a

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

> On 16 Jan 2017, at 20:17, Peter Maydell wrote: > > "reading data that shipped with QEMU > and where QEMU won't work at all without it" (the data files > are clearly part of the program as a whole and the GPL > applies to them even if they don't happen to be

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

On 9 January 2017 at 17:47, Liviu Ionescu wrote: > I can't dispute this, but does't the GPLv2 requirements apply to > the qemu executable only? my JSON files are not compiled into the > binary, but are data files, read by the executable when required. > and anyway, the original

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

> On 9 Jan 2017, at 19:31, Peter Maydell wrote: > > FSF's view is that Apache 2.0 is not compatible with GPLv2: I can't dispute this, but does't the GPLv2 requirements apply to the qemu executable only? my JSON files are not compiled into the binary, but are data

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

On 9 January 2017 at 16:51, Liviu Ionescu wrote: >> On 9 Jan 2017, at 18:16, Peter Maydell wrote: >> The obvious issue that comes to mind >> is licensing, though -- what licenses are the SVD files under, >> and would those be compatible with QEMU's

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

> On 9 Jan 2017, at 18:16, Peter Maydell wrote: > > On 28 December 2016 at 18:49, Liviu Ionescu wrote: >> The latest release of GNU ARM Eclipse QEMU (2.8.0-20161227) introduced >> a new technology for implementing peripherals, based on standard >>

Re: [Qemu-devel] CMSIS SVD based peripheral definitions

On 28 December 2016 at 18:49, Liviu Ionescu wrote: > The latest release of GNU ARM Eclipse QEMU (2.8.0-20161227) introduced > a new technology for implementing peripherals, based on standard > CMSIS SVD definitions > (http://www.keil.com/pack/doc/CMSIS/SVD/html/index.html). > >

[Qemu-devel] CMSIS SVD based peripheral definitions

CMSIS SVD - The latest release of GNU ARM Eclipse QEMU (2.8.0-20161227) introduced a new technology for implementing peripherals, based on standard CMSIS SVD definitions (http://www.keil.com/pack/doc/CMSIS/SVD/html/index.html). The SVD files are large XML files produced by the silicon