From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f53.google.com (mail-pj1-f53.google.com [209.85.216.53]) by mx.groups.io with SMTP id smtpd.web12.51.1623879946490715243 for ; Wed, 16 Jun 2021 14:45:46 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=aYN5BLzu; spf=pass (domain: gmail.com, ip: 209.85.216.53, mailfrom: df7729@gmail.com) Received: by mail-pj1-f53.google.com with SMTP id k7so2544775pjf.5 for ; Wed, 16 Jun 2021 14:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=bFOcJaESdiDzWqML86t9Sq0gHapumb/SvqRkKQM4GDM=; b=aYN5BLzukkdvPULvRADwFfzUVwp2AjYQLksyi2cJ1B86/Wv4kQJ8Y/4Pz/kPSOwkMr /OONAJuZmuZOfp53KQYJwfc2zLrmbcPnaF+wa17RbTakpLJ86XC9ZEEPxRkXkmtLHkPm 4aqVL6cdn/k3Oh1R8BR+HuIbYnP7/dr5sU/5esy/rW4q56SWWybW9+Tbef95q/rYlmwS RE34ZWohxXgS8KDCsVbiGwIRBjie23qTPbYDkHRTN9V62BU+9FO5AiO6FiUngdt+kp7j tvlq3/FipcvJExT4IxJalPJjswQP/lB0iLvGhnKHFfZQsHesrIdSWiNa0WTBnn77baCo WM4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=bFOcJaESdiDzWqML86t9Sq0gHapumb/SvqRkKQM4GDM=; b=AimmoI5gLZMAvX8etRJAS47rjZO7GJLtACbGPTkHTnPNHT154D7SZgcorqxRroPiT1 /owqjF/RO2H/xYkRNgkF93lOGc7GsaB/0y/112BitkXeYVcyAAAURMyPPNDGitQqjFWX uzpJxCikBXpzVSysP5kn3uK1QoyLwHXDAqOukLAqSoSh4p4zKenFBKGToe7qlCJF7wNT HnLONXnf0x4RV2dKhNA/93RzYwxGLEt6zVCo+D/MpZzyURfa76yunfGP3Csl8n4t1LGP zgop42TsFRSCWpL738vVtZHB3Z7oU5xdAyxPaibs9aSLrfrnWe7zvHvP/3gQrvceRu3T 3Qbw== X-Gm-Message-State: AOAM533CDxJl0OtMKLwHOD9TKDQ6CC3tXeHXoyn0O0ucfQv+DKm2dL+x Hr486HDxg/He0dKAdBj7wqObpraiVOp1mPyVQdZtvF1PTZw= X-Google-Smtp-Source: ABdhPJzNyJOEjpFLljmuEKmrrsb2k14F9JBt4pJ/IYuoNvenf4rJUxAzJU1Ckpo0rr2Dxovaj8pS62or9Ghp53GifzE= X-Received: by 2002:a17:90a:d3d2:: with SMTP id d18mr13057316pjw.102.1623879945706; Wed, 16 Jun 2021 14:45:45 -0700 (PDT) MIME-Version: 1.0 References: <1688FC67A39CB5DB.19105@groups.io> In-Reply-To: <1688FC67A39CB5DB.19105@groups.io> From: "David F." Date: Wed, 16 Jun 2021 14:45:33 -0700 Message-ID: Subject: Re: [edk2-devel] SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution To: devel@edk2.groups.io Content-Type: text/plain; charset="UTF-8" Also, I found if there are 2 GOP handles and you change the mode of one, the other one doesn't reflect the change (but still doesn't solve anything with the original question), are you supposed to set the mode on every handle to keep that part in sync? On Tue, Jun 15, 2021 at 11:33 PM David F. via groups.io wrote: > > Hello, > > I've found that most implementation of UEFI don't automatically change > the resolution when setting the mode with STOP (Simple Text Output > Protocol) . You can use GOP to change it after the mode but that > causes other problems. For example, using surface pro 7 in this case, > with 4K screen. The default text mode is 342x96 which puts it in > 2736x1824 mode which you'd expect and the text is tiny. But now you > set the mode to 0 which is 80x25 and it actually sets the mode to > 2736x1824 if not already in that resolution and uses a 80x25 area in > the center of the screen, still tiny text you can hardly read. If you > then say you want GOP in 640x480 mode (which is available as GOP mode > 1 on this system, it will make the font larger but you can't see > anything because it's still offset to the middle of the 2736x1824 area > and you're only seeing the 640x480 upper left of that area on the > screen. Likewise if you have it in 342x96 so it's fully in the upper > left corner of the screen and change the mode to say 800x600 > (available as GOP mode 2 on this system) it will make the text > readable but the text can go off the screen in both directions because > it's still 342x96 when the 100x31 STOP mode would be the correct one > (which happens to be mode 2 on this system). > > Shouldn't setting the STOP mode handle adjusting the resolution since > that's the main reason you want to change the mode so the size shown > on the screen changes to something you can read. > > Any tricks? I've tried a bunch of things, resetting the controller, > using the Reset() protocol function, and other things but nothing > works. As soon as you use STOP to set the mode, it is back to high > resolution and using an area centered in the screen and changing the > resolution after that leaves it in the area centered in the high res > screen and not in the upper left area. > > Thanks. >