All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] rtl8188eu: new package
Date: Wed, 22 Jul 2015 13:26:36 +0200	[thread overview]
Message-ID: <20150722132636.6fe86008@free-electrons.com> (raw)
In-Reply-To: <55AF6DB2.4090301@lucaceresoli.net>

Luca,

On Wed, 22 Jul 2015 12:17:22 +0200, Luca Ceresoli wrote:

> >> It's on my todo list.
> 
> BTW, I think the rtl8188eu can go on its own way, without waiting for
> the discussion about /dev management, right?

Absolutely, I'll be happy to take rtl8818eu independently from the
discussion on /dev management and firmware loading.

> > I think it's OK to support this case. People using kernels older than
> > 2.6.32 are stuck with static /dev and may have to load firmwares.
> 
> Another use case is to have dynamic /dev management on kernels
> <2.6.32, even without any firmware loading need. mdev is reportedly
> working without devtmpfs. I haven't tested it seriously, but it might
> be very interesting for the poor souls.

Correct. So far I believe Peter's position was that people still using
kernel older than 2.6.32 should simply use static, but maybe that was a
too restrictive decision.

> > Do you have some proposals?
> 
> Idea 1:
>    - just add a new entry to "/dev management":
>        ( ) Static using device table
>        ( ) Static using device table + mdev   <- New option
>        (X) Dynamic using devtmpfs only
>        ( ) Dynamic using {devtmpfs +} mdev    {} = new wording only
>        ( ) Dynamic using {devtmpfs +} eudev   {} = new wording only
> 
> Idea 2:
>    - Add a new bool named "Use devtmpfs"
>      - y (default) -> enable devtmpfs in the kernel config
>      - n           -> use the static device table
>    - Change "/dev management" to "dynamic /dev management":
>        ( ) none
>        (X) mdev
>        ( ) eudev

I think I prefer idea (1) here. It's closer to what we already have,
and as you say, it's probably clearer for the user / easier to document.

Our manual has a complete section about /dev management at
http://buildroot.org/downloads/manual/manual.html#_dev_management, so
this will have to be updated.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-07-22 11:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 13:09 [Buildroot] [PATCH 1/2] system: allow using mdev for firmware loading only Luca Ceresoli
2015-07-06 13:09 ` [Buildroot] [PATCH 2/2] rtl8188eu: new package Luca Ceresoli
2015-07-06 13:17   ` Thomas Petazzoni
2015-07-06 13:59     ` Luca Ceresoli
2015-07-06 14:36       ` Thomas Petazzoni
2015-07-18 21:30   ` Thomas Petazzoni
2015-07-21 16:26     ` Luca Ceresoli
2015-07-21 20:57       ` Thomas Petazzoni
2015-07-22 10:17         ` Luca Ceresoli
2015-07-22 11:26           ` Thomas Petazzoni [this message]
2015-07-06 13:49 ` [Buildroot] [PATCH 1/2] system: allow using mdev for firmware loading only Thomas Petazzoni
2015-07-06 14:08   ` Luca Ceresoli

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=20150722132636.6fe86008@free-electrons.com \
    --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.