linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] IXP4xx: Add Gateworks Cambria support.
Date: Fri, 20 Sep 2013 11:13:39 +0200	[thread overview]
Message-ID: <op.w3pc81032s3iss@ecaz> (raw)
In-Reply-To: <m37gebanth.fsf@t19.piap.pl>

On Fri, 20 Sep 2013 10:40:10 +0200, Krzysztof Ha?asa <khalasa@piap.pl> wrote:

> "Imre Kaloz" <kaloz@openwrt.org> writes:
>
>> This file seems to miss both the copyright from the code it's based on
>> as well as most of the additional support that one has.
>> So what's the point?
>
> I have the smaller Cambria (GW2350), not the bigger one which is also
> supported by OpenWRT. I'm not going to blindly pick up the OpenWRT code
> for which I don't have the hw and which I can't really test nor
> maintain.

So you delete portions of the code because you don't want to ask someone with the board to test your changes if needed, but given quite some people use the code for quite some time, you can also assume it works for them.

> The file contains information that it's partially based on OpenWRT, is it
> now a bad idea to pick up fragments from one GPLv2 project (OpenWRT) and
> include them in another GPLv2 project (Linux kernel)? Isn't it what
> OpenWRT does (in the opposite direction)? Aren't all the boards (in this
> particular case) based on Avila and IXDP425, the devel platform?

OpenWrt (yeah, we spell it this way for about 10 years now) is a Linux distribution, you do mix things up a bit here.

> The code doesn't carry any copyright headers maybe because in my country
> they aren't required, maybe because it's a trivial board support code
> which is mostly a list of devices and I didn't bother, and it doesn't
> have OpenWRT copyright because it's not a version from OpenWRT (while
> its parts are, as prominently stated). For precisely the same reason I
> list myself as the platform maintainer, I don't feel authorized to put
> somebody else here.

It's up to you if you add your copyright, but removing others' is clearly a different story legally. And I bet that's the same in your country, too.

> But I have an idea. I would be pleased if you submit and maintain (in
> the official Linux, not OpenWRT) your own version instead. It would be
> great if you also include Ubiquity RouterStation Pro (ATH79) and
> Gateworks Laguna (CNS3xxx). Those boards are supported for a long time
> by OpenWRT (at least there is support code there) and I'm personally
> using them with (stock) Linux.

I'll do when I'll get around it. Both others and we've pushed a lot of code upstream. In the meantime, anyone is free to do so, including you - dumbing down the code could be justifiable in some cases (I don't think this one applies), but dropping others' copyright -- hardly.


Imre

  reply	other threads:[~2013-09-20  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  7:13 [PATCH] IXP4xx: Add Gateworks Cambria support Krzysztof Hałasa
2013-09-19 16:03 ` Luka Perkov
2013-09-19 18:27   ` Krzysztof Halasa
2013-09-19 20:52 ` Imre Kaloz
2013-09-20  8:40   ` Krzysztof Hałasa
2013-09-20  9:13     ` Imre Kaloz [this message]
2013-09-25  7:24       ` Krzysztof Hałasa

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=op.w3pc81032s3iss@ecaz \
    --to=kaloz@openwrt.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).