Hi, Thanks for your comments!
On Sun, Dec 26, 2021 at 07:00:31PM +0100, Patrick Wildt wrote: > On Sun, Dec 26, 2021 at 08:19:49AM -0300, Crystal Kolipe wrote: > > * Although the USB root hubs are detected, external USB devices don't seem > > to be detected when connected. > > That can have multiple reasons. If you have a device that lights up > upon power supply only, use that to find out if the USB device is > powered at all. Maybe it just doesn't supply power to the device. There definitely seems to be a USB power supply issue. I connected a USB analyser to the Pinephone and got the following results: Booted into MP kernel after crash, with just the analyser connected: No voltage or current draw detected. Booted into MP kernel after crash, with the analyser and dock connected: No voltage or current draw detected. Booted into SP kernel, with just the analyser connected: 3.56 volts, 0.06 amps. Booted into SP kernel, with the analyser and dock connected: 3.54 volts, 0.10 amps. Booted into Linux kernel, with just the analyser connected: No voltage or current draw detected. Booted into Linux kernel, with the analyser and dock connected: 5.15 volts, 0.05 amps. I've also noticed that when booted into the OpenBSD kernel: * The phone works on AC power. * The phone works on battery power. But: * The battery does NOT charge. My first wild guess is that the USB controller might be being configured in 'peripheral' mode, rather than 'host' mode. > You can try 'usb start' in U-Boot to see if that changes things. Unfortunately U-boot just reports 'No working controllers found'. > > * The backlight for the display illuminates during boot, around the point > > of "lcd-controller" at simplebus0 not configured. > > Yeah, we have code for the backlight, but we don't have *any* other code > for graphics output on Allwinner-based systems. If U-Boot sets up a > framebuffer, we can use it. Do we even have any documentation for the display hardware in the A64 SoC? I don't mean the Mali GPU, I just mean enough to get un-accelerated plotting working. It might be worth noting that the recently announced Pinephone Pro uses a Rockchip SoC based on the RK3399. I've just tested the HDMI output on a Rock-PI 4a, (which uses an RK3399), running OpenBSD, and it works quite well, (although the console is very slow when scrolling). Since a phone is obviously not going to be much use without the on-board graphics hardware working, (unlike an SBC, which might be accessed exclusively over the network), I'm wondering if it might be worth waiting to see if the Pinephone Pro would be a much easier target for such a portable OpenBSD machine, rather than investing a lot of time on the current Pinephone model? On the other hand, I suspect that many current users of the Allwinner-based Pinephone will be tempted to replace it with a Pinephone Pro, given that the performance of the various Linux distributions available for it is not exactly stella. This could easily lead to a glut of the original model being available at low cost on the used market. OpenBSD could potentially run quite well on that hardware, even if we only had un-accelerated framebuffer console. Bear in mind that a physical keyboard is, (or will be soon), available for it, so we wouldn't even need touchscreen support in order to get a pocketable OpenBSD PDA. > So you might want to find out why sxirsb(4) isn't working well. I'll have a look at the code today.
