[OpenWrt-Devel] [Patch][BCM63XX][V2][RFC] Select HW_RANDOM_BCM63XX only in the SoCs that support it.
ppvazquezfer at gmail.com
Sat Jun 28 13:26:32 EDT 2014
2014-06-28 18:10 GMT+02:00, Jonas Gorski <jogo at openwrt.org>:
> On Sat, Jun 28, 2014 at 3:09 PM, José Vázquez <ppvazquezfer at gmail.com>
> This means your kernel configuration is missing "# HW_RANDOM_BCM63XX
> is not set" in target/linux/brcm63xx/config-3.10, which is *not* an
> issue of the Kernel, but only of your incomplete, custom kernel
> configuration. This would have happened with any missing kernel config
> symbol, and is nothing specific of HW_RANDOM_BCM63XX.
> I guess you just deleted the line from the config-3.10. But the kernel
> config does not work this way - you need to use make kernel_menuconfig
> to change the kernel config symbols, or ensure that you only replace
> values (e.g. "CONFIG_foo=y" <=> "# CONFIG_foo is not set" - the
> important part is that a line containing CONFIG_foo still exists).
>> I'll send COMPILE_TEST patch with the modifications that you recommend
>> to linux-mips because Florian sent the driver to that patchwork two
>> years ago and it was accepted.
> Use scripts/get_maintainer.pl to get the correct people/mailing lists
> to send the patch to. Also use a current kernel tree of course, not
Nop, i used make kernel_menuconfig to deselect HW_RANDOM_BCM63XX and HW_RANDOM.
As you can see in the Kconfig, HW_RANDOM_BCM63XX depends on BCM63XX
so, if it is not selected, sends the aforementioned error. However
SPI_BCM63XX and SPI_BCM63XX_HSSPI can be deselected and the
compilation finishes normally.
P.S.: maybe will be better to forget this patch and leave the things
as they are because the time you are spending don't justify the
"benefits", and could lead to problems in the future.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel