> On Jun 20, 2018, at 4:25 PM, Jason Thorpe <thor...@me.com> wrote: > >> On Jun 20, 2018, at 9:56 AM, Jared McNeill <jmcne...@invisible.ca> wrote: >> >> On Wed, 20 Jun 2018, Jason Thorpe wrote: >> >>> ofctl(8) is pretty useless for this purpose because it doesn't show you >>> which driver instance has attached to a given device tree node. As for >>> passing generic boot args, it's not obvious how one does that on the RPI >>> (and I don't even see the hook that processes the generic boot args >>> bcm283x_platform). >> >> https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md > > Sure, but where is the code for the brcm2835 platform that *processes* it? I > see stuff for parsing console / fb options, but not for standard boot flags.
Firmware puts the string in /chosen/bootargs and we pick it up here: https://nxr.netbsd.org/xref/src/sys/arch/evbarm/fdt/fdt_machdep.c#378 <https://nxr.netbsd.org/xref/src/sys/arch/evbarm/fdt/fdt_machdep.c#378> The standard args are then processed here: https://nxr.netbsd.org/xref/src/sys/arch/evbarm/fdt/fdt_machdep.c#491 <https://nxr.netbsd.org/xref/src/sys/arch/evbarm/fdt/fdt_machdep.c#491>