All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fino Meng <fino.meng@linux.intel.com>
To: Jan Kiszka via Xenomai <xenomai@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [xenomai patch with kernel 5.4.77] Error building the kernel
Date: Mon, 7 Dec 2020 16:16:51 +0800	[thread overview]
Message-ID: <20201207081650.GA11889@linux.intel.com> (raw)
In-Reply-To: <6173aab3-3b0f-862b-9e5e-48989f5196b3@siemens.com>

On Mon, Dec 07, 2020 at 07:52:45AM +0100, Jan Kiszka via Xenomai wrote:
> On 04.12.20 16:13, Mohamed Irfanulla Mohamed Abdulla wrote:
> > Hi,
> > 
> > Thank you for your reply. I encountered another error.
> > 
> > Kernel: arch/x86/boot/bzImage is ready  (#1)
> > ERROR: "__ipipe_dispatch_irq" [drivers/pinctrl/intel/pinctrl-intel.ko]
> > undefined!
> > make[1]: *** [scripts/Makefile.modpost:94: __modpost] Error 1
> > make: *** [Makefile:1319: modules] Error 2
> > 
> > Is it good to exclude CONFIG_PINCTRL?
> 
> Only if you do not need that. But there might be cases where this cannot
> be off.
> 
> Fino, could you have a look?
> 
> Jan
> 

the error is compiler&&linker cannot find __ipipe_dispatch_irq when
building pinctrl-intel.ko,
change pinctrl-intel.ko to built-in but not module should solve the
issue.

a dirty fix is export this function:
+EXPORT_SYMBOL_GPL(__ipipe_dispatch_irq);

I will try if can give a clean fix of this issue.

BR fino

> > 
> > Thanks,
> > 
> > On Mon, Nov 30, 2020 at 2:27 PM Jan Kiszka <jan.kiszka@siemens.com
> > <mailto:jan.kiszka@siemens.com>> wrote:
> > 
> >     On 30.11.20 13:41, florian.bezdeka--- via Xenomai wrote:
> >     > On Mon, 2020-11-30 at 12:16 +0100, Mohamed Irfanulla Mohamed Abdulla
> >     > wrote:
> >     >> Thank you for your reply. 
> >     >> I find that I use the wrong branch. Could you please suggest a good
> >     >> branch that I can use?
> >     >>
> >     >
> >     > I'm quite new to the Xenomai project, so don't trust me ;-)
> >     >
> >     > The problem you are facing was "fixed" in commit
> >     > 608c23297c4d ("cobalt/x86: Account for FPU changes in kernel 5.2")
> >     > which is part of the "next" branch.
> >     >
> >     > It looks like kernels >= 5.2 are not supported in official releases /
> >     > branches yet.
> > 
> >     Correct. Next 3.1.x release will include that. Until then you need a
> >     version from git.
> > 
> >     Jan
> > 
> >     -- 
> >     Siemens AG, T RDA IOT
> >     Corporate Competence Center Embedded Linux
> > 
> 
> 
> -- 
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux
> 


      reply	other threads:[~2020-12-07  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 10:49 RE:[xenomai patch with kernel 5.4.77] Error building the kernel Mohamed Irfanulla Mohamed Abdulla
2020-11-30 11:00 ` [xenomai " florian.bezdeka
     [not found]   ` <CADx0-8C7CW4i+O7g4zAGE0uXtD+bnNr4oR8HF-_tNArpteSDmQ@mail.gmail.com>
2020-11-30 12:41     ` florian.bezdeka
2020-11-30 13:27       ` Jan Kiszka
2020-12-04 15:13         ` Mohamed Irfanulla Mohamed Abdulla
2020-12-07  6:52           ` Jan Kiszka
2020-12-07  8:16             ` Fino Meng [this message]

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=20201207081650.GA11889@linux.intel.com \
    --to=fino.meng@linux.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.