Re: eeepc-laptop rfkill, stupid question #4

[Matthew Garrett]

On Mon, Nov 03, 2008 at 12:51:45PM -0200, Henrique de Moraes Holschuh wrote:

> Not if you can enter or exit HARD_BLOCK, you're not.  If you cannot it is
> fine.  But if you can, you really need to rfkill_force_state() on resume,

The state can always be overridden by software, so I think we're fine 
there.

> And the rfkill core seems to be buggy when you call force_state() on resume,
> which you guys didn't hit because you're not doing it yet.  See my other
> email...

Just to make sure: in the case where we *don't* support hard blocking, 
there's no need to do anything special in the driver on resume and 
rfkill should (but currently doesn't) do the right thing itself?

-- 
Matthew Garrett | mjg59@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/