Date: Sun, 05 Jun 2022 17:31:46 +0000 From: greg@unrelenting.technology To: "Otacilio" <otacilio.neto@bsd.com.br>, "Ronald Klop" <ronald-lists@klop.ws> Cc: freebsd-arm@freebsd.org Subject: Re: Wrong number of CPUs detected on RPI3 and FreeBSD 13.1 Message-ID: <fcc4ea957a6e9e4f104780346c9c61ed@unrelenting.technology> In-Reply-To: <c9a9cd2a-9386-ce2e-6319-def8a801ac57@bsd.com.br> References: <c9a9cd2a-9386-ce2e-6319-def8a801ac57@bsd.com.br> <8fcbebf4-60c3-0ccb-259b-3324b123245c@bsd.com.br> <1047394639.643.1654181685742@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
June 5, 2022 2:18 PM, "Otacilio" <otacilio.neto@bsd.com.br> wrote:=0A=0A>= After some debug I found that this routine is returning -1:=0A> =0A> Som= eone can give-me a hint about the function of psci_callfn ?=0A=0APSCI is = an interface for calling into power management firmware.=0AJust saying th= at *a* PSCI call failed is not informative, we really need the arguments = of the call.=0A=0AI'm not sure what firmware you have on the SD card but = armstub8 from=0Ahttps://github.com/gonzoua/rpi3-psci-monitor should suppo= rt:=0APSCI_VERSION, PSCI_CPU_ON, PSCI_SYSTEM_OFF, and PSCI_SYSTEM_RESET.= =0AWhich should be all the calls that FreeBSD ever does=E2=80=A6
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fcc4ea957a6e9e4f104780346c9c61ed>