From owner-freebsd-arm@freebsd.org Fri Feb 14 10:10:13 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C5CB4245BF6 for ; Fri, 14 Feb 2020 10:10:13 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Jpz8693Jz4LJX for ; Fri, 14 Feb 2020 10:10:11 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from tails.home (lfbn-idf2-1-900-181.w86-238.abo.wanadoo.fr [86.238.131.181]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 948c2d27 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 14 Feb 2020 10:10:10 +0000 (UTC) Date: Fri, 14 Feb 2020 11:10:09 +0100 From: Emmanuel Vadot To: Klaus =?ISO-8859-1?Q?K=FCchemann?= Cc: Klaus =?ISO-8859-1?Q?K=FCchemann?= via freebsd-arm , Mark Millard Subject: Re: u-boot-rpi* has the existing "make first page reserved" code (shown); this appears to be where any fix would go (it works without FreeBSD changes) Message-Id: <20200214111009.944ce2587a0a4d22ac567da8@bidouilliste.com> In-Reply-To: <2DC3F5F2-11EB-44A4-BC45-F5A1E92B509B@googlemail.com> References: <7E7605DC-021D-448A-8459-8EC26BA9836D.ref@yahoo.com> <7E7605DC-021D-448A-8459-8EC26BA9836D@yahoo.com> <36CF6E4B-5607-4752-B2DF-C265BCFB95BA@yahoo.com> <1BE59567-E669-4A88-8389-2E321B0AC1AE@yahoo.com> <27BE7BAF-FD2C-41C6-B270-4BAF77D1FB0C@yahoo.com> <7465BC0D-3F4C-4CD9-B614-0DF321C94331@yahoo.com> <876C4DBE-A243-425A-9978-209C24387668@yahoo.com> <32D0E068-2E1E-46AA-A907-7974BF4DC46D@yahoo.com> <2DC3F5F2-11EB-44A4-BC45-F5A1E92B509B@googlemail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48Jpz8693Jz4LJX X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=bidouilliste.com; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-3.45 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-1.16)[ip: (-7.99), ipnet: 212.83.128.0/19(2.00), asn: 12876(0.22), country: FR(0.00)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2020 10:10:13 -0000 On Fri, 14 Feb 2020 10:54:40 +0100 Klaus K=FCchemann via freebsd-arm wrote: >=20 > > Am 14.02.2020 um 02:16 schrieb Mark Millard : > >=20 > > [The sysutils/u-boot-rpi* change is sufficient to > > be a work around allowing existing FreeBSD versions > > to be used (up to other separate problems).] > > ? > > .. > >=20 > > (I make no claim to know the best direction for a > > long term fix.) > >=20 > >=20 > > =3D=3D=3D > > Mark Millard > > marklmi at yahoo.com > > ( dsl-only.net went > > away in early 2018-Mar) >=20 >=20 > Hi, >=20 > I really like that you investigate in solving the breakage, thank you! > But your workflow is somewhat in the downstream direction > where it should be on the upstream. > sysutils/u-boot-rpi* Is somewhat outdated . U-boot is currently v2020. 0= 1 , > so the direction should be to 1st upgrade sysutils/u-boot to v2020. 01. I have hold off the upgrade to 2020.01 as rockchip u-boot needs a newer ATF and they didn't made a new release yet. My plan is to wait until 2020.04 is release and if at that time there is still no new ATF release just update the ports to use the latest git version. > After that you ?test" 2020.01 , then if necessary you hack it, send a pat= ch=20 > to fbsd-u-boot, and if that patch would be universal to u-boot , fbsd wil= l send the=20 > patch to u-boot itself( if not yet available there). Mhm no, I will not send patch upstream for someone else, I will also not include patch in the freebsd ports tree that haven't been submitted upstream. > Or vice versa fbsd will upgrade 2020.01 with a current patch from u-boot = upstream . > So the first place where you should look for is the u-boot upstream. > The reason for that is that if we all hack our own versions we will compl= etely=20 > out of sync.=20 > AFAIK ?manu' ( e.g. https://reviews.freebsd.org/D23592 ) is responsible= =20 > for syncing upstreams, I would recommend you to contact him to ask where = and when he wants to go > with u-boot and the DTBs and so on. > I hope this helps a little to send your work to the right addresses? >=20 > If you do sync your work with the upstream you absolutely have the right = to claim your "long term fix? . ;-) >=20 >=20 > Regards > Klaus > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Emmanuel Vadot