All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Paul <paul_c@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] rtdm over x86_64
Date: Sat, 03 Feb 2007 16:08:48 +0100	[thread overview]
Message-ID: <45C4A580.3000904@domain.hid> (raw)
In-Reply-To: <200702031313.20104.paul_c@domain.hid>

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

Paul wrote:
> Hi Jan
> 
>  Just a small patch to get the ball rolling with an x86_64 support..
> 
> The attached resolves a compile time warning of: 
> 
> kernel/xenomai/skins/rtdm/core.c: In function ‘_rtdm_ioctl’:
> kernel/xenomai/skins/rtdm/core.c:408: warning: comparison is always false due 
> to limited range of data type
> 

Yeah, when looking at this issue with 64-bit glasses, this urgently
needs fixing (I wonder why ia64 didn't stumble yet?).

Your patch points in the right direction, but it needs a bit fine-tuning
and also has to include the ioctl handlers of drivers. I will work out a
fix and inform you. I'll have to rely on your test lab. :)

But first I need some build environment. A quick shot ended here when
trying to configure a patch and prepared 2.6.19 kernel:

# make ARCH=x86_64 CC="gcc -m64" oldconfig
...
init/Kconfig:572: can't open file "arch/x86_64/xenomai/Kconfig"

Anyone any idea? Is something missing, or is the prepare script broken?

Jan


PS: Once we have in-tree RTDM services and drivers running, are you
interested in a RTnet excursion over x64? I should be able to make this
compile, but for testing...


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

  reply	other threads:[~2007-02-03 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 13:13 [Xenomai-core] rtdm over x86_64 Paul
2007-02-03 15:08 ` Jan Kiszka [this message]
2007-02-03 15:18   ` Jan Kiszka
2007-02-03 15:45   ` Philippe Gerum
2007-02-03 17:51     ` Jan Kiszka
2007-02-03 23:32   ` Paul

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=45C4A580.3000904@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=paul_c@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.