drivers/video: drop framebuffer size constraints

The limit 1900x1200 do not match real world devices (1900 looks like a
typo, should be 1920). But in practice the limits are arbitrary and do
not serve any real purpose. As discussed in "Increase framebuffer size
to todays standards" thread, drop them completely.

This fixes graphic console on device with 3840x2160 native resolution.

Suggested-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Marek Marczykowski-Górecki authored and Jan Beulich committed 2019-05-13 10:13:24 +02:00
1 parent 343459e34a
commit 19600eb75a
1 file changed
-10
-10
View File
@@ -10,9 +10,6 @@
#include "lfb.h"
#include "font.h"
#define MAX_XRES 1900
#define MAX_YRES 1200
struct lfb_status {
struct lfb_prop lfbp;
@@ -146,13 +143,6 @@ void lfb_carriage_return(void)
int __init lfb_init(struct lfb_prop *lfbp)
{
if ( lfbp->width > MAX_XRES || lfbp->height > MAX_YRES )
{
printk(XENLOG_WARNING "Couldn't initialize a %ux%u framebuffer early.\n",
lfbp->width, lfbp->height);
return -EINVAL;
}
lfb.lfbp = *lfbp;
lfb.lbuf = xmalloc_bytes(lfb.lfbp.bytes_per_line);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.