svn commit: r301453 - in head/sys: arm/arm arm64/arm64 dev/fdt dev/gpio dev/iicbus dev/ofw dev/pci dev/vnic kern mips/mips sys

[Nathan Whitehorn]

That's a good idea, Adrian. I've made a wiki page at 
https://wiki.freebsd.org/Complicated_Interrupts describing this and 
moved the discussion to freebsd-arch@
-Nathan

On 07/24/16 11:48, Adrian Chadd wrote:
> [snip]
>
> Hi,
>
> I think a lot of this whole discussion stems from a reasonably unclear
> shared idea of where intrng is supposed to be going and what it's
> supposed to be doing. I'm sure everyone has their own ideas of what it
> is for their own needs, but this thread shows a clear separation
> between the original writers and people working on supporting their
> own platforms.
>
> So, my suggestion - also so I can understand it, since I kinda need it
> now for the atheros mips ports! - is maybe something gets written up
> in the wiki that's a more detailed technical overview of intrng,
> including the problems its trying to solve. Then, instead of flinging
> things around on the commit mailing list, people edit the wiki and
> discuss on -arm about the specific details.
>
> I think that'll avoid a lot of what's going on.
>
> (And honestly, I'd like it more sorted out sooner rather than later,
> as I really want to start attacking the QCA ARM ports (IPQ4019) if
> it's not already done, and that's all interrupt/gpio/etc gymnastics we
> need INTRNG for.)
>
> So, Nathan, wanna start a wiki page with the /current/ implementation
> that's in -HEAD and what the intention was from the PPC side?
>
>
>
> -adrian
>