[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d3f23370806291702g4344a2f9lb62f85cbb475fca4@mail.gmail.com>
Date: Mon, 30 Jun 2008 10:02:21 +1000
From: "John Williams" <john.williams@...alogix.com>
To: "Grant Likely" <grant.likely@...retlab.ca>
Cc: monstr@...nam.cz, linux-kernel@...r.kernel.org, arnd@...db.de,
linux-arch@...r.kernel.org, stephen.neuendorffer@...inx.com,
John.Linn@...inx.com, matthew@....cx, will.newton@...il.com,
drepper@...hat.com, microblaze-uclinux@...e.uq.edu.au,
linuxppc-dev@...abs.org, vapier.adi@...il.com,
alan@...rguk.ukuu.org.uk, hpa@...or.com,
"Michal Simek" <monstr@...str.eu>
Subject: Re: [PATCH 12/60] microblaze_v4: Generic dts file for platforms
On Sat, Jun 28, 2008 at 3:49 PM, Grant Likely <grant.likely@...retlab.ca> wrote:
> On Thu, Jun 26, 2008 at 5:29 AM, <monstr@...nam.cz> wrote:
>> From: Michal Simek <monstr@...str.eu>
>> arch/microblaze/platform/generic/system.dts | 300 +++++++++++++++++++++++++++
> Since this is a generated file, and entirely bitstream specific, does
> it make sense to include it in the kernel tree? If it does, then is
> it produced from one of the Xilinx reference designs? Can you add
> documentation to the header that specifies exactly which design
> version this .dts is for?
I think there's value in having a generic DTS as an example or
template, even if it doesn't correspond to any specific machine.
Agreed a comment block explaining this is valuable.
I'd almost oppose any attempt to include a standard DTS for things
like ML401 boards etc - they are just misleading. Unless we do MD5
hashes on MHS files, and use them as the filenames, any attempt to
define a standard platform will just fail and confuse people. Better
to show them how to generate the DTS for their system.
>> +/*
>> + * (C) Copyright 2007-2008 Xilinx, Inc.
>> + * (C) Copyright 2007-2008 Michal Simek
>> + *
>> + * Michal SIMEK <monstr@...str.eu>
>
> If this is a generated file, then is this copyright notice even appropriate?
I agree. I think Michal is just copying Xilinx's habit of putting
copyright headers in generated files, and it's one that we should stop
now.
Regards,
John
--
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