support for HW_SKIP_CONSOLE breaks use by blind people

[Michal Suchanek]

On 9 January 2013 23:51, Samuel Thibault <samuel.thibault at ens-lyon.org> wrote:

>
>> And I don't see that happening by default with the dummy driver.
>
> s/happening/coming back/
>

Since the drivers are probed one by one in order there can be only one
flag. Two flags set by two drivers will never be set both for the
first driver probed.

So a proper fix needs something like:

1) introduce a HW_OPEN_CONSOLE flag which is inverse of the HW_SKIP_CONSOLE flag
2) have all drivers but void and dummy set that - dummy has nice
example of setting a flag
3) have the input hotplug code handle the flag in addition to the init code

This will not link opening the console to the dummy driver again but
to the evdev driver which requires it.

Just backing out HW_SKIP_CONSOLE after years of dummy driver using it
and test suites and applications relying on it is not an option at
this point.

Thanks

Michal