Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.

2019-03-04 Thread Andreas Schwab
s/comman/common/ in the subject. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.

2019-02-25 Thread Johan Hovold
On Fri, Feb 22, 2019 at 11:41:40AM -0800, Atish Patra wrote: > Currently, we set hwcap based on first valid hart from DT. This may not > be correct always as that hart might not be current booting cpu or may > have a different capability. > > Set hwcap as the capabilities supported by all possible

Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.

2019-02-24 Thread Anup Patel
On Sat, Feb 23, 2019 at 1:11 AM Atish Patra wrote: > > Currently, we set hwcap based on first valid hart from DT. This may not > be correct always as that hart might not be current booting cpu or may > have a different capability. > > Set hwcap as the capabilities supported by all possible harts w

[v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.

2019-02-22 Thread Atish Patra
Currently, we set hwcap based on first valid hart from DT. This may not be correct always as that hart might not be current booting cpu or may have a different capability. Set hwcap as the capabilities supported by all possible harts with "okay" status. Signed-off-by: Atish Patra --- arch/riscv