From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Understanding the LibreSOC core
Date: Mon, 8 Jun 2020 23:17:04 +0100
Message-ID: <CAPweEDwLmSCi4LQ5ksaa9CyaMaXUQ7r7D6bu=3WYwzpT8CqCCQ@mail.gmail.com> (raw)
In-Reply-To: <2731f72d-5638-b594-9de4-1f0db635da44@gmail.com>
On Mon, Jun 8, 2020 at 10:19 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> On 6/8/20 4:38 PM, Luke Kenneth Casson Leighton wrote:
> > there's a BIOS?? oink :)
> >
> > if there's a BIOS, it means that at least some instructions can be
> > loaded (into something - probably an on-board SRAM) and executed, and
> > that at least means we can test _something_ before getting to that
> > stage.
> >
> > (meaning: the instructions to initialise DDR3 have to execute _from_
> > somewhere, they can't be executed from thin air)
> >
> > btw we were planning to put in a "Board Support Package" NLNet Grant Request.
> >
> We were going to need to do something like this anyway though, the
> actual SOC will need some low level boot code in rom right?
the original bugreport is basically for the hardware only
https://bugs.libre-soc.org/show_bug.cgi?id=22
as that milestone has been set and approved, if anyone does write any
low-level boot code, it can't come from that budget. this is just how
it works.
> For initial
> testing the 45f has 216kiB of bram, which is plenty for running test
> code and whatnot
oh good.
> (granted, we will need some of that ram for other
> purposes).
L1 caches. regfiles.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 18:03 Sanjay Menon
2020-06-08 18:24 ` Luke Kenneth Casson Leighton
2020-06-08 18:46 ` Yehowshua
2020-06-08 18:55 ` Luke Kenneth Casson Leighton
2020-06-08 18:58 ` Yehowshua
2020-06-08 19:01 ` Sanjay Menon
2020-06-08 19:09 ` Yehowshua
2020-06-08 19:14 ` Yehowshua
2020-06-08 20:38 ` Luke Kenneth Casson Leighton
2020-06-08 20:46 ` Luke Kenneth Casson Leighton
2020-06-08 21:19 ` Michael Nolan
2020-06-08 22:17 ` Luke Kenneth Casson Leighton [this message]
2020-06-08 22:18 ` Luke Kenneth Casson Leighton
2020-06-08 20:11 ` Michael Nolan
2020-06-08 20:12 ` Yehowshua
2020-06-08 20:31 ` Luke Kenneth Casson Leighton
2020-06-08 19:02 ` Luke Kenneth Casson Leighton
2020-06-08 19:05 ` Yehowshua
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='CAPweEDwLmSCi4LQ5ksaa9CyaMaXUQ7r7D6bu=3WYwzpT8CqCCQ@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git