From: Darren Hart <dvhart@linux.intel.com>
To: Michael_E_Brown@Dell.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: udev blacklist ineffective
Date: Mon, 28 Jan 2013 10:52:05 -0800 [thread overview]
Message-ID: <5106C8D5.9000705@linux.intel.com> (raw)
In-Reply-To: <DB6E482E89290547898851B8CC9D8110DC3609D8@AUSX7MCPS302.AMER.DELL.COM>
On 01/28/2013 08:36 AM, Michael_E_Brown@Dell.com wrote:
> I have two embedded systems that share some devices over an i2c bus. Only one system may load the device driver at a time, and loading the device driver is already well-controlled by the HA subsystem.
>
> Our new yocto build with udev enabled is auto-loading these device drivers with catastrophic results. We must absolutely prohibit such automatic behaviour for our list of devices. I have tried:
>
> $ cat etc/modprobe.d/blacklist.conf
> blacklist seepmtd
> ... cut ...
>
> And this does *NOT* work. I have tried renaming blacklist.conf to
> modprobe.conf as well as creating modprobe.conf with these blacklist
> entries.
>
> This is a huge blocking issue and I have been unable to figure out a
> workaround for it. I would appreciate any suggestions.
OK, so... this needs to be addressed.
However, can you just not build/install the drivers for the system that
shouldn't be accessing them? Or do you require a more general image?
You will need to provide details about the version of oe-core you are
using, kmod or modutils, and any relevant DISTRO configurations you have
made, which bit of software do you expect to be honoring the blacklist, etc.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-01-28 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 16:36 udev blacklist ineffective Michael_E_Brown
2013-01-28 18:52 ` Darren Hart [this message]
2013-01-28 19:09 ` Michael_E_Brown
2013-02-20 7:34 ` Khem Raj
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=5106C8D5.9000705@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=Michael_E_Brown@Dell.com \
--cc=openembedded-core@lists.openembedded.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.