> From: David Gwynne <[email protected]> > Date: Thu, 3 Jan 2019 09:39:29 +1000 > > > On 2 Jan 2019, at 21:16, Mark Kettenis <[email protected]> wrote: > > > >> dlg@o1000 fdt$ dmesg | grep 'not configured' > >> "v2m" at ampintc0 not configured > > > > Hmm, ampintcmsi(4) should attach to that one. Doesn't it attach > > on your machine? Or is there something not quite right in your > > printing logic? > > My build box was still somewhere in 6.3, so it's likely support was > added after I checked out the code. I'm upgrading it now. > > After installing a snap I get: > > ampintcmsi0 at ampintc0: nspi 256
Good!. > >> "clk100mhz_0" at simplebus0 not configured > >> "clk375mhz" at simplebus0 not configured > >> "clk333mhz" at simplebus0 not configured > >> "clk500mhz_0" at simplebus0 not configured > >> "clk500mhz_1" at simplebus0 not configured > >> "clk250mhz_4" at simplebus0 not configured > >> "clk100mhz_1" at simplebus0 not configured > > > > These are clocks that we support without a specific driver that we > > probably should knock out. That can be done later though. > > When you say "knock out" do you mean blacklist matching on them, or > to knock out a small driver to implement the functionality? Probably just blacklist them. But let's wait with that a bit. I'd like to see a few dmesgs with all the "not configured" devices in there. So ok kettenis@ on the diff.
