[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1423613998.2713.16.camel@aoeu.buserror.net>
Date:	Tue, 10 Feb 2015 18:19:58 -0600
From:	Scott Wood <scottwood@...escale.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Ingo Molnar <mingo@...nel.org>,
	Tom Huynh <tom.huynh@...escale.com>,
	"Peter Zijlstra" <peterz@...radead.org>,
	<linuxppc-dev@...ts.ozlabs.org>, <acme@...nel.org>,
	<linux-kernel@...r.kernel.org>, <paulus@...ba.org>,
	"Jiri Olsa" <jolsa@...hat.com>, <mingo@...hat.com>
Subject: Re: [PATCH 1/3] perf/e6500: Make event translations available in
 sysfs
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. CPU event lists
> are data sheets, so are like firmware. 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?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
