From nobody Sun Sep 11 15:31:21 2022 X-Original-To: freebsd-hackers@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 4MQYby3VNBz4c4fg for ; Sun, 11 Sep 2022 15:31:26 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 4MQYbx2lGwz40hf for ; Sun, 11 Sep 2022 15:31:25 +0000 (UTC) (envelope-from void@f-m.fm) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 89B705C00D0 for ; Sun, 11 Sep 2022 11:31:24 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 11 Sep 2022 11:31:24 -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=fm2; t= 1662910284; x=1662996684; bh=m9f+PaMri3SIHbT2lRUv56SNyYaBKFdg47q feoFXa0M=; b=Luu1T2p2G3Pzb8vnm3R2cLldSr0FjqumubhJUZnZxob1SW/MS2h xpt6Bvwhm1B4rxC531iYWl595HeeuEWpm2RoqSG+3+jMBTTbEqOZDSDmswhqIIfm pKKph5zPmlZERcJgkboqMoCIi93Mn2BRZJqhiwcn9ZMTonlKKsp17torRJfKR/If vRsjINKzKTcStykhuzcvkw1RG8gDGMBxIT8mNUBiZyTx/ZtW/xS8/Trg+AlGdKzV bBXQgL0tRnxagmhJ6F7BnRlqE0/T4vGeYwGAdOEEmnCfdH+c0sCJnK1+4Y77P2Li OYC+uEKYiPeXZb9WwJW+fZxnTogZV1ln/Bw== 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=fm2; t=1662910284; x= 1662996684; bh=m9f+PaMri3SIHbT2lRUv56SNyYaBKFdg47qfeoFXa0M=; b=Q P5LeZ/sDGNDJ91hrIZe00XCuSfWMEFjg99oDzdsrMBUekS7Yai2+JKUwkwBKDHKK RlckPt36eMyx3Qd3wdzlc8oXUlmpjhZzRBTQiHfY/J7zJim+4ly6/mT+PU7YGcAT 4Wd0oYF2z4niZpZIJF55RXZUK6/pLt6sPw5TfDWsLb10PCKT1kuO0kAmHApIg8ut 3FWNxetYWRa4DHFnPNUKw1mitu2hkYPNXrChCMV4fhhNAMCnmS1zZQUFxpqaQCKX Rea+qn5U7pLp6LpcwsP2A6XU1TSYM4ib7MkgCFa1xmfZrdRDUHKH9uZw+sibOBwC Lf0fSHc2ovU01JQUMr5rw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfedutddgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepfeetleevtdeujefguedufedukeegieetheeuieefkeekheeiuefgveeljefhie efnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgpdhrrghsphgsvghrrhihphhirdgt ohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvh hoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 11 Sep 2022 11:31:23 -0400 (EDT) Date: Sun, 11 Sep 2022 16:31:21 +0100 From: void To: freebsd-hackers@freebsd.org Subject: [can freebsd utilise gpu split memory on rpi4] Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Rspamd-Queue-Id: 4MQYbx2lGwz40hf X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=Luu1T2p2; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="Q P5LeZ/"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm X-Spamd-Result: default: False [-5.20 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.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-hackers@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N Hello, Posting this here in the hope that someone might know a bit about arm64 internals in the way cpu/gmu memory split applies or doesn't apply for x11 etc on -current. TIA ----- Forwarded message from void ----- 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 Mail-Followup-To: freebsd-arm@freebsd.org List-Id: Porting FreeBSD to ARM processors 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. -- ----- End forwarded message ----- --