linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: François <fbeaulier@orange.fr>
Cc: 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: Wed, 24 Apr 2013 23:27:09 +0200	[thread overview]
Message-ID: <51784E2D.60209@pengutronix.de> (raw)
In-Reply-To: <51784851.1000208@orange.fr>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

On 04/24/2013 11:02 PM, François wrote:
> Stephane,
> 
> This is what i have done in a open source project i have started, a web
> can analyzer called ewecan (https://bitbucket.org/Mongo/ewecan):
> It parses /sys/class/net but unfortunately, as noted in comments, it
> cannot make the difference between up or down interfaces.
> 
> /* Get a list of available socketcan interfaces and return them in
>    a string as a JS array like ["can0", "can1", "vcan"]
>    Returned string must be freed after use
>    BUG : it also returns interfaces that are present but down !
> */

Whan happens if I rename my ethernet interface to "can0"?

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   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-04-24 21:27 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
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 [this message]
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=51784E2D.60209@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=fbeaulier@orange.fr \
    --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).