Iain Hibbert writes:
> On Fri, 5 Jan 2024, Brad Spencer wrote:
>
>> I see a few options for doing this, such as simply matching all of the
>> possible children and using sysctl to enable the one you want. Probably
>> followed by a rescan call. That seems ugly, however. The use of
>> 'drvctl
Brad Spencer writes:
> I don't know just yet, but there might be unwanted device reset the "use
> the one you open" technique. That is, you might have to reset the chip
> to change mode and if you support say, I2C and GPIO at the same time
> (which is possible), but then change to just GPIO the
m...@goathill.org (MLH) writes:
> Brad Spencer wrote :
>
>> It has a built in UART which is a separate USB device and then
>> a USB device that can be programmed to provide I2C,
Hello...
> What are you using to flash these devices?
No flashing of anything is needed to use the I2C mode. All
On Fri, 5 Jan 2024, Brad Spencer wrote:
> I see a few options for doing this, such as simply matching all of the
> possible children and using sysctl to enable the one you want. Probably
> followed by a rescan call. That seems ugly, however. The use of
> 'drvctl -r -a ' seemed to hold promise.
On 1/6/24 08:33, Emile 'iMil' Heitor wrote:
To support this, I've attached `virtio*` to a newly created bus,
`cmdlinebus?` which is attached to mainbus in amd64_mainbus.c
I am not entirely sure this is the cleanest way to proceed and
would like to have your feedback.
I like the design of
