All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [CAN] SIOC* clash
Date: Tue, 27 Feb 2007 15:28:47 +0100	[thread overview]
Message-ID: <45E4401F.3050904@domain.hid> (raw)

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

Hi Wolfgang,

just realised that there is an ABI mine laid in rtcan.h:

#ifndef SIOCGIFINDEX
#define SIOCGIFINDEX \
            _IOWR(RTIOC_TYPE_CAN, 0x00, struct ifreq)
#endif

So, if you happen to have included sys/ioctl.h earlier in your
application, an incompatible IOCTL code will be used in user space.

I recommend to switch to existing IOCTL codes where available (that's
what we do in RTnet as well). This may also mean betting on the current
IOCTL assignments in Socket-CAN, that they will survive unchanged the
eventual merge into Linux mainline.

Jan


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

             reply	other threads:[~2007-02-27 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 14:28 Jan Kiszka [this message]
2007-02-27 14:45 ` [Xenomai-core] Re: [CAN] SIOC* clash Wolfgang Grandegger

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=45E4401F.3050904@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=wg@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.