From: Antony Pavlov <antonynpavlov@gmail.com>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC v4 01/10] Add initial RISC-V architecture support
Date: Tue, 3 Oct 2017 01:15:17 +0300 [thread overview]
Message-ID: <20171003011517.11458b57798f7e6d9d07c512@gmail.com> (raw)
In-Reply-To: <cbe5730e-5da4-6379-6cd0-c75feeeafb1a@phytec.de>
On Mon, 2 Oct 2017 12:04:30 +0200
Daniel Schultz <d.schultz@phytec.de> wrote:
> Hi,
>
>
> On 09/30/2017 01:57 PM, Antony Pavlov wrote:
> > On Fri, 29 Sep 2017 14:07:09 +0200
> > Oleksij Rempel <linux@rempel-privat.de> wrote:
> >
> >> Hi,
> >>
> >> hm... mostly looks identical with existing arch
> > What do you mean when you say "existing arch"?
> >
> > ...
> >
> >> Am 29.09.2017 um 01:12 schrieb Antony Pavlov:
> > ...
> >>> diff --git a/arch/riscv/boot/start.S b/arch/riscv/boot/start.S
> >>> new file mode 100644
> >>> index 000000000..2fd00f63d
> >>> --- /dev/null
> >>> +++ b/arch/riscv/boot/start.S
> >>> @@ -0,0 +1,74 @@
> >>> +/*
> >>> + * Startup Code for MIPS CPU
> >>> + *
> >>> + * based on coreboot/src/arch/riscv/bootblock.S
> >>> + *
> >>> + * Copyright (C) 2016 Antony Pavlov <antonynpavlov@gmail.com>
> >>> + *
> >>> + * This file is part of barebox.
> >>> + * See file CREDITS for list of people who contributed to this project.
> >>> + *
> >>> + * This program is free software; you can redistribute it and/or modify
> >>> + * it under the terms of the GNU General Public License version 2
> >>> + * as published by the Free Software Foundation.
> >>> + *
> >>> + * This program is distributed in the hope that it will be useful,
> >>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> >>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> >>> + * GNU General Public License for more details.
> >>> + *
> >>> + */
> >>> +
> >>> +#include <asm-generic/memory_layout.h>
> >>> +
> >>> + .text
> >>> + .section ".text_entry"
> >>> + .align 2
> >>> +
> >>> +.globl _start
> >>> +_start:
> >>> + li sp, STACK_BASE + STACK_SIZE
> >>> +
> >>> + # make room for HLS and initialize it
> >>> + addi sp, sp, -64 /* MENTRY_FRAME_SIZE */
> >>> +
> >>> + # poison the stack
> >>> + li t1, STACK_BASE
> >>> + li t0, 0xdeadbeef
> >>> + sw t0, 0(t1)
> >>> +
> >>> + # clear any pending interrupts
> >>> + //csrwi mip, 0
> >> should be removed.
> > Actually not!
> >
> > I have imported this code from coreboot.
> >
> > I have commented this line because csrwi does not worked in some cases.
> >
> > But I have to make additional investigations on csrwi.
> >
> CSRRWI is part of the base integer instruction set and the machine mode
> is mandatory. If there are troubles with this instruction, the core has
> a faulty design. So executing this line should be okay even if there is
> no interrupt controller.
>
It's not a bug, it's a feature :)
At the moment I use picorv32 core.
Here is a quote from https://github.com/cliffordwolf/picorv32#custom-instructions-for-irq-handling
The IRQ handling features in PicoRV32 do not follow the RISC-V Privileged ISA specification.
Instead a small set of very simple custom instructions is used to implement IRQ handling with
minimal hardware overhead.
I'm planning to make it possible to use another core instead of picorv32 in Eriso SoC,
so I can introduce something like SYS_HAS_PICORV32_CPU Kconfig macro.
> --
> Mit freundlichen Grüßen,
> With best regards,
> Daniel Schultz
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-10-02 22:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 23:12 [RFC v4 00/10] add " Antony Pavlov
2017-09-28 23:12 ` [RFC v4 01/10] Add " Antony Pavlov
2017-09-29 12:07 ` Oleksij Rempel
2017-09-30 11:57 ` Antony Pavlov
2017-10-02 7:43 ` Oleksij Rempel
2017-10-02 14:08 ` Antony Pavlov
2017-10-02 10:04 ` Daniel Schultz
2017-10-02 22:15 ` Antony Pavlov [this message]
2017-10-02 10:08 ` Daniel Schultz
2017-10-02 22:21 ` Antony Pavlov
2017-10-05 10:55 ` Daniel Schultz
2017-10-06 15:39 ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 02/10] RISC-V: add Erizo SoC support Antony Pavlov
2017-09-29 12:18 ` Oleksij Rempel
2017-09-30 12:05 ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 03/10] RISC-V: add low-level debug macros for ns16550 Antony Pavlov
2017-09-28 23:12 ` [RFC v4 04/10] RISC-V: add nmon nano-monitor Antony Pavlov
2017-09-29 12:26 ` Oleksij Rempel
2017-09-30 12:22 ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 05/10] RISC-V: erizo: add DEBUG_LL support Antony Pavlov
2017-09-28 23:12 ` [RFC v4 06/10] RISC-V: erizo: enable NMON Antony Pavlov
2017-09-28 23:12 ` [RFC v4 07/10] RISC-V: erizo: add nmon image creation Antony Pavlov
2017-09-28 23:12 ` [RFC v4 08/10] RISC-V: add erizo_generic_defconfig Antony Pavlov
2017-09-29 12:29 ` Oleksij Rempel
2017-09-30 12:38 ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 09/10] scripts: add nmon-loader Antony Pavlov
2017-09-28 23:12 ` [RFC v4 10/10] Documentation: add RISC-V docs Antony Pavlov
2017-09-29 12:35 ` Oleksij Rempel
2017-09-30 12:34 ` Antony Pavlov
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=20171003011517.11458b57798f7e6d9d07c512@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=d.schultz@phytec.de \
/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