From: Paul Menzel Subject: [Intel 945] BSM: How to determine size of DRAM used for internal graphics? Date: Fri, 30 May 2014 13:45:51 +0200 Message-ID: <1401450351.4834.96.camel@mattotaupa> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0892138884==" Return-path: Received: from mail.gw90.de (mail.gw90.de [188.40.100.199]) by gabe.freedesktop.org (Postfix) with ESMTP id 8243E6E146 for ; Fri, 30 May 2014 05:21:19 -0700 (PDT) Received: from cable-86-56-56-250.cust.telecolumbus.net ([86.56.56.250] helo=mattotaupa.local) by mail.gw90.de with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1WqLGE-0007kM-A2 for intel-gfx@lists.freedesktop.org; Fri, 30 May 2014 11:46:10 +0000 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0892138884== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-GRp2dVIKn+tlsVh7VpcM" --=-GRp2dVIKn+tlsVh7VpcM Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Intel graphics folks, since commit 17fec8a0 [1] drm/i915: Use Graphics Base of Stolen Memory on all gen3+ Linux reads the register BSM (Base of Stolen Memory) directly to get the base address of graphics stolen memory. With coreboot [2] and native graphics init =E2=80=93 note that everything works with the proprietary VGA BIOS/Option ROM =E2=80=93 this causes a regression [3] as this register is = not programmed at all. =46rom the datasheet *Mobile Intel=C2=AE 945 Express Chipset Family* [4] the register BSM is described on page 290. Graphics Stolen Memory and TSEG are within DRAM space defined under TOLUD. From the top of low used DRAM, (G)MCH claims 1 to 64 MBs of DRAM for internal graphics if enabled. This register contains bits 31 to 20 of the base address of stolen DRAM memory. The host interface determines the base of graphics stolen memory by subtracting the graphics stolen memory size from TOLUD. See Device 0 TOLUD for more explanations. Also see Figure 12 *Main Memory Address Range* in section 9.2 on page 325. Unfortunately I am unable to find out how the graphics stolen memory size is determined. I=E2=80=99d have thought it is used for the framebuffer= , but according to page 93 (Graphics Mode select (GMS)) that the framebuffer size can only be 1 MB or 8 MB, which contradicts that it can be up to 64 MB. If it is determined implicitly by the value I set the BSM to, where can I find the recommendations what size to use? I=E2=80=99d guess it is depend= ent on the RAM size, that means dependent if the system has 512 MB or 4 GB for example. Thanks, Paul [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/= ?id=3D17fec8a08698bcab98788e1e89f5b8e7502ababd [2] http://www.coreboot.org/ [3] https://bugs.freedesktop.org/show_bug.cgi?id=3D79038 [4] http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/= mobile-945-express-chipset-datasheet.pdf Document Number: 309219-006 --=-GRp2dVIKn+tlsVh7VpcM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlOIb3oACgkQPX1aK2wOHVheVACghpZ9NQWJ9ZXXp5h0vBOacc7E GVcAoIjzhIk8cZ8kdS1MbBOQPRh1y4ot =5tyY -----END PGP SIGNATURE----- --=-GRp2dVIKn+tlsVh7VpcM-- --===============0892138884== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0892138884==--