From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 22may2020
Date: Fri, 22 May 2020 12:10:11 -0700
Message-ID: <3C8C9F70-B1BB-4A9C-8EEB-14EA91B6E0C4@getmailspring.com> (raw)
In-Reply-To: <CAPweEDwtA3H9yP0JGQ2CvoR0ZbT0O2hasTbqam+tw7zQmKJ=Dg@mail.gmail.com>
On May 22 2020, at 8:02 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> * attended both OpenPOWER weekly coffee calls which were nice to do,
> especially learning about microwatt first boot and also what Cesar does.
> both very cool.
Would you mind giving a one line description here of what Cesar does?
I'd be interested to know as well.
> y'know... i have to say, i am not often aware at the time because i take
> breaks and binge watch series episodes (Stargate SG1 at present, but only
> because i ran out of American Ninja Warrior episodes), but each day when
> actually written out does seem to be one hell of a lot. this probably
> because i don't do anything else, the entire day.
From an outsiders perspective, Luke, it appears as if you never sleep!! :)
> * keep an eye out for Cole. i couldn't work it out, either. might need
> your help, Michael.
Appreciated, very much appreciated. I spent all of yesterday failing to
get bpermd to work correctly, upon reflection today, since I'm pretty
sure I've tried all possible reverse indexing (e.g. 63-i, 7-i)
permutations, I suspect that I may be missing a line? Or something else
that I causing my module to behave close-ish(very ish) to correctly,
since it produces bit patterns that are usually off-by-one but in
but the bit that is off tends to move around the 'result area' that is
the least significant byte of output ra.
> work some on the bperm module with Cole.
> --Michael
I appreciate it Michael, in the mean time, I will work on the corilis2
chroot script, I believe it is almost complete, just have to setup a
user-USERNAME.mk file that sets up the include paths for alliance correctly.
Cole
_______________________________________________
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: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 15:02 Luke Kenneth Casson Leighton
2020-05-22 15:19 ` Michael Nolan
2020-05-22 15:39 ` Luke Kenneth Casson Leighton
2020-05-22 19:10 ` Cole Poirier [this message]
2020-05-22 19:18 ` Tobias Platen
2020-05-22 19:33 ` Luke Kenneth Casson Leighton
2020-05-23 1:56 ` Cesar Strauss
2020-05-23 2:41 ` Luke Kenneth Casson Leighton
2020-05-23 10:24 ` Cesar Strauss
2020-05-23 11:03 ` Luke Kenneth Casson Leighton
2020-05-23 11:53 ` Cesar Strauss
2020-05-23 12:08 ` Luke Kenneth Casson Leighton
2020-05-23 18:16 ` Cole Poirier
2020-05-22 19:59 ` Jacob Lifshay
2020-05-22 20:04 ` Luke Kenneth Casson Leighton
2020-05-22 20:12 ` Luke Kenneth Casson Leighton
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=3C8C9F70-B1BB-4A9C-8EEB-14EA91B6E0C4@getmailspring.com \
--to=colepoirier@gmail.com \
--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