From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Leo Yan <leo.yan@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Regression] Missing device nodes for ETR, ETF and STM after CONFIG_UEVENT_HELPER=n
Date: Fri, 26 Jul 2019 13:33:16 +0200 [thread overview]
Message-ID: <20190726133316.688a43d8@windsurf> (raw)
In-Reply-To: <20190726101925.GA22476@kroah.com>
Hello,
On Fri, 26 Jul 2019 12:19:25 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > This somehow is not mounting etr, etf, stm devices when uevent-helper is
> > disabled. Anyways as Suzuki mentioned, using devtmpfs does fix the issue.
>
> Last I looked (many years ago) mdev requires uevent-helper in order for
> it to work. I recommend that if you rely on mdev to keep that option
> enabled, or to just use devtmpfs and udev :)
Since Busybox 1.31.0, mdev has gained a daemon mode. In this mode, mdev
runs in the background, and receives uevent through a netlink socket.
So there's been some changes in how Busybox mdev works in recent times.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-26 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:19 [Regression] Missing device nodes for ETR, ETF and STM after CONFIG_UEVENT_HELPER=n Sai Prakash Ranjan
2019-07-26 6:26 ` Sai Prakash Ranjan
2019-07-26 7:04 ` Greg Kroah-Hartman
2019-07-26 8:20 ` Sai Prakash Ranjan
2019-07-26 8:41 ` Greg Kroah-Hartman
2019-07-26 9:28 ` Suzuki K Poulose
2019-07-26 9:58 ` Sai Prakash Ranjan
2019-07-26 10:02 ` Sai Prakash Ranjan
2019-07-26 9:44 ` Sai Prakash Ranjan
2019-07-26 10:14 ` Sai Prakash Ranjan
2019-07-26 10:19 ` Greg Kroah-Hartman
2019-07-26 10:24 ` Sai Prakash Ranjan
2019-07-26 11:33 ` Thomas Petazzoni [this message]
2019-07-26 11:43 ` Greg Kroah-Hartman
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=20190726133316.688a43d8@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).