* Scott Wood <scottw...@freescale.com> wrote:
> On Mon, 2015-02-09 at 21:40 +0100, Andi Kleen wrote:
> > > I'll NAK any external 'download area' (and I told that Andi
> > > before): tools/perf/event-tables/ or so is a good enough
> > > 'download area' with fast enough update cycles.
> >
> > The proposal was to put it on kernel.org, similar to how
> > external firmware blobs are distributed. [...]
Fortunately perf is not an external firmware blob ...
> > [...] CPU event lists are data sheets, so are like
> > firmware. [...]
What an absolute, idiotic, nonsense argument!
CPU event lists are human readable descriptions for events.
If they aren't then they have no place in tooling.
Treating them like firmware is as backwards as it gets.
> > [...] They do not follow the normal kernel code
> > licenses. They are not source code. They cannot be
> > reviewed in the normal way.
>
> How is it different from describing registers and bits in
> driver header files? What does it mean to talk about a
> license on information, rather than the expression of
> information?
Andi is making idiotic arguments, instead of implementing
the technically sane solution.
Thanks,
Ingo
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
