linux-kernel - RE: [PATCH 12/60] microblaze_v4: Generic dts file for platforms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Jul 2008 16:21:42 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
Cc:	John Williams <john.williams@...alogix.com>,
	grant.likely@...retlab.ca, linux-arch@...r.kernel.org,
	Michal Simek <monstr@...str.eu>, vapier.adi@...il.com,
	arnd@...db.de, matthew@....cx, microblaze-uclinux@...e.uq.edu.au,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	will.newton@...il.com, hpa@...or.com, John Linn <linnj@...inx.com>,
	monstr@...nam.cz, drepper@...hat.com, alan@...rguk.ukuu.org.uk
Subject: RE: [PATCH 12/60] microblaze_v4: Generic dts file for platforms


> As for the copyright, I haven't been able to find much information on
> whether or not generated files are even copyrightable.  One might
> argue that they
> don't have sufficient 'creative value' to be copyrightable.  Or
> arguably, they are as copyrightable by the generator author as by the
> author or the .mhs file.
> I admit in this case, I've followed the safe route by claiming a
> copyright, which at least at Xilinx has significant precedent.

Also, thinking about your idea of sticking bits in BRAM etc...

what would be nice would be the ability to "merge" trees. We've been
talking about that multiple times, it would be useful at several levels:

 - We could provide pre-made DTs for known CPUs (ie, 440GP, 440GX,
405EX, ...)
 - Boards can then include that, and then "override" some properties
(clocks, PHY wiring, ...)
 - That could be done at the binary level too so that the BRAM contains
on "overlay" on top of the base ref. platform device-tree that comes
with the kernel for example.

This is slightly different between doing that in the .dts source via
some kind of #include vs. doing that by merging blobs but we could make
it be essentially be the same internally: The #include generates a blob
that is then "merged in".

Just random thoughts...

Ben.
 

--
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/