From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size
Date: Mon, 19 Feb 2018 10:36:50 +0100 [thread overview]
Message-ID: <20180219093650.avb4xipvflfd2kel@pali> (raw)
In-Reply-To: <20180213174556.GM5453@intel.com>
On Tuesday 13 February 2018 19:45:56 Ville Syrjälä wrote:
> On Tue, Feb 13, 2018 at 06:43:41PM +0100, Pali Rohár wrote:
> > On Tuesday 13 February 2018 18:12:21 Ville Syrjälä wrote:
> > > On Tue, Feb 13, 2018 at 05:04:37PM +0100, Pali Rohár wrote:
> > > > So it can be done only once after reboot? Or only prior to booting kernel?
> > >
> > > Never.
> >
> > Never? Now I'm lost. Why then dmesg message instruct user to try set up
> > it in BIOS if you say it is never possible?
>
> You can change it in the BIOS. No way to change it from the operating system.
Hi! Can you explain it a bit more?
What does it mean "in BIOS"? Prior switching from 16bit real mode to
protected or long? Or before exiting EFI boot services? Or before
booting kernel (when initialize memory mapping)?
I still do not see reason nor understand why this cannot be possible
either in bootloader (e.g. grub2) or prior to loading bootloader which
runs in protected or long mode.
It is because BIOS uses some undocumented call/procedure which sets that
amount of memory and it is unknown how to do it?
--
Pali Rohár
pali.rohar@gmail.com
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-19 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:21 Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size Pali Rohár
2018-02-13 8:50 ` Pali Rohár
2018-02-13 13:27 ` Ville Syrjälä
2018-02-13 13:38 ` Pali Rohár
2018-02-13 15:36 ` Ville Syrjälä
2018-02-13 16:04 ` Pali Rohár
2018-02-13 16:12 ` Ville Syrjälä
2018-02-13 17:43 ` Pali Rohár
2018-02-13 17:45 ` Ville Syrjälä
2018-02-19 9:36 ` Pali Rohár [this message]
2018-02-21 13:28 ` Ville Syrjälä
2018-02-21 13:34 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180219093650.avb4xipvflfd2kel@pali \
--to=pali.rohar@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox