On 2013-10-29 19:19 (GMT-0400) Felix Miata composed:
On 2013-10-29 13:54 (GMT+0100) Daniel Vetter composed:
Userspace modesetting is known to be racy and broken, so people don't
really want to waste time on digging into bugs which are most likely
flukes. But if you can bisect this issue to a
On 2013-10-29 13:54 (GMT+0100) Daniel Vetter composed:
Felix Miata wrote:
On 2013-10-29 09:51 (GMT+0100) Daniel Vetter composed:
>Felix Miata wrote:
>>Pre-KMS it used to be that common vga= modes were useless, so I took to
>>using 0x121 to escape from 80x25 screens. Using 0x8121 require
On Tue, Oct 29, 2013 at 08:00:20AM -0400, Felix Miata wrote:
> On 2013-10-29 09:51 (GMT+0100) Daniel Vetter composed:
>
> >Felix Miata wrote:
>
> >>Pre-KMS it used to be that common vga= modes were useless, so I took to
> >>using 0x121 to escape from 80x25 screens. Using 0x8121 required specifyin
On 2013-10-29 09:51 (GMT+0100) Daniel Vetter composed:
Felix Miata wrote:
Pre-KMS it used to be that common vga= modes were useless, so I took to
using 0x121 to escape from 80x25 screens. Using 0x8121 required specifying
an appropriate font via config file. Even after KMS began, vga=0x8121
co
On Tue, Oct 29, 2013 at 9:37 AM, Felix Miata wrote:
> Pre-KMS it used to be that common vga= modes were useless, so I took to
> using 0x121 to escape from 80x25 screens. Using 0x8121 required specifying
> an appropriate font via config file. Even after KMS began, vga=0x8121
> continued to work, an
Embedded Dell motherboard/video BIOS has very limited VESA support!!!
(F00:80x25=VGA, F01:80x50=VGA, F02:80x43=VGA, F03:80x28=VGA, F05:80x30=VGA,
F07:80x60=VGA, 309:132x25=VESA, 30A:132x43=VESA, 30B:132x50=VESA,
30C:132x60=VESA, (8)120:132x25=BIOS, (8)121:132x43=BIOS, (8)122:132x50=BIOS,
(8)123
