From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] rtl8188eu: new package
Date: Tue, 21 Jul 2015 22:57:24 +0200 [thread overview]
Message-ID: <20150721225724.401300ef@free-electrons.com> (raw)
In-Reply-To: <55AE72C8.10405@lucaceresoli.net>
Luca,
On Tue, 21 Jul 2015 18:26:48 +0200, Luca Ceresoli wrote:
> > Can you respin a new version? In the mean time, I'll mark this one as
> > "Changes Requested" in patchwork.
>
> It's on my todo list.
>
> However, I still haven't understood your opinion about using mdev
> without devtmpfs (it's for firmware loading in this case)...
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.
Now, I'm wondering if we should simply make the "mdev" /dev management
option work with both static /dev *and* devtmpfs, or if we should have
something like "mdev with static /dev" and "mdev with devtmpfs".
Do you have some proposals?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-21 20:57 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 [this message]
2015-07-22 10:17 ` Luca Ceresoli
2015-07-22 11:26 ` Thomas Petazzoni
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=20150721225724.401300ef@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.