From: Jan Kiszka <jan.kiszka@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 22:34:25 +0100 [thread overview]
Message-ID: <45E35261.8000505@domain.hid> (raw)
In-Reply-To: <bc4264770702261237v2cdd380ag128ed0cfb703b281@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
roland Tollenaar wrote:
>> Add 1 to 1: The CAN profile describes what IOCTLs are available for CAN
>> sockets. rt_dev_ioctl() (or ioctl() with the POSIX skin) is the way to
>> pass these IOCTLs down to the CAN stack.
>
> Actually this sheds quite a bit of light on matters. If you would be
> so kind as to give a brief explanation of what a "stack" is exactly. I
> have been confronted with the term quite a lot now but its not
> becoming clearer. I used to think it was a buffer of some kind. Kind
> of like the ones that one "pushes" and "pops" on but I can't see a
> connection between that concept and what you say above.
http://en.wikipedia.org/wiki/Protocol_stack? :->
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-02-26 21:34 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
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 [this message]
[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=45E35261.8000505@domain.hid \
--to=jan.kiszka@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.