On 04/25/2013 11:15 AM, Kurt Van Dijck wrote:
> On Thu, Apr 25, 2013 at 09:35:35AM +0200, Marc Kleine-Budde wrote:
>> On 04/25/2013 09:07 AM, Marc Kleine-Budde wrote:
>>> On 04/25/2013 08:41 AM, Wolfgang Grandegger wrote:
>>>> Hi Kurt,
>>>>
>>>> On 04/24/2013 04:49 PM, Kurt Van Dijck wrote:
>>>>> Hi Stephane,
>>>>>
>>>>> I have written this some time ago, not using it actually.
>>>>> I tried a modular approach, don't know if its usefull.
>>>>>
>>>>> PS: I used attachments.
>>>>
>>>> ~/enumif$ ./enumif
>>>> 1: lo	{loopback} <LOOPBACK,UP,LOWER_UP> UNKNOWN
>>>> 2: eth0	{ether} <BROADCAST,MULTICAST> DOWN
>>>> 3: eth1	{ether} <BROADCAST,MULTICAST,UP,LOWER_UP> UNKNOWN
>>>> 4: eth3	{ether} <NO-CARRIER,BROADCAST,MULTICAST,UP> DOWN
>>>> 5: can0	{can} <NOARP,UP,LOWER_UP,ECHO> UNKNOWN
>>>> 6: can1	{can} <NOARP,ECHO> DOWN
>>>> 7: can2	{can} <NOARP,ECHO> DOWN
>>>> 8: can3	{can} <NOARP,ECHO> DOWN
>>>> 9: pan0	{ether} <BROADCAST,MULTICAST> DOWN
>>>>
>>>> Cool! We know that "ip link" does list all network interfaces but the
>>>> code doing the job is not really strength-forward. I think this would be
>>>> a nice enhancement of the can-utils.
>>>
>>> Good idea, Stephane, can you license the code under a permissive license
>>> like LGPL or BSD?
>>
>> Errr...sorry. It's Kurt, who posted that code.
> 
>> Kurt, can you give the code a nice license? :)
> What is needed for LGPL or BSD?
> Is there a short overview available?

If the code is LGPL we can include it in the libsocketcan. You are
allowed to link the library against your closed source application
(without to license under GPL). Any changes you make to the library have
to be made available as source code.

IANAL,
Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |