From: Wolfgang Grandegger <wg@grandegger.com>
To: Stephane Grosjean <s.grosjean@peak-system.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Is there any way of getting the CAN interfaces list, from any C program?
Date: Thu, 25 Apr 2013 09:43:20 +0200 [thread overview]
Message-ID: <5178DE98.7040408@grandegger.com> (raw)
In-Reply-To: <20130425072429.GA448@vandijck-laurijssen.be>
On 04/25/2013 09:24 AM, Kurt Van Dijck wrote:
> On Thu, Apr 25, 2013 at 08:41:16AM +0200, 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.
>
> would it make sense to maintain the split into enumif-test.c and enumif.c,
> so for example Stephane could just link to libenumif.a?
Well, a better place might be libsocketcan then. In general it would be
nice to host libsocketcan (maybe as liblinuxcan) at
https://gitorious.org/linux-can as well.
Wolfgang.
next prev parent reply other threads:[~2013-04-25 7:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 19:35 [RFC PATCH v2] can: sja1000: use common prefix for all sja1000 defines Oliver Hartkopp
2013-04-16 10:40 ` Marc Kleine-Budde
2013-04-24 9:06 ` Is there any way of getting the CAN interfaces list, from any C program? Stephane Grosjean
2013-04-24 14:49 ` Kurt Van Dijck
2013-04-25 6:41 ` Wolfgang Grandegger
2013-04-25 7:07 ` Marc Kleine-Budde
2013-04-25 7:35 ` Marc Kleine-Budde
2013-04-25 9:15 ` Kurt Van Dijck
2013-04-25 9:20 ` Marc Kleine-Budde
2013-04-25 7:24 ` Kurt Van Dijck
2013-04-25 7:43 ` Wolfgang Grandegger [this message]
2013-04-25 9:14 ` Kurt Van Dijck
2013-04-25 9:23 ` Marc Kleine-Budde
2013-04-25 9:42 ` Kurt Van Dijck
2013-04-25 21:08 ` Kurt Van Dijck
2013-04-24 21:02 ` François
2013-04-24 21:27 ` Marc Kleine-Budde
2013-04-25 8:04 ` Kurt Van Dijck
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=5178DE98.7040408@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
/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).