RPI4 Install r357606 test 09.02.2020 failed

[Mark Millard]

On 2020-Feb-9, at 20:19, Bakul Shah <bakul at bitblocks.com> wrote:

> On Feb 9, 2020, at 8:10 PM, Mark Millard via freebsd-arm <freebsd-arm at freebsd.org> wrote:
>> 
>> 
>> 
>> On 2020-Feb-9, at 18:32, Bakul Shah <bakul at bitblocks.com> wrote:
>> 
>>> On Feb 9, 2020, at 2:48 PM, Mark Millard via freebsd-arm <freebsd-arm at freebsd.org> wrote:
>>>> 
>>>> If you want a build that works, use the kernel from head
>>>> -r356767 . The next head version ( -r356776 ) is where
>>>> the broken status starts for RPi4 and RPi3. RPi4B's with
>>>> 4 GiBYTes of RAM fail to boot. As I understand, at least
>>>> some forms of RPi3 boot but are messed up, such as only
>>>> running 1 core. (Not surprising given the PSCI version
>>>> problem which happens there as well.)
>>> 
>>> With this version I was able to boot it and log in as root.
>>> Thanks!
>>> 
>>> I don't see any bcm2711 specific files in sys/arm/broadcom/bcm2835.
>>> Is this intentional? pi3 (bcm2838) and pi4 (bcm2711) are rather
>>> different.
>> 
>> The ports:
>> 
>> sysutils/rpi-firmware
>> sysutils/u-boot-rpi4
>> 
>> have the materials that are used, including a .dtb
>> file. There are other
>> 
>> sysutils/u-boot-rpi*
>> 
>> ports as well. The rpi-firmware has materials for
>> all of them.
> 
> Thanks. Yes, I am aware of those and used them as well.
> 
> Sorry, I wasn't clear. I am talking about FreeBSD driver
> code. For example PCIe, XHCI and ethernet code will be
> different. There are other differences as well. Not sure
> all that is captured in the device tree files.

Ahh. These things have not been developed yet. I'm not
sure it is clear what their future is, given the 
documentation status for them and other issues around
RPi*'s and their history for FreeBSD.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)