How about using the SPDX licensing method:
Here's an example of its usage in a U-Boot Makefile:
# (C) Copyright 2007 Semihalf
# SPDX-License-Identifier: GPL-2.0+
On Tue Mar 03 07:24, ron minnich wrote:
> We've had this discussion before, many times. I've pointed out many times
> it can be easy, using a form that's now over 20 years old. This is taken
> from linux.
> * * Copyright 1993 United States Government as represented by the
> * Director, National Security Agency.
> * This software may be used and distributed according to the terms
> * of the GNU General Public License, incorporated herein by reference.*
> *it doesn't get much simpler than that. I just wish we could get
> buyin. You're not required to cite the NSA. use your own company.*
> On Mon, Mar 2, 2015 at 10:07 PM Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
> > There's this thing called a copyright notice, which is pretty cool. When
> > coding on 24" monitors or larger, it's this tiny thing that keeps some
> > legal
> > history of a file. The world is perfect and there are no issues!
> > Then FSF comes and teaches us to be in-your-face with a 20+ line copyright
> > notice, and laptops happen. And 14" screens become a long-forgotten glory.
> > Now
> > you have to *BLEEP*ing scroll down every time you open a file just to get
> > to
> > the real content. It becomes so annoying, that I will personally stop
> > giving
> > positive gerrit scores on any CL that introduces such a file.
> > Then we get to situations where we waste all that copyright notice space
> > for
> > one line of code . This madness has to stop.
> > Tell me what the file does, add your (C) line, tell me how you license the
> > file, and move on! Start coding already for *BLEEP*'s sake! Here:
> > /*
> > * On copyright notices: Angry email to coreboot mailing list
> > *
> > * Copyright (C) Some really pissed off guy <angry(a)mad.com>
> > * Licensed under WTFPL, or, at your option, Allah Akbar public license.
> > */
> > There, you've achieved the same thing as that abomination of notice that we
> > need to change whenever some third party moves its headquarters. Now I can
> > open a file and see
> > /*
> > * On the subject of flowers and sunny skies
> > *
> > ...
> > and I immediately know I'm in the wrong place. Be pragmatic! Be practical!
> > Tell me what your file does. Talk about it. Document stuff. It's a much
> > better
> > use of space. I could probably kidnap any of you, torture you asking for
> > your
> > bank information, and you'd be much more likely to recite, without error,
> > all
> > versions of the GPL.
> > And once that's settled, we can start migrating all files to concise
> > notices,
> > while keeping the exact same information we had before.
> > TL;DR
> > 1) Tell me about your file
> > 2) Add your (C) line
> > 3) Document the license of your choosing (in 1 line)
> > 4) Move on to coding!
> >  http://review.coreboot.org/#/c/8488/10/src/cpu/amd/model_
> > 10xxx/ram_calc.h
> > Alex
> > --
> > coreboot mailing list: coreboot(a)coreboot.org
> > http://www.coreboot.org/mailman/listinfo/coreboot
> coreboot mailing list: coreboot(a)coreboot.org
On Mon, Mar 2, 2015 at 11:14 AM, Corey Osgood <corey.osgood(a)gmail.com> wrote:
> On Mon, Mar 2, 2015 at 12:03 PM, Vadim Bendebury <vbendeb(a)chromium.org> wrote:
>> Not that I care much, but I can't help it: this new symbol looks very
>> much like the infamous SS Bolts:
> I can see where you're coming from, but IMO it's a bit of a stretch.
I am sure there will be more people who would make this mental
connection. But as I said, just my 2c, up to you guys.
On Mon, Mar 2, 2015 at 9:24 AM, Darmawan Salihun
> I have checked the list of supported chipset and board but it seems
> that Intel Q45 is not yet in the list. I recall, this chipset is the
> same family with Intel gm45. Anyway, the specific board I'm going to
> port into is Gigabyte GA-EQ45M-S2 Rev.1. This board has Intel Q45
> northbridge and ICH10(DO) southbridge, SuperIO ITE8720F
Keep in mind this chipset uses memory init not in the public Intel
datasheets. Unless it is extremely similar to the GM45, any port will
require MCH code from Intel, a very high level NDA, or reverse
> 1. Which part of the code that I need to read to add support for this
> Intel Q45 and i82801J-DO?
> I've been reading the coreboot/src/northbridge/intel/gm45/ section and
> coreboot/src/southbridge/intel/i82801ix so far.
You'll need to add new folders for your code in the same locations,
and modify the config files in the */intel/ folders to bring your code
into the build process. You may also need to add your CPU, I don't
know what the state of LGA775 CPUs is. You'll then have to create a
folder in coreboot/src/mainboard/ to pull it all together.
> 2. The SuperIO (ITE 8720F) is also not in the source code it seems. I
> saw ITE 8721F in there but no ITE 8720F
2. Compare the datasheets, most likely the 8721F and 8720F are
configured the same, or possibly it is the same as some other ITE
chipset. If it is, you can just point your mainboard code to that
code. If not, you may have to port it as well.
> Thanks in advance.
> Kind Regards,
> -= Знания людей принадлежат миру =-
> [-Human knowledge belongs to the world-]
> coreboot mailing list: coreboot(a)coreboot.org
FYI: I've created a ticket in jolla's ticket system. When I've received an answer I'll paste it here too.
I have checked the list of supported chipset and board but it seems
that Intel Q45 is not yet in the list. I recall, this chipset is the
same family with Intel gm45. Anyway, the specific board I'm going to
port into is Gigabyte GA-EQ45M-S2 Rev.1. This board has Intel Q45
northbridge and ICH10(DO) southbridge, SuperIO ITE8720F
1. Which part of the code that I need to read to add support for this
Intel Q45 and i82801J-DO?
I've been reading the coreboot/src/northbridge/intel/gm45/ section and
coreboot/src/southbridge/intel/i82801ix so far.
2. The SuperIO (ITE 8720F) is also not in the source code it seems. I
saw ITE 8721F in there but no ITE 8720F
Thanks in advance.
-= Знания людей принадлежат миру =-
[-Human knowledge belongs to the world-]