* Re: [libre-riscv-dev] daily kan-ban update 31jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-31 17:41 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyjb7M+8zFsHBabTbEFY9iU7Rth8wfA5cQh3H55k0RO2A@mail.gmail.com>
On Friday, July 31, 2020, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
not sure. the litex simulation is "acting up", not outputting serial
> console data (for microwatt or libresoc), is stopping early and not quite
> matching.
>
ok i have some clues from this. memory LD / STs were at the wrong
addresses. this led me to investigate the immediate offsets, which turned
out to be unsigned only.
immediates are calculated in power_decoder which was one the first things
written. it is amazing that it has gone unnoticed for so long.
basically we had nowhere near good enough unit test coverage for LD / ST
otherwise this would have been caught far sooner.
l.
--
---
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] microwatt feature request: "switch off all optimisations" mode
From: Luke Kenneth Casson Leighton @ 2020-07-31 14:40 UTC (permalink / raw)
To: openpower-hdl-cores; +Cc: Libre-RISCV General Development
paul, benjamin, mikey: i have a huge favour to ask of you (or a "howto"
question), given that i never done VHDL programming before.
thank to florent of enjoy-digital's help, libresoc now has connectivity to
litex in simulation, just like in microwatt. in particular he added a
"Display" option on any wishbone activity requested by (either) core,
allowing me to see what is going on.
i was therefore looking to do cycle-accurate side by side comparisons, spot
the discrepancies, fix the bug and move on to the next one.
this technique has worked extremely well up to now by comparing against
qemu, and against our python simulator.
we would like to be able to add microwatt to that list.
the problem is that microwatt has branch prediction, L1 cacheing and
pipeline latency all of which mean that i am completely guessing about what
caused any given bus read/write.
any kind of side-by-side comparison of log files, looking for the "one
instruction that does something different/wrong" is out of the question.
... *unless*... there is a "mode" for microwatt that is effectively
equivalent to gdb single-step.
we need a way to stop microwatt from doing any kind of overlapping
instructions. this *may* be possible already through the JTAG/debug
interface, i do not know.
the alternative is some minor modifications that throw in a deliberate 10
to 20 cycle delay in the instruction issue phase. this would give ample
time to inspect the internal state (regfiles, PC, SPRs, etc) looking for
discrepancies when running the exact same binary.
what would you suggest here? how can we "single-step" microwatt? clearly
performance is not important: cycle-accurate comparisons is the goal.
with thanks, and understanding that you are busy people,
l.
--
---
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] daily kan-ban update 31jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-31 13:53 UTC (permalink / raw)
To: Libre-RISCV General Development
tasks:
*
https://bugs.libre-soc.org/showdependencytree.cgi?id=383&maxdepth=1&hide_resolved=1
yesterday:
* tracked down XICS unit test bug
* investigated litex libresoc simulation kindly provided by florent
* helped jean-paul with direction on "floorplan" version of layout.
* attended hilarious and informative OpenPOWER Virtual Coffee
*
today:
* added ref to powerpc-notebook article
* updated https://libre-soc.org/3d_gpu/ "progress" section
* looked again with puzzlement at the litex simulation.
rest of day:
not sure. the litex simulation is "acting up", not outputting serial
console data (for microwatt or libresoc), is stopping early and not quite
matching.
microwatt has branch prediction and a L1 cache so examining the wishbone
reads/writes does not give an accurate picture of what it is actually doing.
i would _like_ to do a cycle accurate comparison of log output and find the
discrepancies however this is really not that easy.
this is going to need some thought.
l.
--
---
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] daily kan-ban update 30jul2020
From: Cole Poirier @ 2020-07-30 20:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz9b98paEhLArSk9qOPzh11+RsC16N5+6TqGkhF0zL65w@mail.gmail.com>
On Thu, Jul 30, 2020 at 6:24 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> rest of day:
>
> * started watching Andromeda Season 1. it's low budget, kitcsh, and i love
> it.
Sounds like fun!
> * continuing with the litex sim debugging.
Sounds like less fun ;)
Yesterday:
* Libre-SOC OPF MKII Call
* Administrative tasks like closing bugs that had been solved but not
marked RESOLVED
* Minor changes to 180 nm test asic memory layout diagram
Today:
* start a correspondence with Mitch about getting the original images
from his book chapters (vector rather than bitmap), and consultation
on if he would like to use the new SVGs in a future version of the
book chapters
* start the process of creating a bug report for each diagram that is
to be converted to SVG
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] daily kan-ban update 30jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-30 13:23 UTC (permalink / raw)
To: Libre-RISCV General Development
tasks:
*
https://bugs.libre-soc.org/showdependencytree.cgi?id=383&maxdepth=1&hide_resolved=1
yesterday:
* preliminary xics unit test investigation
* communication with microwatt developers about xics
* libresoc openpower microwatt meeting
* got https://docs.libre-soc.org running thanks to alain.
today:
* fixed bug in xics unit test (xics wishbone itself was fine)
* based on florent's insights and with whitequark's help got further in the
litex (verilog) simulation.
rest of day:
* started watching Andromeda Season 1. it's low budget, kitcsh, and i love
it.
* continuing with the litex sim debugging.
l.
--
---
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] daily kan-ban update 29jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-29 21:04 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7humyp54V5ymyqFUe_tff6hq8BmXBY019=SZfdawXR2swgw@mail.gmail.com>
On Wed, Jul 29, 2020 at 9:37 PM Cole Poirier <colepoirier@gmail.com> wrote:
> * Libre-SOC OPF MKII Call
>
> The call will start in just under an hour and a half from now, correct?
correct.
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] daily kan-ban update 29jul2020
From: Cole Poirier @ 2020-07-29 20:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200729194812.0bee3946188405499d94fcec@platen-software.de>
Yesterday:
* finished coriolis2 workflow scripts and documentation (now includes
soclayout instructions)
* finished 180nm test ASIC memory layout diagram translation to SVG,
the hand-drawn version has been replaced with this version on the
180nm test ASIC wiki page
* got profoundly confused about XICS, LoPAR, PAPR... etc.
(fortunately Luke figured a temporary solution with microwatt team)
Today:
* start a correspondence with Mitch about getting the original images
from his book chapters (vector rather than bitmap), and consultation
on if he would like to use the new SVGs in a future version of the
book chapters
* documented my completed, current, near future work on my wiki page
* closed several bugs that had been resolved at various points in the
past few months but hadn't been marked RESOLVED on bugzilla
* start the process of creating a bug report for each diagram that is
to be converted to SVG
* brainstorming with other project members about recruiting more
project members
* solicit input from project members on what should be asked about
the BlackParrot RV664GC 14nm (!!!!) Multicore SoC in my email
to that project's developers
* Libre-SOC OPF MKII Call
The call will start in just under an hour and a half from now, correct?
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] daily kan-ban update 29jul2020
From: Tobias Platen @ 2020-07-29 17:48 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDw1+nyxukac0JOwgud41i7KZgo7Ku8kZO_4gSdhAzrAXg@mail.gmail.com>
today:
modified LDSTSplitter to conform to PortInterface
On Wed, 29 Jul 2020 17:15:58 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> task list:
>
> *
> https://bugs.libre-soc.org/showdependencytree.cgi?maxdepth=1&id=383&hide_resolved=1
>
> yesterday:
>
> * added unit test for XICS, started debate on lsdev and openpower hdlcores
> * sorted silliness in shiftrot proof so Sam can run it
>
> today:
>
> * reviewed div test mods (looks great, jacob)
> * received notification on MoU approval, sent out RFP template for
> whitequark
> * more review of XICS, possible bug found in microwatt xics.vhdl
> * sorted out names for CompUnits to make Jean-Paul's life easier
> * got word from Florian investigating Litex, sent him an updated verilog
> core.
>
> later:
>
> * more on XICS unit tests
> * GPU Sync meeting with OpenPOWER Foundation and microwatt developers,
> which is one hour later than 2 weeks ago.
>
> l.
>
>
>
> --
> ---
> 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
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
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] daily kan-ban update 29jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-29 16:15 UTC (permalink / raw)
To: Libre-RISCV General Development
task list:
*
https://bugs.libre-soc.org/showdependencytree.cgi?maxdepth=1&id=383&hide_resolved=1
yesterday:
* added unit test for XICS, started debate on lsdev and openpower hdlcores
* sorted silliness in shiftrot proof so Sam can run it
today:
* reviewed div test mods (looks great, jacob)
* received notification on MoU approval, sent out RFP template for
whitequark
* more review of XICS, possible bug found in microwatt xics.vhdl
* sorted out names for CompUnits to make Jean-Paul's life easier
* got word from Florian investigating Litex, sent him an updated verilog
core.
later:
* more on XICS unit tests
* GPU Sync meeting with OpenPOWER Foundation and microwatt developers,
which is one hour later than 2 weeks ago.
l.
--
---
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] openpower foundation summit
From: Luke Kenneth Casson Leighton @ 2020-07-28 20:51 UTC (permalink / raw)
To: Libre-RISCV General Development
https://linuxfoundation.smapply.io/prog/openpower_na_2020/
another one, going to be online.
--
---
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] system call (sc) LEV "reserved field"
From: Benjamin Herrenschmidt @ 2020-07-23 22:25 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <CAPweEDx_gUy8KoQUrfE+Xn-URqFQsMiiT8A9WcLsK67E5bY8Jg@mail.gmail.com>
On Thu, 2020-07-23 at 05:16 +0100, Luke Kenneth Casson Leighton wrote:
>
> what i have observed (again this is from RISCV), for instructions
> that can be "safely ignored" are of a "hint" type.
See what Paul said... the idea is that any change to an existing
instruction that makes use of formerly reserved bits needs to be done
in such a way that the ignoring the bits is a correct implementation.
In practice that often means the new bits are indeed hints, but not
always, see Paul example about mfocrf.
> the RISCV Fence instructions also fell into this category. being
> optimisations, less complex implementations could completely ignore
> them.
>
> however in the example that you give - lwsync - i take it that this
> is a "less costly" cache/sync flush type instruction than the one
> that it was added to?
>
> i.e. old sync is a "superset" of lwsync?
sync is a memory barrier. lwsync is a lighter weight version of it, so
yes, sync is a superset of lwsync.
> this is very interesting to me, because i have made a longterm study
> of "how to develop stable specifications", and it is the first time
> in 25 years that i have encountered a counterexample to the practice
> of disallowing "reserved behaviour".
>
> the "normal" way in "reserved is illegal" specifications, would be
> that lwsync would raise an illegal instruction on a processor that
> did not support it, the author of the trap would know that the extra
> bit did not matter, the trap would call the alternative sync
> instruction, and return from the trap.
The performance impact of this would make it entirely unusable however.
> i do not know the full story about what FSL is: without knowing the
> details i suspect that a trap *could* have sorted things out, there,
> *if* the older processor was required to raise "illegal instruction"
FSL is Freescale. Some variants of their embedded cores did trap, which
forced the kernel to do some nasty dynamic patching at runtime to get
rid of lwsync's on these. The cost of a trap is way too prohibitive
(and in some cases those could be use in code path that arent safe to
take traps in).
> but because the bit is ignored, there is no way that can be done.
But that's fine because "sync" is a strict superset so ignoring the bit
works just fine.
> so whilst on the face of it, lwsync *sounds* like a counterexample,
> instead (caveat, i do not know what FSL is), it seems more to support
> the case *for* use of reserved bits raising illegal instructions [on
> UNIX platforms]
I fail to follow your logic. The trap case is a complete non-starter
for an instruction meant to be a lightweight memory barrier. The
transparent "fallback" to a full memory barrier on the contrary works
fine. There is never any case where "trapping an emulating" is the
desired behaviour.
> where of course this would become problematic is if lwsync (or other
> future added instruction) was part of a tight, performance-critical
> loop. a trap and emulate in the middle of that would severely
> degrade older processor performance. there is nothing that can be
> done about that.
Precisely.
>
> > > if however reserved bits being set cause an exception, the "old"
> > > processor stands a chance of emulating the new behaviour (in
> > > software, even if that's slow), giving it a chance of keeping out
> > of
> > > landfill for slightly longer.
> >
> > Which is why powerpc tends not to "add bits" to instructions unless
> > ignoring them is a safe fallback.
>
> as we can see above, the example that was given shows that this is a
> problematic approach.
I fail to understand the "problem" in your example, maybe you can
rephrase it ?
.../...
> sorry, Benjamin, i apologise for saying this: the question appears to
> be implying, very subtly, that you've not taken on board what i've
> said. if you had summarised what i wrote, in your own words, i would
> have a clear indicator that you'd heard me. if that is a
> misinterpretation i apologise.
>
> the specific concern *is* that reserved bits do not cause illegal
> instructions to be raised on the UNIX Platform, because without that
> in place, UNIX platform longterm seamless upgradeability and
> interoperability between vendors across all their product ranges over
> time is simply not possible.
Experience with decades of POWER architecture however seems to
demonstrate the contrary. Again, we have yet to find a case where this
approach has be the source of a specific problem.
> i have not spelled it out explicitly, seeking instead to use logical
> reasoning rather than make categorical statements, but this is
> actually a really serious problem.
Again, experience seems to indicate this is not as long as the
definition of the architecture is careful in how the reserved bits get
allocated in the future.
> > IE. Actual examples where
> > this has been cause of breakage in the past ?
>
> with PowerISA having only a few implementors, even though i am new to
> PowerISA i do not expect there to be many such examples, simply
> because as i said, for he "Embedded" class processors (Motorola's 32
> bit range, and even the Quorl 64 bit range can be said to be
> targetted at the "Embedded" market of Networking and Routing), these
> will not encounter this as a problem (because of the customised
> firmware that they run).
>
> it is only the *UNIX* Platform where this matters.
>
> that leaves, realistically, only the IBM POWER range. and when there
> is only one vendor, interoperability with other vendors is not
> important when there aren't any other vendors!
>
> however if PowerISA expands (as we know it would like to), and this
> is not changed, i *guarantee* that when more implementors are
> involved there will be problems, here.
>
> in other words the approach of ignoring reserved bits has only worked
> (for the past 20 years?) because IBM, realistically, is the only
> (non-Embedded) implementor of UNIX Platform processors.
That wasn't always true and still didn't become a problem.
Again, I really fail to see the smoking gun you seem to be implying
there is.
Cheers,
Ben.
_______________________________________________
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] [OpenPOWER-HDL-Cores] system call (sc) LEV "reserved field"
From: Benjamin Herrenschmidt @ 2020-07-23 0:52 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton, Libre-RISCV General Development
Cc: openpower-hdl-cores
In-Reply-To: <CAPweEDxxJqcy4kAcL0+wDYQh9A0KtW3dSi9kMdQ-_YotuRSsQw@mail.gmail.com>
On Thu, 2020-07-23 at 00:41 +0100, Luke Kenneth Casson Leighton wrote:
>
> because i did not expect that behaviour, because doing so (ignoring
> them) makes it impossible to trap and emulate. (it becomes necessary
> to use JIT analysis)
>
> so, when some bit is added in the future, an older processor (and the
> device it is in) basically has to be thrown into landfill.
Depends, it goes both ways. For example, this is what allowed the
addition of lwsync without throwing older processors into the landfill
because it would automatically "escalate" to a full sync on processors
that didn't implement it (or should have... FSL did screw that up on
some cores).
> if however reserved bits being set cause an exception, the "old"
> processor stands a chance of emulating the new behaviour (in
> software, even if that's slow), giving it a chance of keeping out of
> landfill for slightly longer.
Which is why powerpc tends not to "add bits" to instructions unless
ignoring them is a safe fallback.
> however it is not appropriate for all systems to raise exceptions on
> reserved bits: the cost of having the detection hardware (a full
> POWER9 decoder and also illegal/unsupported/reserved SPR detection)
> can be very high especially for resource and power constrained
> silicon or FPGAs.
>
> (example: i know someone - yea, you Sam - who implemented RV64 to
> comply with the UNIX RISCV spec rather than the Embedded RISCV spec:
> the "CSR detection" just to support all the zeros and illegal CSRs
> took a whopping 15% of an ICE40 FPGA!)
>
> in RISC-V they get this right, by having two separate Platforms:
>
> * Embedded which is permitted to ignore reserved bits entirely
>
> * UNIX, which definitely is not.
>
> for Embedded, the vendor customises the firmware entirely, and binary
> interoperability as well as legacy software support is completely
> unimportant.
>
> for UNIXen, interoperability and longterm stability we know very well
> is critical.
>
> bottom line if it is correct that on the PowerISA UNIX Platform
> reserved bits can be ignored that is cause for some concern, where
> for Embedded it would be the other way round: cause for concern if
> the reserved bits could *not* be ignored.
Do you have more specific concerns here ? IE. Actual examples where
this has been cause of breakage in the past ?
> > > however this is so unclear (because of the referral from one
> > section
> > > to another) that i am seeking confirmation. should we raise an
> > > "illegal instruction" when "LEV > 1" on sc?
> >
> > Section 1.8.2 (Book I) says "any attempt to execute an invalid form
> > of
> > an instruction will either cause the system illegal instruction
> > handler to be invoked or yield boundedly undefined results".
> > Putting
> > LEV=1 in sc would be an example of an invalid form (on an
> > implementation without hypervisor mode).
>
> ok that helps clarify what that means, thank you.
>
> > A boundedly undefined result
> > is one which could be obtained by a sequence of valid instructions,
> > so in the case of sc 1, making it do what sc 0 does meets the
> > boundedly undefined results requirement.
>
> ok so that... if i am understanding correctly, means, "you can in
> fact do something different and OS software has to detect it and sort
> it out to yield expected behaviour"
>
> which, if i am being honest, makes me nervous :)
>
> > > secondly, we note that "LEV=1" is for invocation of the
> > hypervisor.
> > > what's not clear to us is - given that we are not implementing
> > > hypervisor - should this be *also* treated as an illegal
> > instruction?
> > > or, should we just leave it to fall through to trap @ addr
> > 0x0c00, and
> > > expect the trap *there* to notice and deal with the situation?
> >
> > That is what I would do.
>
> ok. we can do that.
>
> > There is one of the variants of KVM on PPC, called KVM-PR, which
> > runs
> > the guest entirely in user mode and traps and emulates all
> > privileged
> > instructions (thus it doesn't need hypervisor mode and can run
> > inside
> > a guest of another hypervisor). If you are running a KVM guest
> > inside
> > that environment and the guest does sc 1, KVM-PR expects that to
> > end
> > up at the kernel's 0xc00 handler. So that is one reason to treat
> > sc 1
> > as sc 0.
>
> ahh. i did wonder :)
>
> > > also: if we set the HV bit in MSR (when LEV=1) section 6.5.14
> > p1077
> > > which refers us back to figure 65 on p1064, will this "break"
> > things?
> >
> > Probably not. Linux does check whether HV=1 at boot time, but I'm
> > pretty sure that's only on certain processors which it knows to be
> > HV-capable (either by looking at PVR or the device tree).
>
> ok. thank you.
>
> > > also: in microwatt, i'm not seeing the remaining bits which
> > appear [to
> > > need to] be set.
> > >
> > >
> > https://github.com/antonblanchard/microwatt/blob/master/execute1.vhdl#L479
> > > ctrl_tmp.msr(MSR_SF) <= '1';
> > > ctrl_tmp.msr(MSR_EE) <= '0';
> > > ctrl_tmp.msr(MSR_PR) <= '0';
> > > ctrl_tmp.msr(MSR_IR) <= '0';
> > > ctrl_tmp.msr(MSR_DR) <= '0';
> > > ctrl_tmp.msr(MSR_RI) <= '0';
> > > ctrl_tmp.msr(MSR_LE) <= '1';
> > >
> > > these appear to be correct as defined according to figure 65
> > (p1063)
> > >
> > > however the remaining actions do not seem to be implemented
> > (p1064):
> > >
> > > Bits bit 5, TM, VEC, VSX, PR, FP, and PMM are set to 0.
> > > The TE field is set to 0b00.
> > > TM, FP, VEC, VSX, and bit 5 are set to 0.
> >
> > Right. We have a to-do list for architecture compliance. (We
> > haven't
> > implemented 32-bit mode or BE mode, for instance.)
>
> yeahh although we have 32 bit op modes (using microwatt
> decode1.vhdl, turned into CSV) we have yet to support the MSR 32bit
> global mode.
>
> LE/BE amazingly seems to work on LibreSOC, it was quite funny having
> the trap jump into 0x700 when testing against qemu (running
> singlestep under gdb), only to find that qemu traps change the LE bit
> and of course in qemu once that's changed gdb can't read registers
> correctly. sigh.
It can if you manually change endian in gdb no ?
> > > question: what effect would it have - bear in mind that we are
> > > following microwatt - if we implemented these changes to MSR?
> > bear in
> > > mind that we ignore most of them at the moment (MSR.LE being one
> > > notable exception), so the question is, in effect: does the Linux
> > > kernel *also* ignore them?
> >
> > The Linux kernel clearly needs PR to be set to zero and it also
> > expects FP, VEC, VSX, TM to be cleared. Setting TE to 0 is
> > necessary
> > once you implement the trace interrupt, otherwise you could get a
> > trace interrupt inside your first-level interrupt handlers, which
> > would be bad.
>
> ah :)
>
> > Similarly if you have floating-point and you don't set
> > FE0 and FE1 to 0 on an interrupt, there is the chance of taking a
> > floating-point program interrupt inside a first-level handler.
>
> whoops. ok appreciate the warning.
>
> > I'm not sure that all this counts as the Linux kernel "ignoring"
> > the
> > bits, but in general if you do what the architecture says, the
> > kernel
> > will be happier than if you don't.
>
> ha, that makes sense.
>
> i generally found this out when network reverse-engineering, despite
> not understanding at all what i was sending to the client or server
> :)
>
> thank you Paul
>
> l.
>
>
>
> _______________________________________________
> OpenPOWER-HDL-Cores mailing list
> OpenPOWER-HDL-Cores@mailinglist.openpowerfoundation.org
>
http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-hdl-cores
_______________________________________________
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] system call (sc) LEV "reserved field"
From: Benjamin Herrenschmidt @ 2020-07-27 4:29 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <CAPweEDws3LZYJuYmMuDd89Q5RWjHPYX3tWbQp9VjPZC_AFSDWg@mail.gmail.com>
On Fri, 2020-07-24 at 17:53 +0100, Luke Kenneth Casson Leighton wrote:
>
> a low-grade version of JIT translation, which is one solution.
> expensive, but a solution.
>
> although i have to ask why, for Embedded, they did not just recompile
> the source code, customised for that enduser application.
Because the distinction between "embedded" and "unix" is very blurry
and in many areas obsolete.
One can compile a single image that is meant to run on a wide variety
of system and even the "embedded" world wants that capability. Either
because they end up running some kind of "upstream" OS image, or
because they don't want to maintain completely different SW images for
all their products, etc...
> however this also actually illustrates precisely why i mentioned that
> for best results, a spec has to have different platform behaviour for
> Embedded as completely separate and distinct from UNIX.
This is not really true anymore. For example, do you consider your cell
phone or your TV "embedded" or "unix" ? They are both running Linux
after all...
> the rules for Embedded in RISCV state that traps are *not* needed for
> illegal instructions (it is up to an implementor to decide if they
> wish to add them). the Conformance Test Suite does *not* test for
> illegal instructions.
>
> this on the basis that Embedded Markets are typically one-off
> deployment, where the toolchain and all build source is "snapshotted"
> at product release time, used internally and the source code and
> toolchain almost never see the light of day. mainline upgrades are
> exceptionally rare.
There are quite a few counter examples even in the "embedded" market.
Especially when it comes to storage appliances. Some of these things
can even run CentOS.
> examples include Trinamic Stepper ASICs, which actually hit the
> shelves even before RISCV Standardisation was ratified.
>
> the binaries are in ROM. whatever trap spec incompatibility with
> "Latest and Greatest" are utterly irrelevant for them and their
> customers.
>
>
> so in that context, i am slightly confused to hear that for Freescale
> *Embedded* processors that there is even a binary incompatibility
> problem with lwsync *at all*.
>
> if you have time i'd love to hear more, what's the story there?
I forgot the details, but a specific core variant from FSL screwed up
the decode table and would trap on lwsync instead of ignoring the bit.
> > > but because the bit is ignored, there is no way that can be done.
> >
> > But that's fine because "sync" is a strict superset so ignoring the
> > bit
> > works just fine.
>
> in this case, yes.
>
>
> > > so whilst on the face of it, lwsync *sounds* like a
> > counterexample,
> > > instead (caveat, i do not know what FSL is), it seems more to
> > support
> > > the case *for* use of reserved bits raising illegal instructions
> > [on
> > > UNIX platforms]
> >
> > I fail to follow your logic. The trap case is a complete non-
> > starter
> > for an instruction meant to be a lightweight memory barrier.
>
> ok given that it is a "hint" type and not quite suited to "reserved"
> we are now at cross purposes.
>
> and, also, it is a special case that happens to gave, as one of its
> requirements, to be "lightweight" in order to be useful.
>
> > The
> > transparent "fallback" to a full memory barrier on the contrary
> > works
> > fine. There is never any case where "trapping an emulating" is the
> > desired behaviour.
>
> indeed... in this very special case that we have established, by it
> effectively being a "hint", falls completely outside of what i am
> concerned about
In *most* cases trap + emulation leads to unusable performances though.
Ben.
_______________________________________________
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] how do we test external interrupts?
From: Luke Kenneth Casson Leighton @ 2020-07-28 18:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4G6Y7WifJiPW+-O7s7+yPLLY-5WKccEp655qvFfbOt0Q@mail.gmail.com>
On Tuesday, July 28, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> I found what looks like the reference source:
> in
> https://github.com/torvalds/linux/blob/ab02b61f24c76b1659086fcc8b00cb
> eeb6e95ac7/Documentation/virt/kvm/devices/xics.rst
> > This device emulates the XICS (eXternal Interrupt Controller
> Specification) defined in PAPR.
i glanced through that. the definitions there are for the format of the
linux kernel ioctls (etc) and they happen to *contain* the same information
as is read from the hardware registers (in the case of microwatt, over a
wishbone bus), and therefore they must *be* reading the memory locations
associated with each XICS register
it's just that it's damn hard to interpret because the linux kernel is
written as a re-entrant FSM.
throwing a full-on linux kernel at the HDL is one way to test this, however
it would be slow and also cumbersome to debug.
i'd really like to brainstorm on how to do a piece-by-piece set of small
tests, so that by the time we actually get to run a linux kernel we have a
high degree of confidence that it would "just work".
what's needed:
* the core needs an incoming "interrupt notifier" wire (coming from XICS
presentation layer) in microwatt this is ext_irq_in
* the external interrupt wire in the core needs to trigger the PC to jump
to 0x500 (microwatt execute1.vhdl ext_irq_in goes high)
* a mini interrupt handler (at address 0x500) that then starts looking at
the XICS registers (via the wishbone bus) and "handles" it
* an actual peripheral of some kind which is connected to one of the XICS
"source" irq interrupt bits that generates the interrupt in the first place
this bundle of five bits of HDL which will also need an appropriate
wishbone arbiter capable of dealing with 64/32 bit integration *and* some
software is about the minimum i can think of (!)
oh and also if we want to run the sane binary under ISACaller it needs
implementing like in qemu or dolphin!
which is quite ridiculous but there you go :v
looking at the microwatt helloworld example i don't think it's set up for
interrupts
https://github.com/antonblanchard/microwatt/blob/master/hello_world/head.S
the 0x500 handler is a stub, there: i believe it goes into a 100% cpu
polling loop (see lib/console.c as well as hello_world.c)
this seems like a lot more work than formerly anticipated. however
throwing the linux kernel at the core and hoping does not inspire me with
deep feelings of joy :)
l.
--
---
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] how do we test external interrupts?
From: Jacob Lifshay @ 2020-07-28 16:50 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEz=so=F_Bqy0jF3aWperQ-ghAX-PcRK4ST1WF7Sct0_8p14sw@mail.gmail.com>
I found what looks like the reference source:
in
https://github.com/torvalds/linux/blob/ab02b61f24c76b1659086fcc8b00cbeeb6e95ac7/Documentation/virt/kvm/devices/xics.rst
> This device emulates the XICS (eXternal Interrupt Controller
Specification) defined in PAPR.
https://en.wikipedia.org/wiki/Power_Architecture_Platform_Reference
https://github.com/OpenPOWERFoundation/Linux-Architecture-Reference
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] how do we test external interrupts?
From: Samuel Falvo II @ 2020-07-28 16:41 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxTwXHe0KQ8=xHW41YX1dDoGv=bS+EEAD9BsohWzqem+w@mail.gmail.com>
On Tue, Jul 28, 2020 at 9:15 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> the *actual* name is "Logical Partition" (LPAR) although where on
I saw a reference to LoPAR in my searches, which appeared to be
something different from LPAR. I didn't research it further, though.
--
Samuel A. Falvo II
_______________________________________________
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] how do we test external interrupts?
From: Luke Kenneth Casson Leighton @ 2020-07-28 16:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEz=sonuUeOMOHyBw8iezd5t6GjMCRDx=Sr2XauvvcpGV+EnbA@mail.gmail.com>
On Tue, Jul 28, 2020 at 3:55 PM Samuel Falvo II <sam.falvo@gmail.com> wrote:
>
> I might be stating the obvious; but, according to
> https://www.kernel.org/doc/html/latest/virt/kvm/devices/xive.html, it
> looks like XICS is a POWER7- / POWER8-related specification.
> Wikipedia indicates POWER7 was released around 2010-ish. Maybe
> finding specs dated about that time would be a good place to look? (I
> tried but wasn't successful.)
yeah i've reviewed v2.07B which was POWER8 and there's nothing in
that, either. according to this:
https://github.com/qemu/qemu/blob/master/hw/intc/xics.c
the *actual* name is "Logical Partition" (LPAR) although where on
earth the relationship is with XICS, is completely unclear, and
reading the Chapter on LPAR Control (p927 v3.0B) gives nothing
obvious. searching for keywords "CPPR", "MFFR" also give nothing.
if we are deploying reverse-engineering and pattern-matching, this
looks very similar to microwatt xics.vhdl:
https://github.com/qemu/qemu/blob/master/hw/intc/xics_pnv.c
at least the memory set/get looks familiar, where qemu xics.c looks
more like it is more qemu-internals / qemu-plumbing
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] how do we test external interrupts?
From: Samuel Falvo II @ 2020-07-28 14:54 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDySLuS1NVLv71LZ_UXRRdfxWQ5WQ__1wkkx5JY9vS1mWA@mail.gmail.com>
I might be stating the obvious; but, according to
https://www.kernel.org/doc/html/latest/virt/kvm/devices/xive.html, it
looks like XICS is a POWER7- / POWER8-related specification.
Wikipedia indicates POWER7 was released around 2010-ish. Maybe
finding specs dated about that time would be a good place to look? (I
tried but wasn't successful.)
On Tue, Jul 28, 2020 at 6:31 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> i've started on the XICS controller, and have converted both the ICS and
> ICP. a simple unit test on XICS-ICS shows it to be functional.
>
> however we are hampered in several ways:
>
> 1) there does not appear to exist an actual accessible specification.
>
> 2) the only implementations are source code (linux kernel, qemu)
>
> 3) nobody else has written unit tests
>
> 4) given that XICS is involved in *external* interrupts, how do we even
> *begin* to write a unit test that runs under e.g. qemu and the simulator,
> here??
>
> so i'd like to open up the discussion to develop a strategy here.
>
> my feeling is that we may have to create a simulated peripheral (an
> interrupt driven 16550 UART) in ISACaller which would allow exploration,
> here.
>
> thoughts welcome.
>
> l.
>
>
>
> --
> ---
> 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
--
Samuel A. Falvo II
_______________________________________________
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] how do we test external interrupts?
From: Luke Kenneth Casson Leighton @ 2020-07-28 13:30 UTC (permalink / raw)
To: Libre-RISCV General Development
i've started on the XICS controller, and have converted both the ICS and
ICP. a simple unit test on XICS-ICS shows it to be functional.
however we are hampered in several ways:
1) there does not appear to exist an actual accessible specification.
2) the only implementations are source code (linux kernel, qemu)
3) nobody else has written unit tests
4) given that XICS is involved in *external* interrupts, how do we even
*begin* to write a unit test that runs under e.g. qemu and the simulator,
here??
so i'd like to open up the discussion to develop a strategy here.
my feeling is that we may have to create a simulated peripheral (an
interrupt driven 16550 UART) in ISACaller which would allow exploration,
here.
thoughts welcome.
l.
--
---
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] daily kan-ban update 27jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-27 20:51 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200727220648.972dbede6660b48fc266bbe1@platen-software.de>
On Monday, July 27, 2020, Tobias Platen <libre-soc@platen-software.de>
wrote:
>
> while the https://git.libre-soc.org/git/nmigen-soc.git was
>
nmigen-soc does not contain sram. i had to add it.
l.
--
---
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] daily kan-ban update 27jul2020
From: Tobias Platen @ 2020-07-27 20:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDy2HKE08tZLUdsh4VNWwqb4o+Qh0X1OG_9GcgX+GQxOHA@mail.gmail.com>
On Mon, 27 Jul 2020 20:46:08 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Mon, Jul 27, 2020 at 8:10 PM Tobias Platen
> <libre-soc@platen-software.de> wrote:
>
> > File "/home/isengaara/Hacking/lSOC/TEST/nmigen-soc/nmigen_soc/wishbone/sram.py", line 89, in elaborate
> > n_wrport = wrport.en.shape()[0]
> > TypeError: 'Shape' object is not subscriptable
>
> git pull on the nmigen-soc repo, i sorted this a couple weeks ago?
>
> l.
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
The https://github.com/nmigen/nmigen-soc repository was last updated was 5 days,
while the https://git.libre-soc.org/git/nmigen-soc.git was updated 8 days ago.
I assume that I am using the wrong one.
In this case I would have to update the scripts in dev-env-setup too.
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;h=255692bd91bdcd42b18ebd608787de77a23e01eb;hb=HEAD
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
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] daily kan-ban update 27jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-27 19:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200727211044.aca147ec0215b65b04190115@platen-software.de>
On Mon, Jul 27, 2020 at 8:10 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
> File "/home/isengaara/Hacking/lSOC/TEST/nmigen-soc/nmigen_soc/wishbone/sram.py", line 89, in elaborate
> n_wrport = wrport.en.shape()[0]
> TypeError: 'Shape' object is not subscriptable
git pull on the nmigen-soc repo, i sorted this a couple weeks ago?
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] daily kan-ban update 27jul2020
From: Tobias Platen @ 2020-07-27 19:10 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAEg7humQySZ8m=CtLxE+cgh0XbG++eJj=Wi0opC37OKLJ-_OFw@mail.gmail.com>
Today:
I was working on l0_cache.py where I got the following error.
ERROR: test_l0_cache_test_bare_wb (__main__.TestL0Cache)
----------------------------------------------------------------------
Traceback (most recent call last):
File "l0_cache.py", line 361, in test_l0_cache_test_bare_wb
vl = rtlil.convert(dut, ports=[])# TODOdut.ports())
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/back/rtlil.py", line 1056, in convert
fragment = ir.Fragment.get(elaboratable, platform).prepare(**kwargs)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/hdl/ir.py", line 39, in get
obj = obj.elaborate(platform)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/hdl/dsl.py", line 538, in elaborate
fragment.add_subfragment(Fragment.get(self._named_submodules[name], platform), name)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/hdl/ir.py", line 39, in get
obj = obj.elaborate(platform)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/hdl/dsl.py", line 538, in elaborate
fragment.add_subfragment(Fragment.get(self._named_submodules[name], platform), name)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen/nmigen/hdl/ir.py", line 39, in get
obj = obj.elaborate(platform)
File "/home/isengaara/Hacking/lSOC/TEST/nmigen-soc/nmigen_soc/wishbone/sram.py", line 89, in elaborate
n_wrport = wrport.en.shape()[0]
TypeError: 'Shape' object is not subscriptable
Am I using the wrong version of nmigen?
On Mon, 27 Jul 2020 11:38:33 -0700
Cole Poirier <colepoirier@gmail.com> wrote:
> Heads up Luke today is the 27th, 29th will be this wednesday, we have
> our biweekly OpenPower-Libre-SOC meeting
>
> Yesterday:
> * spoke to Luke about recruiting more project members and conversion
> of bitmap diagrams on wiki into svg
> * finished 180nm_single_core_test_asic_memlayout diagram conversion into svg
>
> Today:
>
> * finish conversion of comp_unit_req_rel bitmap to svg
> * finish conversion of comp_unit_multi_rw
> * documenting how to layout soclayout repo
> * creating one bug report under product Documentation per bitmap
> diagram for conversion to svg, in order to successfully coordinate
> this medium size substantial task. All svg diagram bugs will be
> children of the top level bug report "Bug 389 - Review all diagrams on
> wiki for translation into SVG" and will be listed in the description
> (comment #0) for easy birds-eye-viewing of the progress of this
> meta-task <https://bugs.libre-soc.org/show_bug.cgi?id=389#c0>
>
> Cole
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
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] daily kan-ban update 27jul2020
From: Cole Poirier @ 2020-07-27 18:38 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzuYRzhURO=wp_jht09mPwND1u06JCYS0umTaGZs3CJrA@mail.gmail.com>
Heads up Luke today is the 27th, 29th will be this wednesday, we have
our biweekly OpenPower-Libre-SOC meeting
Yesterday:
* spoke to Luke about recruiting more project members and conversion
of bitmap diagrams on wiki into svg
* finished 180nm_single_core_test_asic_memlayout diagram conversion into svg
Today:
* finish conversion of comp_unit_req_rel bitmap to svg
* finish conversion of comp_unit_multi_rw
* documenting how to layout soclayout repo
* creating one bug report under product Documentation per bitmap
diagram for conversion to svg, in order to successfully coordinate
this medium size substantial task. All svg diagram bugs will be
children of the top level bug report "Bug 389 - Review all diagrams on
wiki for translation into SVG" and will be listed in the description
(comment #0) for easy birds-eye-viewing of the progress of this
meta-task <https://bugs.libre-soc.org/show_bug.cgi?id=389#c0>
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] nmigen weekly monday meeting starting NOW.
From: Luke Kenneth Casson Leighton @ 2020-07-27 18:04 UTC (permalink / raw)
To: Libre-RISCV General Development
hi folks,
those bi-weekly nmigen meetings changed to weekly, i didn't realise.
consequently, that's right now (UTC 1800). logs will be at
https://freenode.irclog.whitequark.org/nmigen/2020-07-27 if anyone
misses it.
l.
---
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
page: next prev 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