On 29 August 2014 22:04, Arnd Bergmann <arnd@xxxxxxxx> wrote:
> You mentioned that the 'boot_device' variable in your code snippet
> comes from a hardware register that can be accessed easily, right?
> A possible way to handle it would then be to have two DT entries
> like
>
> nvram@1c000000 {
> compatible = "bcm,bcm4710-nvram";
> reg = <0x1c000000 0x1000000>;
> bcm,boot-device = BCMA_BOOT_DEV_NAND;
> };
>
> nvram@1c000000 {
> compatible = "bcm,bcm4710-nvram";
> reg = <0x1e000000 0x1000000>;
> bcm,boot-device = BCMA_BOOT_DEV_SERIAL;
> };
This sounds like a nice consensus for me! Actually it seems to be
similar to what we already do for other hardware parts.
E.g. in bcm4708.dtsi Hauke put registers location of 4 Ethernet cores
(gmac@0, gmac@1, gmac@2, gmac@3). I believe this board is ready for 4
Ethernet cores so DT matches hardware capabilities. Then most vendors
use/activate only one (maybe up to 2?) Ethernet cores. It's up to the
driver to detect if core is activated/used.
AFAIU having two flash mappings (as suggested above) would follow this
logic. It would match hardware capabilities. And then it would be up
to driver to detect which one mapping is really in use for this
particular board.
Does it make sense?
--
Rafał
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
