All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Michael Haberler <haberlerm@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] RTDM-native brushup
Date: Fri, 19 Jun 2015 14:07:31 +0200	[thread overview]
Message-ID: <55840603.4090600@siemens.com> (raw)
In-Reply-To: <99b5d80b7648a20419ad62efa3865cc3.squirrel@sourcetrek.com>

On 2015-06-19 13:58, Gilles Chanteperdrix wrote:
> 
> Michael Haberler wrote:
>> Jan - thanks! I made minor progress. duh on the mknod..
> 
> Note that it is possible to get devices to be automatically created by
> udev/devtmptfs, I did the exercise once. I think you need the device to be
> instances of a "device class", or something like that.

Exactly, kernel/cobalt/pipe.c contains that pattern, to name just one
example. mknod is only a quick workaround.

> 
> Also note that with the advent of devtmpfs, the complexity of udev, the
> slow down it causes to the boot procses, and its entanglement with
> systemd, devtmpfs is probably a better choice on embedded systems now. If
> you need a larger subset of udev functionality, you can also have a look
> at busybox mdev.
> 

That should be an independent optimization path.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-06-19 12:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 14:39 [Xenomai] RTDM-native brushup Michael Haberler
2015-06-17 18:37 ` Jan Kiszka
2015-06-19 10:14   ` Michael Haberler
2015-06-19 11:58     ` Gilles Chanteperdrix
2015-06-19 12:07       ` Jan Kiszka [this message]
2015-06-19 12:14     ` Jan Kiszka
2015-06-19 13:27       ` Michael Haberler
2015-06-19 13:35         ` Jan Kiszka
2015-06-19 17:51           ` Michael Haberler
2015-06-22 15:34             ` Michael Haberler
2015-06-22 15:50               ` Jan Kiszka
2015-06-22 22:46                 ` Michael Haberler

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=55840603.4090600@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=haberlerm@gmail.com \
    --cc=xenomai@xenomai.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.