On Wed 2016-02-24 14:31:33, Johannes Berg wrote:
> On Wed, 2016-02-24 at 13:14 +0100, Pavel Machek wrote:
> >
> > Why would it need to? It could look at default triggers for the led
> > if it really wanted to.
>
> And then it needs to change them; if anything goes wrong error recovery
> is practi
On Wed, 2016-02-24 at 13:14 +0100, Pavel Machek wrote:
>
> Why would it need to? It could look at default triggers for the led
> if it really wanted to.
And then it needs to change them; if anything goes wrong error recovery
is practically impossible since the trigger information is lost
forever.
On Wed 2016-02-24 12:01:37, Johannes Berg wrote:
> On Wed, 2016-02-24 at 11:46 +0100, Pavel Machek wrote:
>
> > If you want different trigger, implement different trigger. If you
> > want to indicate all but wifi, implement all but wifi, and then
> > userspace can select it by writing trigger name
On Wed, 2016-02-24 at 11:46 +0100, Pavel Machek wrote:
> If you want different trigger, implement different trigger. If you
> want to indicate all but wifi, implement all but wifi, and then
> userspace can select it by writing trigger name.
This is still mostly a strawman, since userspace cannot
On Wed 2016-02-24 10:01:49, Johannes Berg wrote:
> On Tue, 2016-02-23 at 22:45 +0100, Pavel Machek wrote:
>
> > Well "the airplane mode" is well defined. It means no intentional
> > transmitting at radio frequencies.
> >
> > The fact that you are allowed to use WIFI on certain flights does not
>