All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eva Rachel Retuya <eraretuya@gmail.com>
To: Elizabeth Ferdman <gnudevliz@gmail.com>
Cc: Daniel Baluta <daniel.baluta@intel.com>,
	Alison Schofield <amsfield22@gmail.com>,
	outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] IIO Experiment #1 Build Dummy Help
Date: Mon, 17 Oct 2016 07:49:39 +0800	[thread overview]
Message-ID: <20161016234938.GA2809@Socrates-DK> (raw)
In-Reply-To: <20161016212357.GA2263@localhost>

On Sun, Oct 16, 2016 at 02:23:58PM -0700, Elizabeth Ferdman wrote:
> On Sun, Oct 16, 2016 at 10:04:27AM +0800, Eva Rachel Retuya wrote:
> > Hi Liz,
> > 
> > On Sat, Oct 15, 2016 at 02:07:49PM -0700, Elizabeth Ferdman wrote:
> > ----massive snip----
> > > I think that running $ make -j2 && sudo make modules_install could solve
> > > this problem? If I can't do insmod can I just do modprobe?
> > > 
> > 
> > modprobe is OK to use.
> > 
> Thanks, I used modprobe and the modules were loaded.
> 
> I'm running into this issue in Task 01
> When I do 'ls -l /config/iio/devices/dummy/' the terminal just hangs. I
> closed the terminal and tried it a few more times but it was just
> freezing and I had to xkill it. I have been following the tutorial. I
> mounted the configfs at /config, made the modules, loaded them, ran
> mkdir /config/iio/devices/dummy/my_dummy_device.
> 

Hi,

I suggest to do 'make clean' again and start from scratch.
Run 'make menuconfig' and make sure the settings look like this:
{*} Industrial I/O support ---> (instead of module, make this built-in,
use 'y' instead of 'm')
<Descend this option where you'll configure configfs, dummy, etc>
{*} Enable IIO configuration via configfs (use 'y' instead of 'm')
<M> Enable software IIO device support
<M> Enable software triggers support

Under IIO dummy driver:
<M> An example driver with no hardware requirements
[*] Event generation support
[*] Buffered capture support

Compile and install, then boot to that kernel and test if it works.

Eva
> These succeeded:
> lsmod | grep dummy 
> ls -l /sys/bus/iio/devices/iio:device0/
> ls -l /sys/bus/iio/devices/iio_evgen/
> 
> The one that's no working is 
> ls -l /config/iio/devices/dummy/my_dummy_device
> or 
> ls -l /config/iio/devices/dummy/
> 
> Liz
> 
> > Eva
> > 
> > > Thanks,
> > > Liz
> > > 
> > > > thanks,
> > > > Daniel.
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20161015210748.GA13776%40localhost.
> > > For more options, visit https://groups.google.com/d/optout.


  reply	other threads:[~2016-10-16 23:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 19:52 IIO Experiment #1 Build Dummy Help Alison Schofield
2016-10-03 17:14 ` [Outreachy kernel] " sayli karnik
2016-10-03 17:23   ` Daniel Baluta
2016-10-03 17:48     ` sayli karnik
2016-10-03 18:02       ` Daniel Baluta
2017-03-23  8:28         ` sayli karnik
2016-10-09 23:19 ` Elizabeth Ferdman
2016-10-11  8:44   ` Daniel Baluta
2016-10-11 17:24     ` Elizabeth Ferdman
2016-10-14 16:06       ` Daniel Baluta
2016-10-15 21:07         ` Elizabeth Ferdman
2016-10-16  1:29           ` Elizabeth Ferdman
2016-10-16  2:04           ` Eva Rachel Retuya
2016-10-16 21:23             ` Elizabeth Ferdman
2016-10-16 23:49               ` Eva Rachel Retuya [this message]
2017-03-23 14:21                 ` SIMRAN SINGHAL
2017-03-23 14:39                   ` Daniel Baluta
2017-03-23 14:50                     ` SIMRAN SINGHAL

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=20161016234938.GA2809@Socrates-DK \
    --to=eraretuya@gmail.com \
    --cc=amsfield22@gmail.com \
    --cc=daniel.baluta@intel.com \
    --cc=gnudevliz@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.