2014-07-01 0:57 GMT+02:00, Florian Fainelli :
> 2014-06-30 4:30 GMT-07:00 José Vázquez :
>> b43 and b43-legacy drivers enable CONFIG_HW_RANDOM in
>> .config.override; without they selected the "problem" does not happen.
>> More drivers need HW_RANDOM but they were not selected in my owrt
>> config.
2014-06-30 4:30 GMT-07:00 José Vázquez :
> 2014-06-29 22:45 GMT+02:00, Jonas Gorski :
>> On Sun, Jun 29, 2014 at 10:37 PM, José Vázquez
>> wrote:
>>> 2014-06-28 19:54 GMT+02:00, Jonas Gorski :
Ah, I guess your problem is that something in your openwrt config
depends on kmod-random-c
2014-06-29 22:45 GMT+02:00, Jonas Gorski :
> On Sun, Jun 29, 2014 at 10:37 PM, José Vázquez
> wrote:
>> 2014-06-28 19:54 GMT+02:00, Jonas Gorski :
>>>
>>> Ah, I guess your problem is that something in your openwrt config
>>> depends on kmod-random-core, which will cause HW_RANDOM to be selected
>>
On Sun, Jun 29, 2014 at 10:37 PM, José Vázquez wrote:
> 2014-06-28 19:54 GMT+02:00, Jonas Gorski :
>>
>> Ah, I guess your problem is that something in your openwrt config
>> depends on kmod-random-core, which will cause HW_RANDOM to be selected
>> (as m), which makes HW_RANDOM_BCM63XX visible. In
2014-06-28 19:54 GMT+02:00, Jonas Gorski :
>
> Ah, I guess your problem is that something in your openwrt config
> depends on kmod-random-core, which will cause HW_RANDOM to be selected
> (as m), which makes HW_RANDOM_BCM63XX visible. In that case you need
> to either add "# CONFIG_HW_RANDOM_BCM63X
On Sat, Jun 28, 2014 at 7:26 PM, José Vázquez wrote:
> 2014-06-28 18:10 GMT+02:00, Jonas Gorski :
>> On Sat, Jun 28, 2014 at 3:09 PM, José Vázquez
>> wrote:
>> This means your kernel configuration is missing "# HW_RANDOM_BCM63XX
>> is not set" in target/linux/brcm63xx/config-3.10, which is *not*
2014-06-28 18:10 GMT+02:00, Jonas Gorski :
> On Sat, Jun 28, 2014 at 3:09 PM, José Vázquez
> wrote:
> 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, custo
On Sat, Jun 28, 2014 at 3:09 PM, José Vázquez wrote:
> 2014-06-27 13:14 GMT+02:00, Jonas Gorski :
>> On Fri, Jun 27, 2014 at 1:00 PM, José Vázquez
>> wrote:
>>> 2014-06-27 12:29 GMT+02:00, Jonas Gorski :
On Wed, Jun 18, 2014 at 5:34 PM, José Vázquez Fernández
wrote:
> Select HW_RAN
2014-06-27 13:14 GMT+02:00, Jonas Gorski :
> On Fri, Jun 27, 2014 at 1:00 PM, José Vázquez
> wrote:
>> 2014-06-27 12:29 GMT+02:00, Jonas Gorski :
>>> On Wed, Jun 18, 2014 at 5:34 PM, José Vázquez Fernández
>>> wrote:
Select HW_RANDOM_BCM63XX only in the SoCs that support it.
Only B
On Fri, Jun 27, 2014 at 1:00 PM, José Vázquez wrote:
> 2014-06-27 12:29 GMT+02:00, Jonas Gorski :
>> On Wed, Jun 18, 2014 at 5:34 PM, José Vázquez Fernández
>> wrote:
>>> Select HW_RANDOM_BCM63XX only in the SoCs that support it.
>>>
>>> Only BCM6368, BCM6362 and BCM63268 have a hardware random n
2014-06-27 12:29 GMT+02:00, Jonas Gorski :
> On Wed, Jun 18, 2014 at 5:34 PM, José Vázquez Fernández
> wrote:
>> Select HW_RANDOM_BCM63XX only in the SoCs that support it.
>>
>> Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers
>> generator, so, if none of these are selected, don't
On Wed, Jun 18, 2014 at 5:34 PM, José Vázquez Fernández
wrote:
> Select HW_RANDOM_BCM63XX only in the SoCs that support it.
>
> Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers
> generator, so, if none of these are selected, don't compile it.
>
> Tested with BCM6358 and BCM6328 su
Select HW_RANDOM_BCM63XX only in the SoCs that support it.
Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers
generator, so, if none of these are selected, don't compile it.
Tested with BCM6358 and BCM6328 successfully with both 3.10 and 3.14
kernels.
Signed off by: José Vázque
13 matches
Mail list logo
