All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fino Meng <fino.meng@linux.intel.com>
To: xenomai@xenomai.org
Cc: fino.meng@intel.com, jan.kiszka@siemens.com,
	quirin.gylstorff@siemens.com, henning.schild@siemens.com,
	florent.pirou@intel.com, rick.y.wang@intel.com,
	hongzhan.chen@intel.com
Subject: build scripts for the WIP xenomai porting to kernel 5.4
Date: Wed, 14 Oct 2020 21:25:00 +0800	[thread overview]
Message-ID: <20201014132459.GB24671@linux.intel.com> (raw)

hi team,

I just updated the scripts to build the WIP version xenomai porting to
kernel 5.4, just follow the steps:

git clone https://github.com/finomeng/xenomai-mirror.git /tmp/xenomai-mirror.next-5.4
cd /tmp/xenomai-mirror.next-5.4
git checkout -t origin/wip/next-5.4-porting

git clone https://github.com/intel/linux-stable-xenomai /tmp/kernel
cd /tmp/kernel
git checkout -t review/5.4.59/stable/ipipe-x86

./patching-xenomai2kernel.sh

cp config_xenomai.kernel_debug .config
make olddefconfig
./build-debpkg.sh


I didn't put it togethter with ISAR/Debian yet. I test it with a PC with Debian 10 installed.

if no error, linux-image-*.deb and linux-headers-*.deb should generated outside kernel folder,
copy them to your target test device with already installed a Debian/Ubuntu,
install the deb with "dpkg -i", update-grub should be called during install linux-image-*.deb
reboot and select to boot the new kernel in grub's menu

the build steps also written in patching-xenomai2kernel.sh and build-debpkg.sh

switchtest will fail in current version, for example: "./switchtest rtk_fp_ufpp0"
will print:

r0: 2147483648 != 1000
r1: 2147483648 != 1000
r2: 2147483648 != 1000
r3: 2147483648 != 1000
r4: 2147483648 != 1000
r5: 2147483648 != 1000
r6: 2147483648 != 1000
r7: 2147483648 != 1000
ymm0: 2676586395008836901/0 != 1000/1000
ymm1: 71776119061217280/0 != 1000/1000
ymm2: 0/0 != 1000/1000
ymm3: 1000/0 != 1000/1000
ymm4: 1000/0 != 1000/1000
ymm5: 1000/0 != 1000/1000
ymm6: 1000/0 != 1000/1000
ymm7: 1000/0 != 1000/1000
Error after context switch from task 1(rtk_fp_ufpp0-1) to task 0(sleeper_ufps0-0),
FPU registers were set to 0 (maybe task sleeper_ufps0-0)

if meet more questions just write to me, thanks!

BR fino



             reply	other threads:[~2020-10-14 13:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 13:25 Fino Meng [this message]
2020-10-15 14:20 ` build scripts for the WIP xenomai porting to kernel 5.4 Jan Kiszka
2020-10-15 14:30   ` Jan Kiszka
2020-10-16  3:36   ` Fino Meng
2020-10-18 21:41     ` Jan Kiszka
2020-10-21  6:36       ` Jan Kiszka
2020-10-21 11:43         ` Fino Meng
2020-10-22  6:27           ` Jan Kiszka
2020-10-22  7:26             ` Jan Kiszka
2020-10-22  7:38               ` Fino Meng
2020-10-22 11:49               ` Fino Meng
2020-10-22 12:15                 ` Jan Kiszka
2020-10-22 13:25                   ` Fino Meng
2020-10-22 15:22                     ` Jan Kiszka
2020-10-22 16:02                       ` Jan Kiszka
2020-10-23  9:04                       ` Fino Meng
2020-10-23 12:29                         ` Jan Kiszka
2020-10-24  3:59                           ` Fino Meng
2020-10-26  7:35                         ` Jan Kiszka
2020-10-26  8:12                           ` Fino Meng
2020-10-26  8:20                             ` Jan Kiszka
2020-10-26  8:25                               ` Jan Kiszka
2020-10-26  8:26                               ` Fino Meng
2020-10-26  8:38                                 ` Jan Kiszka
2020-10-26  9:15                                   ` Fino Meng
2020-10-26  9:20                                     ` Jan Kiszka
2020-10-27  5:23                                       ` Fino Meng
2020-10-27  6:01                                         ` Jan Kiszka
2020-10-27  6:44                                           ` Fino Meng
2020-10-27  6:50                                             ` Jan Kiszka

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=20201014132459.GB24671@linux.intel.com \
    --to=fino.meng@linux.intel.com \
    --cc=fino.meng@intel.com \
    --cc=florent.pirou@intel.com \
    --cc=henning.schild@siemens.com \
    --cc=hongzhan.chen@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.com \
    --cc=rick.y.wang@intel.com \
    --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.