From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Softing Firmware on gitorious
Date: Thu, 12 Jan 2012 10:30:09 +0100 [thread overview]
Message-ID: <20120112093009.GC380@e-circ.dyndns.org> (raw)
In-Reply-To: <4F0EA442.8080303@pengutronix.de>
On Thu, Jan 12, 2012 at 10:13:38AM +0100, Marc Kleine-Budde wrote:
> On 01/12/2012 10:02 AM, Kurt Van Dijck wrote:
> >>> https://lists.berlios.de/pipermail/socketcan-core/2008-June/001613.html
> >> This convinces me as a developer that they have not problem.
> >>>
> >>> I'll check the mentioned driver packages for license information which i don't
> >>> have on my current machine here.
> >> I'll look too.
> >
> > The 5.01 package states the binary blob (and their code) is GPLv2.
> > The remainders of the 4.6 package I still have (only the firmware part) also
> > state it's all released under GPLv2.
>
> Do you mean the binary blob's source code is available as GPLv2? Do we
> have access to the source code? Would be interesting for the Debian Kernel.
Softing releases a linux driver package, with linux driver code and firmware
under GPLv2. The firmware is packaged as array's in c files.
The sources of the firmware itself are not available.
Kurt
next prev parent reply other threads:[~2012-01-12 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 16:18 Softing Firmware on gitorious Oliver Hartkopp
2012-01-11 16:57 ` Alexander Stein
2012-01-11 18:06 ` Oliver Hartkopp
2012-01-11 16:57 ` Marc Kleine-Budde
2012-01-11 17:37 ` Oliver Hartkopp
2012-01-12 8:25 ` Kurt Van Dijck
2012-01-12 9:02 ` Kurt Van Dijck
2012-01-12 9:13 ` Marc Kleine-Budde
2012-01-12 9:30 ` Kurt Van Dijck [this message]
2012-01-12 9:34 ` Marc Kleine-Budde
2012-01-12 10:01 ` Kurt Van Dijck
2012-01-12 10:12 ` Marc Kleine-Budde
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=20120112093009.GC380@e-circ.dyndns.org \
--to=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
/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).