Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26  5:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #114 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
actually, i like what you wrote a whooole lot better, michael:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/qemu.py;h=c9b1b573dd22d3da0adb0415a0a6b8bb005c99c6;hb=4b50a170c413f47e0527c843be49babc493c684b

the only modification i needed:

set architecture powerpc:common64
target remote localhost:1234
layout asm
b *0x20000000
c

and to use debian package "gdb-multilib" which *sigh* had to come from
debian/unstable.

building cross-compilers etc. from source has always stressed me out :)

if we do that, we need a proper documented reproducible process.

how did you get powerpc64-linux-gnu-gdb?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Git mirroring
From: Luke Kenneth Casson Leighton @ 2020-03-26  5:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7gKSn03BW8aTic-VKCyR5OMZFnDCkNW2qsx=KSfFDTuw@mail.gmail.com>

On Thu, Mar 26, 2020 at 4:37 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Stupid gmail formatting.

doh. whyy do we put up with it??

> fixed:
>
> https://salsa.debian.org/Kazan-team/ieee754fpu
> https://salsa.debian.org/Kazan-team/soc
> https://salsa.debian.org/Kazan-team/nmutil

this means manual checkout (and instructions) don't need an extra
argument.  while we're at it, soclayout might as well be added to
that?

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26  5:40 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #111 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
deep breath....

install dependencies (saves messing about) with
apt-get build-dep qemu

git clone from here:

[remote "origin"]
    url = https://github.com/legoater/qemu.git
    fetch = +refs/heads/*:refs/remotes/origin/*

git checkout this branch:
* origin/powernv-next

configure/build with this:
./configure --enable-system
--target-list=ppc64-softmmu,ppc64-linux-user,ppc64le-linux-user

edit hw/ppc/pnv.c and comment out these lines:

        /*
    if (qemu_uuid_set) {
        _FDT((fdt_property_string(fdt, "system-id", buf)));
    }
    */

run python3 domstart.py (files to be attached shortly)

dump the state to a file:

virsh # dump Linux-0.2 mem.hex --memory-only --crash


objdump the results with this:

objdump -x mem.hex

which gives the following (including regfile and memory):

architecture: powerpc:common64, flags 0x00000000:

start address 0x0000000000000000

Program Header:
    NOTE off    0x00000000000000b0 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**0
         filesz 0x0000000000000710 memsz 0x0000000000000710 flags ---
    LOAD off    0x00000000000007c0 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**0
         filesz 0x0000000040000000 memsz 0x0000000040000000 flags ---

Sections:
Idx Name          Size      VMA               LMA               File off  Algn
  0 note0         00000710  0000000000000000  0000000000000000  000000b0  2**0
                  CONTENTS, READONLY
  1 .reg/0        00000180  0000000000000000  0000000000000000  00000134  2**2
                  CONTENTS
  2 .reg          00000180  0000000000000000  0000000000000000  00000134  2**2
                  CONTENTS
  3 .reg2/0       00000108  0000000000000000  0000000000000000  000002d0  2**2
                  CONTENTS
  4 .reg2         00000108  0000000000000000  0000000000000000  000002d0  2**2
                  CONTENTS
  5 load1         40000000  0000000000000000  0000000000000000  000007c0  2**0
                  CONTENTS, ALLOC, LOAD, READONLY

and thus can be parsed with python elf libraries mentioned in previous
comments.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Git mirroring
From: Jacob Lifshay @ 2020-03-26  4:37 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7GCeYTNNHSH2Q5RX5eefEmYDx0-5dxQw-vVjB1kRG30w@mail.gmail.com>

On Wed, Mar 25, 2020, 21:35 Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Wed, Mar 25, 2020, 21:08 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
>> On Thursday, March 26, 2020, Jacob Lifshay <programmerjake@gmail.com>
>> wrote:
>>
>> > I added git mirrors for ieee754fpu.git and soc.git on debian salsa:
>> >
>> > https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu
>> > https://salsa.debian.org/Kazan-team/libreriscv-soc
>>
>>
>> nmutil also needed.  the rename is a bit.... inconvenient?
>
>
> added nmutil and renamed the others.
>
> https://salsa.debian.org/Kazan-team/ieee754fpu
> <https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu>
> https://salsa.debian.org/Kazan-team/soc
> <https://salsa.debian.org/Kazan-team/libreriscv-soc>
> https://salsa.debian.org/Kazan-team/
> <https://salsa.debian.org/Kazan-team/libreriscv-soc>nmutil
>

Stupid gmail formatting.

fixed:

https://salsa.debian.org/Kazan-team/ieee754fpu
https://salsa.debian.org/Kazan-team/soc
https://salsa.debian.org/Kazan-team/nmutil
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Git mirroring
From: Jacob Lifshay @ 2020-03-26  4:35 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwYTfh=SrmEbP6u1ZFrSKFUssk=MREjcaj8J1GSbzydOw@mail.gmail.com>

On Wed, Mar 25, 2020, 21:08 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Thursday, March 26, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > I added git mirrors for ieee754fpu.git and soc.git on debian salsa:
> >
> > https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu
> > https://salsa.debian.org/Kazan-team/libreriscv-soc
>
>
> nmutil also needed.  the rename is a bit.... inconvenient?


added nmutil and renamed the others.

https://salsa.debian.org/Kazan-team/ieee754fpu
<https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu>
https://salsa.debian.org/Kazan-team/soc
<https://salsa.debian.org/Kazan-team/libreriscv-soc>
https://salsa.debian.org/Kazan-team/
<https://salsa.debian.org/Kazan-team/libreriscv-soc>nmutil

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Setup automation scripts
From: Luke Kenneth Casson Leighton @ 2020-03-26  4:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CA8910BD-0AFF-43FF-ACEB-C3022F0A7258@getmailspring.com>

cole click the three dots first before reading this further...

On Wednesday, March 25, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

>
>
> On Mar 25 2020, at 9:18 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > On Wed, Mar 25, 2020 at 4:04 PM Cole Poirier <colepoirier@gmail.com>
> wrote:
> >>
> >> Hi Libre-SOC team,
> >>
> >> I'm currently working on turning the setup Jacob and I did on his build
> >> server into an easily replicable bash setup script. While working on
> >> this yesterday, I concurrently tried to follow the hdl workflow, a
> >> substantial part of which is setting up a debootstrapped chroot and
> >> installing coriolis2. On this attempt I was finally able to complete it
> >> (thanks to Luke and Jock for updating the process for Debian 10 and
> >> working out a few other kinks in the process!),
> >
> > hooraaay!
> >
> >> but given the length and
> >> complexity of this process, it strikes me as another candidate for
> >> automation. I was thinking I could repeat the process I'm going through
> >> with Jacob, working on the build server setup automation, with the HDL
> >> workflow.
> >
> > yep, sure, go for it.  drop all the commands into scripts, then...
> > hmmm, you have git read/write access to the wiki: git commit them into
> > HDL_workflow directory and put in a link to them in coriolis2.mdwn
>
> Will do!
>
> >> Jacob has advised me to set up a local debian vm for the
> >> purposes of ensuring the script's reliability, so it is my thiniking
> >> that it will be worthwhile to work on these two process automations
> concurrently.
> >> Do you think that this is would be useful and worthwhile? Also, given
> >> that we already have a hard dependency on python, are bash scripts
> >> preferable to the python equivalent of these automation scripts?
> >
> > python is total overkill, bash is generic and brain-dead.
> >
> > there's absolutely no need for using python for this task, as there is
> > zero interaction.  it's literally a matter of bang, bang, command,
> > command.  remember you can output stuff to files with:
> >
> > $ cat <<EOF > filename
> > adasdjhasd
> > asda
> > sd
> > EOF
> > $
> >
> > https://stackoverflow.com/questions/2500436/how-does-
> cat-eof-work-in-bash
> >
> > so you absolutely do not need to use python, not even for file-writing.
> >
> > l.
>
> Perfect, thanks for the advice Luke. Working with you is a great
> education in how to do software engineering properly.


... which includes trimming context on replies.  you see how much crap
there is, how long it took to scroll down and find this?

not everyone is using gmaul.

l.


> Cole
>
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] [OP-CD] OpenPOWER Foundation "Virtual Coffee" Calls
From: Luke Kenneth Casson Leighton @ 2020-03-26  4:10 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD49oPkpdhGFAUt9Dp+m-=vj=Gk1UZ-Qgq3m44gtpqE6rQ@mail.gmail.com>

On Tuesday, March 24, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> Maybe we should participate.


i'll be on both.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Git mirroring
From: Luke Kenneth Casson Leighton @ 2020-03-26  4:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6tt-iORTe1RVyc-Tgv_PuSKsmVcbpP95qSoTx6hWx2+Q@mail.gmail.com>

On Thursday, March 26, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> I added git mirrors for ieee754fpu.git and soc.git on debian salsa:
>
> https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu
> https://salsa.debian.org/Kazan-team/libreriscv-soc


nmutil also needed.  the rename is a bit.... inconvenient?



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] Git mirroring
From: Jacob Lifshay @ 2020-03-26  2:15 UTC (permalink / raw)
  To: Libre-RISCV General Development

I added git mirrors for ieee754fpu.git and soc.git on debian salsa:

https://salsa.debian.org/Kazan-team/libreriscv-ieee754fpu
https://salsa.debian.org/Kazan-team/libreriscv-soc

Since GitLab CE doesn't yet support pull mirroring, I set up a cron
job on jacob-build-server that syncs every minute.

GitLab issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/23166

I wrote up the instructions for reproducing the server setup:

https://libre-riscv.org/resources/server-setup/git-mirroring/

Jacob

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-03-25 22:15 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=266

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
A potentially useful reference (not known to be correct):
http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/

Showing the URL required for cloning is a good accessibility improvement.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 266] New: Allow read-only git clone over https
From: bugzilla-daemon @ 2020-03-25 22:12 UTC (permalink / raw)
  To: libre-riscv-dev

http://bugs.libre-riscv.org/show_bug.cgi?id=266

            Bug ID: 266
           Summary: Allow read-only git clone over https
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: programmerjake@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

The git protocol is a insecure protocol, we should also support cloning over
https.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 21:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #110 from Michael Nolan <mtnolan2640@gmail.com> ---
I've got a rudimentary qemu-gdb interface working in qemu.py:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/qemu.py;h=70e29b0d76b65227a06d3ba3bd95315cf5af37e8;hb=3f7e6c771c7f8df65e67e6dc350964a54aee8066

It's able to load a kernel into qemu, set up a breakpoint at the start of it,
single step it, and dump the register contents.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 20:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #109 from Michael Nolan <mtnolan2640@gmail.com> ---
I'm going to try using https://sourceware.org/gdb/wiki/PythonGdb to see if I
can't get something working that way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 19:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #108 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://bugzilla.redhat.com/show_bug.cgi?id=1585991

woooow....

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 19:43 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #107 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
currently attempting to get python-libvirt to "start" launch.sh.
wooow is this painful.  obtuseness beyond obtuseness.

/usr/bin/qemu-system-ppc64 \
-name guest=Linux-0.2,debug-threads=on \
-S \
-object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-Linux-0.2/master-key.aes
\
-machine powernv9,accel=tcg,usb=off,dump-guest-core=off \
-m 1024 \
-overcommit mem-lock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid ce1326f0-a9a0-11e3-a5e2-0800200c9a66 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=33,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc \
-no-shutdown \
-boot strict=on \
-kernel /home/lkcl/testdisk.raw \
-sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-03-25T19:38:07.721499Z qemu-system-ppc64: error creating device tree:
(fdt_property_string(fdt, "system-id", buf)): FDT_ERR_BADSTATE
2020-03-25 19:38:07.758+0000: shutting down, reason=failed


https://bugzilla.redhat.com/show_bug.cgi?id=1624539

nggggggh.

attempting to downgrade qemu-system-ppc so that the older version of libfdt can
be used

apt-get install libfdt1=1.4.2-1 qemu-system-ppc=1:3.1+dfsg-8+deb10u3
qemu-system=1:3.1+dfsg-8+deb10u3 qemu-system-misc=1:3.1+dfsg-8+deb10u3

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] cache SRAM organisation
From: Jacob Lifshay @ 2020-03-25 17:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxiyTEsneXN65Kq0HsEsdL3wdY=NYayq2tz5egXJNCVfg@mail.gmail.com>

On Wed, Mar 25, 2020, 08:54 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wed, Mar 25, 2020 at 1:46 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
>
> > Keep the discussion on development of other types til after the
> prototype tape-out in October.
>
> good idea.
>
> > I know there is other development ongoing for dual port RAM in the
> OpenRAM community so likely it is more clear what extra still has to happen.
> > BTW, I think there also is possibility to have register files block with
> 2R1W RAM blocks.
>
> ah that's good.  we can combine two of them to create 4R1W (we need
> minimum 3R1W, however the design does not critically depend on this:
> it just takes 2 cycles to read all operands for 3-operand instructions
> such as FMAC).
>
> > > this because it turns out that asynchronous SRAM can act, when used in
> aRegister File, as if it was a (separate) Register Bypass /
> ForwardingPort.  with the Out-of-Order Engine being a huge cyclic feedback
> loopbetween ALUs and RegFile, clock delays are an impediment, and
> havingcompletely separate (extra) Regfile Bypass ports dramatically
> increases thenumber of wires and Multiplexers.
> >
> > Could detail more on how the adress, data and output signals of this
> asynchronous block would be used and switched between synchronous and
> asynchronous functioning. To me it seems that it would just place of the
> multiplexers, not the amount.
>
> ok i will try to outine it, there is quite a lot of detail, i apologise.
>
> it's basically the "pass-through" system used in nmigen FIFOs, and the
> "synchronous" mode of nmigen Memory.  the requirements are: what is
> written has to be available *combinatorially* - i.e. on the same clock
> cycle - if simultaneously read via another port.
>
> now, yes i took note that this is not supposed to be permitted: you're
> not normally permitted to be able to read *and* write to an SRAM cell
> at the same time.  however, that's exactly what we need.
>

It seems obvious to me that you just add a mux on each read port to bypass
directly from the write ports when the address matches -- that way you
don't have to worry about needing both read and write to the same cell.

Also, assuming I'm not missing something, grouping two 1R or 1W srams
doesn't give 2R1W, it gives 2R or 1W since each cycle that you write, you
write to all srams meaning all srams can't read.

Jacob

>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 17:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #106 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://libvirt.org/drvqemu.html

shows how to convert qemu to xml if you have some args already ("virsh
domxml-from-native")

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 17:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #105 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #104)

> see earlier comments, yes do drop the qemu example into a subfolder.

It's now uploaded here:
https://git.libre-riscv.org/?p=soc.git;a=tree;f=src/soc/simulator/qemu_test;h=50cde50b45e9af13b3c070c8b9618a956f63d3b5;hb=40c5ec1f0df4bed1d78b1d0d019b399450d87ced

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 17:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #104 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
just taking a closer look at python-libvirt, and trying to find the examples i
saw which turn qemu params into xml files

also this:

https://www.programcreek.com/python/example/28110/libvirt.open
canCreateVM - is able to run virsh, which will get a coredump
(including regfile as well as memory).

see earlier comments, yes do drop the qemu example into a subfolder.

be with you in a sec, just investigating.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] nmutil failing tests due to attribute errors
From: Cole Poirier @ 2020-03-25 17:03 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDzLArv-M2gdUMBYfsZfKPZGvgD9x66M2Vd8=2SSonQNCQ@mail.gmail.com>

On Mar 25 2020, at 9:13 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Wed, Mar 25, 2020 at 4:00 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> 
>> Hi Libre-SOC team,
>> 
>> I think I completed HDL workflow sucessfully yesterday, however when I
>> try to run "python3 setup.py test" in nmutil I get 33 errors.
>> Adhering to the rule of not pasting large amounts of autogenerated
>> output, I will only include two examples in this first email, but I can
>> provide more details should you need them to help me. Can you please
>> advise me as to what I've done wrong or misconfigured?
>> 
>> ###
>> ERROR: nmutil.test.test_outmux_pipe.test1
>> AttributeError: 'Queue' object has no attribute 'we'
> 
> do a "git pull", i fixed this.  i thought i'd sorted it a few days ago
> however that was in Queue itself, not singlepipe.py
> 
>> ERROR: nmutil.test.test_inout_unary_mux_cancel_pipe.test1
>> AttributeError: 'TestInOutPipe' object has no attribute 'domains'
> 
> err.... err....
> 
> that works here, for me... and i think i know why.  it's because i
> keep (temporarily) adding this to nmigen:
> 
> diff --git a/nmigen/compat/sim/__init__.py b/nmigen/compat/sim/__init__.py
> index c6a89e3..42f6fd6 100644
> --- a/nmigen/compat/sim/__init__.py
> +++ b/nmigen/compat/sim/__init__.py
> @@ -19,7 +19,7 @@ def run_simulation(fragment_or_module, generators,
> clocks={"sync": 10}, vcd_name
> 
>     if not isinstance(generators, dict):
>         generators = {"sync": generators}
> -        fragment.domains += ClockDomain("sync")
> +        #fragment.domains += ClockDomain("sync")
> 
>     sim = Simulator(fragment)
>     for domain, period in clocks.items():
> 
> add that one line and it'll work.
> 
> l.


Woohoo!! Thanks that worked perfectly!

Cole

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Setup automation scripts
From: Cole Poirier @ 2020-03-25 16:22 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxtmL-5in1Xeed90OMGyvxWSSB2TAum_xdAbrJprug-Hg@mail.gmail.com>



On Mar 25 2020, at 9:18 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On Wed, Mar 25, 2020 at 4:04 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> 
>> Hi Libre-SOC team,
>> 
>> I'm currently working on turning the setup Jacob and I did on his build
>> server into an easily replicable bash setup script. While working on
>> this yesterday, I concurrently tried to follow the hdl workflow, a
>> substantial part of which is setting up a debootstrapped chroot and
>> installing coriolis2. On this attempt I was finally able to complete it
>> (thanks to Luke and Jock for updating the process for Debian 10 and
>> working out a few other kinks in the process!),
> 
> hooraaay!
> 
>> but given the length and
>> complexity of this process, it strikes me as another candidate for
>> automation. I was thinking I could repeat the process I'm going through
>> with Jacob, working on the build server setup automation, with the HDL
>> workflow.
> 
> yep, sure, go for it.  drop all the commands into scripts, then...
> hmmm, you have git read/write access to the wiki: git commit them into
> HDL_workflow directory and put in a link to them in coriolis2.mdwn

Will do!
 
>> Jacob has advised me to set up a local debian vm for the
>> purposes of ensuring the script's reliability, so it is my thiniking
>> that it will be worthwhile to work on these two process automations concurrently.
>> Do you think that this is would be useful and worthwhile? Also, given
>> that we already have a hard dependency on python, are bash scripts
>> preferable to the python equivalent of these automation scripts?
> 
> python is total overkill, bash is generic and brain-dead.
> 
> there's absolutely no need for using python for this task, as there is
> zero interaction.  it's literally a matter of bang, bang, command,
> command.  remember you can output stuff to files with:
> 
> $ cat <<EOF > filename
> adasdjhasd
> asda
> sd
> EOF
> $
> 
> https://stackoverflow.com/questions/2500436/how-does-cat-eof-work-in-bash
> 
> so you absolutely do not need to use python, not even for file-writing.
> 
> l.

Perfect, thanks for the advice Luke. Working with you is a great
education in how to do software engineering properly.

Cole


_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-25 16:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #103 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #102)
> (In reply to Luke Kenneth Casson Leighton from comment #98)
> > https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/test_sim.
> > py;hb=HEAD
> > 
> > y'know... the comment "checked this against qemu" got me thinking. this
> > looks like it could be used to actually run any of:
> > 
> > * qemu
> 
> what do you think, michael: does firing off qemu to run those same
> (tiny) binaries sound practical?

It doesn't seem like a bad idea, especially since we don't have another power
simulator to compare to yet. Getting the instructions/data into qemu is pretty
easy, just compile and link a bare metal kernel. I've got a folder with my
manual method for this already, and I can add it to the git repo. 
However, getting the data (registers/memory) out of qemu might be a bit harder.
Probably the best way would be to use the gdb socket that qemu makes available
for reading registers and memory. I know GDB is written with python in mind, so
it *should* be doable to control it from python, but I haven't investigated
that yet.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Setup automation scripts
From: Luke Kenneth Casson Leighton @ 2020-03-25 16:18 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <C2D1868C-320A-4A59-B944-FA79576C112A@getmailspring.com>

On Wed, Mar 25, 2020 at 4:04 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> Hi Libre-SOC team,
>
> I'm currently working on turning the setup Jacob and I did on his build
> server into an easily replicable bash setup script. While working on
> this yesterday, I concurrently tried to follow the hdl workflow, a
> substantial part of which is setting up a debootstrapped chroot and
> installing coriolis2. On this attempt I was finally able to complete it
> (thanks to Luke and Jock for updating the process for Debian 10 and
> working out a few other kinks in the process!),

hooraaay!

> but given the length and
> complexity of this process, it strikes me as another candidate for
> automation. I was thinking I could repeat the process I'm going through
> with Jacob, working on the build server setup automation, with the HDL
> workflow.

yep, sure, go for it.  drop all the commands into scripts, then...
hmmm, you have git read/write access to the wiki: git commit them into
HDL_workflow directory and put in a link to them in coriolis2.mdwn


> Jacob has advised me to set up a local debian vm for the
> purposes of ensuring the script's reliability, so it is my thiniking
> that it will be worthwhile to work on these two process automations concurrently.
> Do you think that this is would be useful and worthwhile? Also, given
> that we already have a hard dependency on python, are bash scripts
> preferable to the python equivalent of these automation scripts?

python is total overkill, bash is generic and brain-dead.

there's absolutely no need for using python for this task, as there is
zero interaction.  it's literally a matter of bang, bang, command,
command.  remember you can output stuff to files with:

$ cat <<EOF > filename
adasdjhasd
asda
sd
EOF
$

https://stackoverflow.com/questions/2500436/how-does-cat-eof-work-in-bash

so you absolutely do not need to use python, not even for file-writing.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] nmutil failing tests due to attribute errors
From: Luke Kenneth Casson Leighton @ 2020-03-25 16:13 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <067FEFA4-E343-49D5-B131-29E41DC9F622@getmailspring.com>

On Wed, Mar 25, 2020 at 4:00 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> Hi Libre-SOC team,
>
> I think I completed HDL workflow sucessfully yesterday, however when I
> try to run "python3 setup.py test" in nmutil I get 33 errors.
> Adhering to the rule of not pasting large amounts of autogenerated
> output, I will only include two examples in this first email, but I can
> provide more details should you need them to help me. Can you please
> advise me as to what I've done wrong or misconfigured?
>
> ###
> ERROR: nmutil.test.test_outmux_pipe.test1
> AttributeError: 'Queue' object has no attribute 'we'

do a "git pull", i fixed this.  i thought i'd sorted it a few days ago
however that was in Queue itself, not singlepipe.py

> ERROR: nmutil.test.test_inout_unary_mux_cancel_pipe.test1
> AttributeError: 'TestInOutPipe' object has no attribute 'domains'

err.... err....

that works here, for me... and i think i know why.  it's because i
keep (temporarily) adding this to nmigen:

diff --git a/nmigen/compat/sim/__init__.py b/nmigen/compat/sim/__init__.py
index c6a89e3..42f6fd6 100644
--- a/nmigen/compat/sim/__init__.py
+++ b/nmigen/compat/sim/__init__.py
@@ -19,7 +19,7 @@ def run_simulation(fragment_or_module, generators,
clocks={"sync": 10}, vcd_name

     if not isinstance(generators, dict):
         generators = {"sync": generators}
-        fragment.domains += ClockDomain("sync")
+        #fragment.domains += ClockDomain("sync")

     sim = Simulator(fragment)
     for domain, period in clocks.items():

add that one line and it'll work.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] Setup automation scripts
From: Cole Poirier @ 2020-03-25 16:04 UTC (permalink / raw)
  To: Libre-RISCV General Development

Hi Libre-SOC team,

I'm currently working on turning the setup Jacob and I did on his build
server into an easily replicable bash setup script. While working on
this yesterday, I concurrently tried to follow the hdl workflow, a
substantial part of which is setting up a debootstrapped chroot and
installing coriolis2. On this attempt I was finally able to complete it
(thanks to Luke and Jock for updating the process for Debian 10 and
working out a few other kinks in the process!), but given the length and
complexity of this process, it strikes me as another candidate for
automation. I was thinking I could repeat the process I'm going through
with Jacob, working on the build server setup automation, with the HDL
workflow. Jacob has advised me to set up a local debian vm for the
purposes of ensuring the script's reliability, so it is my thiniking
that it will be worthwhile to work on these two process automations concurrently.
Do you think that this is would be useful and worthwhile? Also, given
that we already have a hard dependency on python, are bash scripts
preferable to the python equivalent of these automation scripts?

Cole

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

page:   latest

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