public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Copyright/License text in cpu/ppc4xx/4xx_pci.c
Date: Thu, 9 Jul 2009 11:24:39 +0200	[thread overview]
Message-ID: <200907091124.39593.matthias.fuchs@esd.eu> (raw)
In-Reply-To: <200907091100.18995.sr@denx.de>

On Thursday 09 July 2009 11:00, Stefan Roese wrote:
> On Thursday 09 July 2009 10:44:13 Matthias Fuchs wrote:
> > I just checked the nine years old initial version of 405gp_pci.c:
> >
> > http://ppcboot.cvs.sourceforge.net/viewvc/ppcboot/ppcboot/cpu/ppc4xx/405gp_
> >pci.c?revision=1.1&view=markup
> >
> > I do not see that this file has anything in common with the current
> > 4xx_pci.c code! One could say that setting up the PMM registes looks a
> > little as is comes from the old IBM code, but can writing zeros into some
> > registers really stop us from cleaning up this license issue?
> 
> Yes, those files don't have much in common any more. Only some comments (which 
> could be removed or rewritten) and and the sequence of some register 
> initialisation. But again, IANAL and I don't really know if we can remove the 
> IBM header with such a history.
It seems nobody is a lawyer! So I think this issue cannot be solved by 
the U-boot community and therefore the only way seems to be the removal
of this file in August as stated in the feature-removal plan.

I will not start cleaning up this file as it seems to be a waste of
time when the file will be removed in August.

Stefan, how do you plan to reach the August goal?

> > If so, I see no way to reach the GPL cleanup goal.
> >
> > I will submit a cleanup patch for the 4xx_pci.c when we are common in this
> > point. I also request "Ack-bys" at least from you and Stefan on my patch to
> > not have one foot in the grave :-)
> 
> Heh, don't be such a coward! No risk, no fun! ;)
When I go through my posting I must admit that I never said IANAL.
But many others did. Perhaps we can setup an open source developer jail
where everything is allowed because they cannot put you deeper in jail :-)

Matthias

  reply	other threads:[~2009-07-09  9:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 13:40 [U-Boot] Copyright/License text in cpu/ppc4xx/4xx_pci.c Matthias Fuchs
2009-07-08 13:57 ` Stefan Roese
2009-07-08 14:21   ` Matthias Fuchs
2009-07-08 14:31     ` Stefan Roese
2009-07-08 15:51     ` Wolfgang Denk
2009-07-08 17:50       ` Robin Getz
2009-07-08 18:24       ` Matthias Fuchs
2009-07-08 19:03         ` Wolfgang Denk
2009-07-08 20:51           ` Matthias Fuchs
2009-07-08 20:57             ` Wolfgang Denk
2009-07-09  8:44               ` Matthias Fuchs
2009-07-09  9:00                 ` Stefan Roese
2009-07-09  9:24                   ` Matthias Fuchs [this message]
2009-07-09  9:51                     ` Stefan Roese
2009-07-09 10:10                       ` Wolfgang Denk
2009-07-09 10:15                         ` Stefan Roese
2009-07-09 12:20                           ` Wolfgang Denk
2009-07-09 12:23                             ` Stefan Roese
2009-07-21 11:42                       ` Matthias Fuchs
2009-07-21 11:58                         ` Stefan Roese
2009-07-21 14:09                         ` Scott McNutt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907091124.39593.matthias.fuchs@esd.eu \
    --to=matthias.fuchs@esd.eu \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox