From: Kurt Van Dijck <kurt.van.dijck-/BeEPy95v10@public.gmane.org>
To: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
Cc: "socketcan-users-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org"
<socketcan-users-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>,
"linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Bit rate configuration of PEAK USB devices
Date: Thu, 17 Nov 2011 17:25:36 +0100 [thread overview]
Message-ID: <20111117162535.GF366@e-circ.dyndns.org> (raw)
In-Reply-To: <4EC532E9.5050308-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
On Thu, Nov 17, 2011 at 05:14:33PM +0100, Oliver Hartkopp wrote:
> On 17.11.2011 12:24, Kurt Van Dijck wrote:
>
> > On Thu, Nov 17, 2011 at 07:49:43AM +0100, Heinz-Jürgen Oertel wrote:
> >>
> >> Danke Oliver,
> >>
> >> for now I decided to use something like
> >>
> >> system("echo \"i 0x4914 e\" > /dev/pcan0");
> >>
> >> Unfortunately at the moment I have no idea how to determine if I'm just talking to an Peak or an EMS interface to select the method of setting the bit rate.
> >
> > Maybe
> >
> > $ ip -d link show can0
> >
> > will show differently?
>
>
> No.
>
> The PEAK driver does not use the candev framework (drivers/net/can/dev.c).
> Therefore you won't see anything beyond up/down state and tx_queue_len, etc.
> Not bitrate settings :-(
My idea was to use this 'lack of information' to auto-decide if it's an EMS or PEAK
interface. But Heinz-Jürgen already pointed out that using some /proc file, you
can also see if a device is a PEAK device.
Kurt
>
> Regards,
> Oliver
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
Socketcan-users mailing list
Socketcan-users@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/socketcan-users
next prev parent reply other threads:[~2011-11-17 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 14:13 Bit rate configuration of PEAK USB devices Heinz-Jürgen Oertel
2011-11-15 18:09 ` [Socketcan-users] " Oliver Hartkopp
2011-11-15 18:33 ` Oliver Hartkopp
[not found] ` <4EC2B072.5060704-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-11-17 6:49 ` Heinz-Jürgen Oertel
[not found] ` <B3B3BE5A55ED7743A83865E234A22B1D1B91F2BE57-E+xEQJb9ENTWDPv2tuTBK42P0GrZ+RbP@public.gmane.org>
2011-11-17 11:24 ` Kurt Van Dijck
[not found] ` <20111117112447.GA366-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-11-17 16:14 ` Oliver Hartkopp
[not found] ` <4EC532E9.5050308-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-11-17 16:25 ` Kurt Van Dijck [this message]
[not found] ` <20111117162535.GF366-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-11-17 17:55 ` Wolfgang Grandegger
[not found] ` <4EC54A78.2060109-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-11-18 9:23 ` Marc Kleine-Budde
2011-11-17 16:11 ` Oliver Hartkopp
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=20111117162535.GF366@e-circ.dyndns.org \
--to=kurt.van.dijck-/beepy95v10@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org \
--cc=socketcan-users-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
/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).