t: January 20, 2017 3:11 PM
To: Anindya Mukherjee
Cc: freebsd-current@freebsd.org
Subject: Re: vt(4) chops off the leftmost three columns
hiya,
Mechanically it doesn't look /that/ hard:
* vesa.ko pulls in the vesa.c bits and the syscons vesa control bits.
Ideally we'd have them as two
Thanks! I needed a breakdown like this. I'll need to study the code a bit more.
Anindya
From: Adrian Chadd [adrian.ch...@gmail.com]
Sent: January 20, 2017 3:11 PM
To: Anindya Mukherjee
Cc: freebsd-current@freebsd.org
Subject: Re: vt(4) chops of
Hi Adrian,
I was looking at the source for the vt driver. Wondering how much work it is to
add VESA support to the VGA backend? As you say ATM it's hardcoded to use
640x480. Pardon my ignorance, but can we reuse any VESA code from syscons?
Also, how dependent is splash/screensaver support on th
Good, that makes me feel better :) The system is running fine, so I think
you're right and it's nothing to worry about. Thanks again for your responses.
Best,
Anindya
From: Benjamin Kaduk [ka...@mit.edu]
Sent: January 9, 2017 1:53 PM
To: Anindya
ever
happens.
Best,
Anindya
From: Benjamin Kaduk [ka...@mit.edu]
Sent: January 8, 2017 4:47 PM
To: Anindya Mukherjee
Cc: freebsd-current@freebsd.org
Subject: Re: New Lock Order Reversal in 12.0?
On Mon, Jan 09, 2017 at 12:32:28AM +, Anindya Mukherjee wrote:
> Hi, I'm running
Hi, I'm running 12.0-current and noticed a LOR message from WITNESS which I
couldn't find a report about. I looked at
http://sources.zabbadoz.net/freebsd/lor.html, among other places.
system details:
root@triskelion:~ # uname -a
FreeBSD triskelion 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r311461: Th
