On 08/02/2018 03:19 AM, Alexey Brodkin wrote:
> Otherwise kernel uses random MAC which is not very conveniet.
Curious what exactly is the issue - why does the user care what MAC is assigned
?
> With that change in place use might set desired MAC in U-Boot
> with "setenv ethaddr 11:22:33:44:55:66
On 08/02/2018 12:08 AM, Alexey Brodkin wrote:
>> The fault handling is spaghetti mess of checks and more checks and has not
>> really
>> been touched since upstreaming. I need to clean it up and essentially
>> rewrite it
>> for v4.19
> So would you like me to send a re-spin with less changes as d
Hi Linus,
Another batch of fixes for ARC, this time mainly DMA API rework wreckage.
Please pull.
Thx,
-Vineet
--->
The following changes since commit d72e90f33aa4709ebecc5005562f52335e106a60:
Linux 4.18-rc6 (2018-07-22 14:12:20 -0700)
are available in the git reposito
Otherwise kernel uses random MAC which is not very conveniet.
With that change in place use might set desired MAC in U-Boot
with "setenv ethaddr 11:22:33:44:55:66", save environment and
then from boot to boot the same MAC will be used by the kernel.
One other note for this to happen it's required
CONFIG_DEVKMEM by default is disabled so clean-up
our defconfigs.
Signed-off-by: Alexey Brodkin
Cc: Vineet Gupta
Cc: Ofer Levi
---
arch/arc/configs/axs101_defconfig | 1 -
arch/arc/configs/axs103_defconfig | 1 -
arch/arc/configs/axs103_smp_defconfig | 1 -
arch/arc/conf
SWAP support on ARC was fixed earlier by
commit 6e3761145a9b ("ARC: Fix CONFIG_SWAP")
so now we may safely enable it on platforms that
have external media like USB and SD-card.
Signed-off-by: Alexey Brodkin
Cc: sta...@vger.kernel.org # 6e3761145a9b: ARC: Fix CONFIG_SWAP
---
arch/arc/configs/axs1
There's no reason to set the same hostname to all ARC boards
by default. It usually gets overwritten by init scripts anyways.
Signed-off-by: Alexey Brodkin
---
arch/arc/configs/axs101_defconfig | 1 -
arch/arc/configs/axs103_defconfig | 1 -
arch/arc/configs/axs103_smp_defconfi
Hi Vineet,
On Wed, 2018-08-01 at 12:49 -0700, Vineet Gupta wrote:
> Hi Alexey,
>
> I was finally forced to revisit this for my glibc tst-tls3-malloc deadlock.
> And
> indeed with this change we don'tsee the deadlock. But see below..
>
>
> > @@ -139,12 +139,16 @@ void do_page_fault(unsigned lon