From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] CI: Protect Debian Ports targets by KFAIL
Date: Mon, 31 Jan 2022 18:52:04 +0300 [thread overview]
Message-ID: <3b8c5109-2447-f681-7157-88b2bce80af7@ilbers.de> (raw)
In-Reply-To: <20220131094322.1026434-1-amikan@ilbers.de>
31.01.2022 12:43, Anton Mikanovich wrote:
> Debian Ports provides unofficial architectures support which not always
> stable enough.
> Currently few sifive-fu540-sid-ports recipes fail with:
>
> opensbi-0.9/lib/sbi/sbi_tlb.c: Assembler messages:
> opensbi-0.9/lib/sbi/sbi_tlb.c:175: Error: unrecognized opcode `fence.i'
> ...
> ../arch/riscv/include/asm/timex.h: Assembler messages:
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a5,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a1,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a1,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr t4,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a5,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a5,0xc01'
> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr a2,0xc01'
>
> To not block other targets cover both sid-ports targets with KFAIL.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
Applied to next.
prev parent reply other threads:[~2022-01-31 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 9:43 Anton Mikanovich
2022-01-31 9:45 ` Anton Mikanovich
2022-01-31 10:31 ` Jan Kiszka
2022-01-31 15:52 ` Anton Mikanovich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b8c5109-2447-f681-7157-88b2bce80af7@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox