> On Dec 15, 2016, at 7:23 AM, Hayward, Shaun <haywshau@xxxxxxxxxx> wrote: > > >> On Dec 15, 2016, at 4:59 AM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: >> >> question is, what is the "appropriate" info to pass to the >> is this a reasonable way to do this? is there a better/standard way? >> and is there a simple example of that in the current kernel source? >> >> rday > > I just (last week) tackled a similar issue. In our case, we used u-boot to detect board type and then load a different device file. This caused our optional device to only be present on the appropriate board (we use udev). We also then used the device tree "model" name from user space to key additional customizations (/sys/firmware/devicetree/base/model, if memory serves me right). > > In this setup, the driver is always in the kernel (we run the same image for both boards), but a device is only registered on boards with the matching device in their device tree. > > Shaun (Forgot to cc list...) _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
