From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: image.bbclass: USE_DEVFS is now useless
Date: Tue, 01 Apr 2014 20:34:15 +0100 [thread overview]
Message-ID: <1396380855.2910.34.camel@ted> (raw)
In-Reply-To: <533AFEE9.6050001@windriver.com>
On Tue, 2014-04-01 at 13:01 -0500, Mark Hatle wrote:
> On 4/1/14, 12:51 PM, Richard Purdie wrote:
> > On Tue, 2014-04-01 at 18:48 +0100, Phil Blundell wrote:
> >> Also note that the default for USE_DEVFS was (and is) 1, so the lack
> >> of this check is actually causing a difference in the default
> >> behaviour. If there's no appetite for reinstating the USE_DEVFS
> >> mechanism per se then it seems like it would be a good idea to make
> >> the default IMAGE_DEVICE_TABLE be blank in order to restore the
> >> previous default of no /dev in the rootfs.
> >>
> >> At present you get a somewhat arbitrary-seeming smattering of devices
> >> from meta/files/device_table-minimal.txt, including such anachronisms
> >> as /dev/ttySA0 and /dev/apm_bios. It's hard to imagine that anybody
> >> actually wants this stuff in their rootfs in this day and age.
> >
> > Can we kill apmd at the same time? Please? :)
>
> Isn't this still used on some ARM and MIPS targets? (they emulate apm for basic
> power management.)
Its not gone as far as I know but whether we need the userspace portion,
I'm not so sure, it just does suspend/resume event notifuication afaik
these days and I doubt much uses that now. The battery interfaces were
long since replaced with proper sysfs ones.
Cheers,
Richard
next prev parent reply other threads:[~2014-04-01 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 11:11 image.bbclass: USE_DEVFS is now useless Matthieu CRAPET
2014-04-01 17:44 ` Phil Blundell
2014-04-01 17:48 ` Phil Blundell
2014-04-01 17:51 ` Richard Purdie
2014-04-01 18:01 ` Mark Hatle
2014-04-01 19:34 ` Richard Purdie [this message]
2014-04-01 21:29 ` Phil Blundell
2014-04-02 8:47 ` Paul Eggleton
2014-04-02 8:08 ` Laurentiu Palcu
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=1396380855.2910.34.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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.