linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Kurt Van Dijck <kurt.van.dijck@eia.be>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Softing Firmware on gitorious
Date: Wed, 11 Jan 2012 18:37:00 +0100	[thread overview]
Message-ID: <4F0DC8BC.4040704@hartkopp.net> (raw)
In-Reply-To: <4F0DBF90.5050906@pengutronix.de>

On 11.01.2012 17:57, Marc Kleine-Budde wrote:

> On 01/11/2012 05:18 PM, Oliver Hartkopp wrote:
>> Hello Kurt,
>>
>> i just uploaded the Softing firmware from BerliOS to our new 
>>
>> https://gitorious.org/linux-can/can-misc
>>
>> git repository.
>>
>> See at 
>>
>> https://gitorious.org/linux-can/can-misc/blobs/master/firmware/softing-fw-4.6-binaries.tar.gz
>>
>> Currently the only reference is in the Linux Kernel in the Softing Kconfig:
>>
>> config CAN_SOFTING_CS
>>         tristate "Softing Gmbh CAN pcmcia cards"
>>         depends on PCMCIA
>>         depends on CAN_SOFTING
>>         ---help---
>>           Support for PCMCIA cards from Softing Gmbh & some cards
>>           from Vector Gmbh.
>>           You need firmware for these, which you can get at
>>           http://developer.berlios.de/projects/socketcan/
>>           This version of the driver is written against
>>           firmware version 4.6 (softing-fw-4.6-binaries.tar.gz)
>>           In order to use the card as CAN device, you need the Softing generic
>>           support too.
>>
>>
>> The question is now:
>>
>> 1. change the link in the Kconfig
>> 2. Add the PCMCIA firmware to the Linux Kernel (linux/firmware/*.ihex)
>> 3. 1 & 2
> 
> 3.
> 
> It would be nice to have a license statement on that files. As these are
> in binary form, the driver would be removed from the debian kernel.
> What's the official source of that firmware? Do we have a contact to
> softing?
> 


Yes. See here:

https://lists.berlios.de/pipermail/socketcan-core/2008-June/001613.html

I'll check the mentioned driver packages for license information which i don't
have on my current machine here.

Regards,
Oliver

  reply	other threads:[~2012-01-11 17:37 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 [this message]
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
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=4F0DC8BC.4040704@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=kurt.van.dijck@eia.be \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.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;
as well as URLs for NNTP newsgroup(s).