Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Hans-Heinrich Hansen <hhansen@avt-nbg.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] Buildroot with Advantech EIO-IS200-DRIVER
Date: Tue, 05 Aug 2025 08:04:09 +0200	[thread overview]
Message-ID: <87ms8ejodi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <FR5P281MB5078D44083ABDE1AAC41FC828722A@FR5P281MB5078.DEUP281.PROD.OUTLOOK.COM> (Hans-Heinrich Hansen's message of "Tue, 5 Aug 2025 04:53:39 +0000")

>>>>> "Hans-Heinrich" == Hans-Heinrich Hansen <hhansen@avt-nbg.de> writes:

Hello Hans,

Please keep Buildroot discussion on the mailing list, thanks.

 > Hi Peter,
 > my problem is indeed the "out-of-tree kernel module". Btw. I've tried
 > it with loadable module support enabled and disabled.

You will need to enable modules support in your kernel in order to build
and load external modules.

 > It seems that the eio-is200 is not used by the buildroot process.
 > I've followed the buildroot instructions. I'm sure that I've made a
 > mistake. Please can you check my attached configuraton files?

For reference, the custom package is:

################################################################################
#
# eio_is200_driver
#
################################################################################

EIO_IS200_DRIVER_VERSION = 082e737c59aa92bba2c29db46a06cdd0e5beb600
EIO_IS200_DRIVER_DEPENDENCIES = linux
EIO_IS200_DRIVER_SITE = $(call github,ADVANTECH-Corp,eio-is200-linux-kernel-driver,$(EIO_IS200_DRIVER_VERSION))
EIO_IS200_DRIVER_LICENSE = GPL-2.0
EIO_IS200_DRIVER_LICENSE_FILES = COPYING

$(eval $(kernel-module))
$(eval $(generic-package))

Which looks sensible to me (didn't check the details of the upstream
eio-is100-linux-kernel-driver Makefiles). Does it build some kernel
modules? What happens if you modprobe/insmod them?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-08-05  6:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 11:37 [Buildroot] Buildroot with Advantech EIO-IS200-DRIVER Hans-Heinrich Hansen
2025-08-04 18:31 ` Peter Korsgaard
     [not found]   ` <FR5P281MB5078D44083ABDE1AAC41FC828722A@FR5P281MB5078.DEUP281.PROD.OUTLOOK.COM>
2025-08-05  6:04     ` Peter Korsgaard [this message]
2025-08-06  6:14       ` Hans-Heinrich Hansen
2025-08-06  7:37         ` Peter Korsgaard
2025-08-06 10:45           ` Hans-Heinrich Hansen

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=87ms8ejodi.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=hhansen@avt-nbg.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox