From: Wolfgang Grandegger <wg@domain.hid>
To: roland Tollenaar <rolandtollenaar@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] newby question, can/socket stuff
Date: Mon, 26 Feb 2007 20:57:20 +0100 [thread overview]
Message-ID: <45E33BA0.6080903@domain.hid> (raw)
In-Reply-To: <bc4264770702261108l6b3f60b2w53e9e90e40d79b92@domain.hid>
roland Tollenaar wrote:
> Hi,
>
> I am looking through the rtcan code provided with the xenomai package
> and I realize one thing:
>
> I know too little of the basic socket programming. Not even sure my
> wording in the previous sentence is capturing the correct area of
> ignorance.
There are plenty text books on BSD socket programming and the rational
behind it.
> I suspect very strongly that the rtcan functionality is designed to
> piggyback on whatever standard iocontrol is taking place in functions
> like
>
> ret = rt_dev_ioctl(can_fd, SIOCGIFINDEX, &ifr);
>
> and
> ret = rt_dev_ioctl(can_fd, SIOCSCANBAUDRATE, &ifr);
>
> But exactly what is happening is beyond me at the moment.
SIOCGIFINDEX gets the interface index for a named device and
SIOCSCANBAUDRATE allows to set the baudrate. The RT-Socket-CAN utilities
are now even hyperlinked with the API doc (still not 100% perfect yet) e.g.:
http://www.xenomai.org/documentation/trunk/html/api/rtcanconfig_8c-example.html
> Now I can obviously try to copy like a chinaman (no disrespect
> intended!) and not understand what I am doing but it is not really a
> mode of operation I relish.
>
> I have briefly tried to locate the rt_dev_ioctl back to a xenomai
> header but have not managed to trace it yet.
> Is it defined in the standard linux ioctl headers? Where can I find
> some info on what arguments these functions are passed etc?
Hm, try:
$ cd <xenomai-root>
$ find . -name '*.[ch]' | xargs grep SIOCSCANBAUDRATE
> Much appreciated.
Wolfgang.
next prev parent reply other threads:[~2007-02-26 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 19:08 [Xenomai-help] newby question, can/socket stuff roland Tollenaar
2007-02-26 19:18 ` Gilles Chanteperdrix
2007-02-26 19:58 ` roland Tollenaar
2007-02-26 20:13 ` Wolfgang Grandegger
2007-02-26 20:13 ` Gilles Chanteperdrix
2007-02-26 19:57 ` Wolfgang Grandegger [this message]
2007-02-26 20:06 ` roland Tollenaar
2007-02-26 20:16 ` Jan Kiszka
2007-02-26 20:37 ` roland Tollenaar
2007-02-26 21:13 ` Paul
2007-02-26 21:34 ` Jan Kiszka
[not found] ` <45E3F83B.4070702@domain.hid>
[not found] ` <45E3FDD5.4070308@domain.hid>
2007-02-27 10:03 ` Roland Tollenaar
2007-02-26 20:25 ` Wolfgang Grandegger
2007-02-26 20:42 ` roland Tollenaar
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=45E33BA0.6080903@domain.hid \
--to=wg@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.