All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: sayli karnik <karniksayli1995@gmail.com>
Cc: daniel.baluta@gmail.com, outreachy-kernel@googlegroups.com
Subject: Re: Doubt regarding iio task 01
Date: Sat, 24 Sep 2016 23:28:14 -0700	[thread overview]
Message-ID: <20160925062813.GA9644@d830.WORKGROUP> (raw)
In-Reply-To: <CAKG5xWjTCC4oyXcHC5du3imeE9VP2nwL=3c9XwvvHzYTB0zCSA@mail.gmail.com>

On Sat, Sep 24, 2016 at 07:11:23PM +0530, sayli karnik wrote:
> Hello,
> 
> I ran the following compilation command:
> make drivers/iio/dummy/iio_dummy_evgen.ko
> 
> The following is the error encountered:
> https://www.irccloud.com/pastebin/aO6XB4Le
> 
> I have enabled the config options required:
>  #
>  # IIO dummy driver
>  #
>  CONFIG_IIO_DUMMY_EVGEN=m
>  CONFIG_IIO_SIMPLE_DUMMY=m
>  CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y
>  CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y
> 
> Could you point me towards a solution to this?
> 
> Thanks!
Hi Sayli,

Hope this helps...ask more if you get stuck.

git grep those undefined labels and you'll find you need industrialio.ko

To use insmod you'll need to insmod the dependencies. 

insmod industrialio.ko
insmod iio_dummy_evgen.ko
insmod kfifo_buf.ko
insmod iio_dummy.ko

Your end result will satisfy these dependencies..

$ lsmod | grep dummy
iio_dummy              16384  0
kfifo_buf              16384  1 iio_dummy
iio_dummy_evgen        16384  2 iio_dummy
industrialio           61440  3 iio_dummy,kfifo_buf,iio_dummy_evgen

alisons


      parent reply	other threads:[~2016-09-25  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-24 13:41 Doubt regarding iio task 01 sayli karnik
2016-09-24 13:47 ` [Outreachy kernel] " Julia Lawall
2016-09-25  6:28 ` Alison Schofield [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=20160925062813.GA9644@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=daniel.baluta@gmail.com \
    --cc=karniksayli1995@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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.