Re: NetBSD on rpi0-2w

[adr <adr%sdf.org@localhost>]

On Mon, 1 Apr 2024, Michael van Elst wrote:
> adr%sdf.org@localhost (adr) writes:
>
> > [ 533.1690757] audio0(vcaudio0): setting play.port=0 failed: errno=22
> > Which would be handy in my use case, using an hdmi->av adapter.
>
> Ports are something different. You need to set outputs.select with
> mixerctl. The value 'auto' lets the firmware chose (i.e. it will
> use HDMI if it detects an audio-capable device), 'hdmi' choses
> the HDMI port, 'headphones' the analog output. For some devices
> you also need to force the audio capability in config.txt to make
> HDMI audio work.

No, 0 is the hdmi port, I know about mixerctl &c. The options
to force audio in config.txt doesn't work either.

> > *- Bluetooth is not detected, I supposed it should be this:
> > [     1.799021] (manufacturer 0x2d0, product 0xa9a6) at sdmmc1 function 2 not config
> > ured
>
> Bluetooth is connected to an UART, not SDIO. You need to attach it
> with btattach by configuring an entry in /etc/bluetooth/btattach.conf.
>
> There is also the conflict between bluetooth and console. Both
> want the "full" UART for performance (FIFO) and constant baudrate.
> You have to chose between several compromises.

With this board with the dtb configuring the bluetooth attached to
the primary uart, netbsd configures the serial console to the
secondary uart automatically:

[     1.000004] plcom0 at simplebus1: ARM PL011 UART
[     1.000004] plcom0: txfifo 16 bytes
[     1.000004] plcom0: interrupting on icu irq 57
[     1.000004] com0 at simplebus1: BCM AUX UART, 1-byte FIFO
[     1.000004] com0: console
[     1.000004] com0: interrupting on icu irq 29, clock 800000000 Hz

I can attach the bluetooth driver to the primary uart:

# btattach bcm43xx /dev/dplcom0 921600

I have to experiment, but I was interested in other people experience
to not waste time as with the wifi.

Thanks for the interest, tough.

adr.