[BRLTTY] Linux screen driver.

高生旺 coscell at gmail.com
Thu Feb 28 02:32:59 EST 2019


Did you mean that I should patch current kernel and boot with disabled 
unicode parameter?

On Thu, 28 Feb 2019, Dave Mielke wrote:

> [quoted lines by 高生旺 on 2019/02/28 at 10:36 +0800]
>
>> My last working system with 5.6 is patched kernel 2.14 and disable default
>> unicode within booting.
>
> Can you verify that 5.6 still actually does work on it? If so, can you then
> build 6.0 for it and check if it works?
>
> I'm quite sure that charset= has been fixed, and this may be the only way to
> verify it. If we can't then maybe we just need to admit that charset= is no
> longer a viable option and might just as well be removed.
>
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty


More information about the BRLTTY mailing list