From nobody Sun Sep 04 14:00:35 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MLCwT0HMJz4bmfm for ; Sun, 4 Sep 2022 14:00:41 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MLCwR6XQzz3Yds for ; Sun, 4 Sep 2022 14:00:39 +0000 (UTC) (envelope-from void@f-m.fm) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 941BD32008FD for ; Sun, 4 Sep 2022 10:00:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 04 Sep 2022 10:00:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm1; t= 1662300037; x=1662386437; bh=OzUC6br8sQT85zrRNo1PswN/ddldZs/kJXw qgm/1ghc=; b=YasRusATMDfQ5Qw5JFt0IvPSOb3VpIR6099MTS1LmkreD7HfGsc dMwWtTOAGnnbLhl6TeaCtAqHnkzHkYjX4SujY0kdLaTo8Ql28R/uxfH6TZ1S0LPU VxTwJWmchIUawZjc/v7wMtgX8SOxY8yMmZDTesM6yWXK2qPX7EW5zfcj7ov6aWnT bwUpVI0c+uzkHPihw0DSwb5MTnWRXcjUVqIQuUnq445QoUTUkUWTKhWWqHEGFyI9 boru88w2rtxFMUhu0imNczURlKgRAKSUGdHw/AtbleKKKtfk2tFP3pypPkvfHpe4 mkcC+/KNg/cN6YPwFDOsexPikSlmlX5MBng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1662300037; x= 1662386437; bh=OzUC6br8sQT85zrRNo1PswN/ddldZs/kJXwqgm/1ghc=; b=0 c/261/fSe8X3Es9nlYgX+HcuFEOzVG1+rrPBSiYsyb7bPu30xswkVQirKAS4oOuw NibHu718kITUWDZSIcFIaKmdyQ3D+00P4uTENN+wEqUk73QIHjF8hz2DS9TeWdEj 8N0tPo2k+Wb+okHCe0K7D1QVQf+0NpILihIjA+lRQQwds35I6u/SRcnfYT+a1jja B72gcvXAAxNrMkihzFY/NLHHyBCtLiLa2NvJdqsxyRW1C/wPhLBpo5XhEyFjgYUs N4/CwXTWwLAZQarHh0yxzSv5nbo4+/cpVsBQscDGhhF1V7abmFKM17AVwiyKMapB e3ODuTySqJzlfSOEW2Nww== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdelgedgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepudfhkeeuteegvefggeegiedutdfggfekffduleeitdevveefhedtledtkeevle egnecuffhomhgrihhnpehrrghsphgsvghrrhihphhirdgtohhmnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 4 Sep 2022 10:00:36 -0400 (EDT) Date: Sun, 4 Sep 2022 15:00:35 +0100 From: void To: freebsd-arm@freebsd.org Subject: can freebsd utilise gpu split memory on rpi4 Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Rspamd-Queue-Id: 4MLCwR6XQzz3Yds X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=YasRusAT; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="0 c/261/"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.25 as permitted sender) smtp.mailfrom=void@f-m.fm X-Spamd-Result: default: False [-5.07 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.966]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.25:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N Hi, tl;dr : I'm trying to make a freebsd desktop configuration for rpi4b. Is freebsd able to utilise the GPU part of the raspberry pi 4b? In config.txt there can be a GPU_MEM statement for a variable size, the remaining memory being used by the CPU. Would it make sense to set this as large as possible for a desktop environment, or will it simply subtract from available memory and not be used, or does it not have any effect at all in freebsd/xorg ? GPU memory split appears under legacy options. https://www.raspberrypi.com/documentation/computers/config_txt.html#legacy-options it's not clear to me if these would even work under latest firmware. --