Date: Mon, 23 Dec 2019 08:58:47 -0800 From: Mark Millard <marklmi@yahoo.com> To: Greg V <greg@unrelenting.technology> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Attempt to update Rock64 to head -r355976 failed to boot afterwards, anyone have a recent FreeBSD booting a Rock64? Message-ID: <DAA86131-0A36-4DD4-AE0D-5DAD3A364772@yahoo.com> In-Reply-To: <56255a99-0280-4ca0-a1ce-f6b725b2915f@localhost> References: <78081E30-3758-46F3-A228-02B29CDAA6A6.ref@yahoo.com> <78081E30-3758-46F3-A228-02B29CDAA6A6@yahoo.com> <20191222113844.9385de125afd10e86358bc98@bidouilliste.com> <3C550401-A5BF-441E-81E6-29D5D917302B@yahoo.com> <FF778D08-0C49-4181-98B8-371003663F22@yahoo.com> <0AADC2F5-9867-40E7-B4C0-139CA16A3974@yahoo.com> <6DAB33B7-0627-40AA-81DB-9853EAB7FB6D@yahoo.com> <8BA15674-DDF6-4BA2-847D-211ABDFEE94D@googlemail.com> <58BC8D9C-4A3B-495E-8843-E61147D59328@yahoo.com> <A76CE4D3-A188-4CE8-BCAC-C5DD7AE0870D@googlemail.com> <56255a99-0280-4ca0-a1ce-f6b725b2915f@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Dec-23, at 05:19, Greg V <greg at unrelenting.technology> wrote: > . . . >>> One place were I do not have such is the MACCHIATObin >>> Double Shot's ACPI information: That is from software >>> outside the FreeBSD ports. > As > The whole point of ACPI is to get the hell away from OS-specific = anything and embrace standards. My preference for being able to build via ports-mgmt/poudriere-devel = what is not vender-supplied on-the-board (or via buildworld buildkernel) is independent of that, not an argument over DTB vs. ACPI information, u-boot vs. edk2, or other such. Sorry if it appeared otherwise. I'm happy that you provided the edk2 variant that I'm using: thanks. But if/when a FreeBSD port can be used instead, I'll switch to building it = myself via ports-mgmt/poudriere-devel with the other ports that I use. This is = just a personal preference for how to get software. Technically, FreeBSD ports start from software that is "outside the = FreeBSD ports" and make them buildable for FreeBSD via its ports infrastructure. = So=20 my wording was not great at making the distinctions involved. > But sure, my mcbin firmware fork does have a couple hacks, one = FreeBSD-oriented-sort-of (fixing SPCR to describe the UART correctly, = which FreeBSD understands =E2=80=93 upstream it's intentionally wrong to = satisfy Linux) and one PCIe-device-oriented (the hardware is messed up, = devices can get duplicated into many slots, so upstream moved the base = address to only expose the last slot =E2=80=93 but many modern devices = like the RX 480 do NOT get duplicated (!!) so I removed the shift to get = FreeBSD to see the GPU). >=20 > Long term "when I have time" plan is to make this configurable from = the setup UI on the system, but for now.. >=20 > I guess for now if I were to write a Port for building the firmware, I = could make these port options. Sounds reasonable for a port to me. > I'll try making a port soon maybe. Cool if you decide to and end up with the time. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net <http://dsl-only.net/>; went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DAA86131-0A36-4DD4-AE0D-5DAD3A364772>