From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Allow several device tables and split in two parts our device table
Date: Tue, 17 May 2011 10:55:09 +0200 [thread overview]
Message-ID: <20110517105509.5521276b@surf> (raw)
In-Reply-To: <87mxilhg3z.fsf@macbook.be.48ers.dk>
On Tue, 17 May 2011 10:43:28 +0200
Peter Korsgaard <jacmet@uclibc.org> wrote:
> Thomas> But I don't know what we can do against this. Should we instead add an
> Thomas> option to makedevs to instruct makedevs to skip entries in /dev ? This
> Thomas> option could then be used for all dynamic /dev cases, and would work
> Thomas> even if the device table contains entries for /dev ? Or should we keep
> Thomas> it as it is ?
>
> Alternatively we can split it up and provide an option for the base
> device table (which will default to target/generic/device_table.txt) and
> add an option for static device nodes (which defaults to
> target/generic/device_table_dev.txt) and only make that option visible
> if static dev is used.
>
> The makefile can then concatenate those options and use them like it is
> done today.
Seems like a good idea. The first option shouldn't be named "device
table", but instead "permission table", and the file device_table.txt
could be renamed as well to permission_table.txt.
We should also preserve the fact that those two options can be lists,
so that one can keep the original permission table, and add some more
entries by specifying a second table.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-05-17 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 21:43 [Buildroot] [git commit] Allow several device tables and split in two parts our device table Thomas Petazzoni
2011-05-17 7:04 ` Thomas Petazzoni
2011-05-17 8:43 ` Peter Korsgaard
2011-05-17 8:55 ` Thomas Petazzoni [this message]
2011-05-17 9:42 ` Peter Korsgaard
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=20110517105509.5521276b@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.