Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 17:09 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=379

Cole Poirier <colepoirier@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Cole Poirier <colepoirier@gmail.com> ---
Migrated to new toplevel "Libre-SOC Organization"

Bug 380 - First round of recruitment attempts on university and technical
mailing lists
<https://bugs.libre-soc.org/show_bug.cgi?id=380>

-- 
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] daily kan-ban update 12jun2020
From: Cole Poirier @ 2020-06-12 17:07 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDw2FqhkBXc2geWaVP2Jbv=YgdQqH3gED=HX4iFS2SzOyw@mail.gmail.com>

On Jun 12 2020, at 9:49 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> short for test_pipe_caller.py when typing on phone at 3am...

I'm slowly learning to read your abbreviated language.

_______________________________________________
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 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 17:05 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #14 from Alain D D Williams <addw@phcomp.co.uk> ---
Repost: as reply to email does not appear here:

> > alain sent something a few days ago.  he was able to ascertain that apache2
> > fastcgi redirection works perfectly, where nginx does not.

It could be my inexperience with nginx - but bugzilla documentation had a
strong
preference for apache.

> > rather than waste time working out why i am inclined to recommend a
> > deployment where apache2 operates on port 8080 120.0.0.1 and nginx does a
> > transparent proxy for bugs.libre-soc.org

> Sure, I think apache via nginx is fine. Alain, should the kanban board work
> after this is done?

Well - it worked under Apache so I do not see why not.

I tried this under Debian 10 - the current libre-soc machine runs Debian 9 -
but
I would be surprised if it made a difference -- famous last words.

I will also point it at the latest version of buzilla that I installed a few
days ago.

First thing is apache on port 8080, get that to work, then worry about
proxying.

-- 
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 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 16:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #13 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #12)
> (In reply to Luke Kenneth Casson Leighton from comment #11)
> > (In reply to Cole Poirier from comment #10)
> > > bugzilla product do discuss the specifics of these organizational matters.
> > > Can you please create a new component "Libre-SOC Organizational" for
> > > "Product: Libre-SOC's first SoC". Or would it be better to create a new
> > > bugzilla 'Product' "Libre-SOC Organization and Planning" like we have
> > > "Product Libre-riscv website"?
> > 
> > yep.  toplevel.
> 
> done, default cc is libre-soc-org@libre-soc.org and you are the default
> assignee, congratulations.

Thank you kindly. I'm looking forward to taking a very active role in the
organizational and 'project management' aspects while I slowly improve my
technical skills. The most important thing is that I continue to be very
diligent - as a take on a 'larger' role, with much more responsibility - in my
inviolable obligations under the charter to be transparent and operate based on
consensus decision making. It is new responsibility that I am being granted not
authority.

-- 
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 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 16:56 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=379

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Conferences                 |Planning
           Assignee|lkcl@lkcl.net               |colepoirier@gmail.com
                 CC|                            |libre-soc-org@lists.libre-s
                   |                            |oc.org
            Product|Libre-SOC's first SoC       |Libre-SOC Organisation

-- 
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 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 16:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=379

--- Comment #2 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #1)
> (In reply to Cole Poirier from comment #0)
> > Cole Poirier:
> they're generally unwelcome except in this case we actually have donations
> available.

Understood. I will take the time and diligence to properly respect each
community's guidelines.

When it comes to contacting official university faculty/student mailing lists,
the only option that I can think of is to send a polite email to the
administrators of these lists at each school/department. 

In the email I will ask if they can please share with their mailing list
(usually department student mailing lists will promote job/internship
opportunities, ours is like a donation-based, task-completion based
internship(?)) our letter that outlines an opportunity to work on a complex
real world hardware and software project, as well as get paid in donations by
NLNet for the tasks they complete. Is my presumption correct, or is there a
better method you can recommend? 

> it is however necessary to carefully research each organisation and find out.
> 
> for example, the FSF takes a dim view of recruitment spam on its losts. 
> they have a special "jobs" board.  you have to give a small donation to use
> it.
> 
> except... we are not *looking* for "jobs" because we are not a commercial
> entity.

Indeed, I have been and will continue to be very careful to assert this
essential distinction in my communications about this.

> sigh.
> 
> so on that one we fall between two stools.

Don't despair, I'll be trying to put some significant effort into this, because
you've already being at it for years, but now I think you really have more
important things to take care of and devote your focus to. 

May I be delegated the task of recruitment (non-commercial 'contracted' work on
tasks that are eligible for donations)? I will keep the project informed of my
efforts here... Well actually I think I'll create a new bug for this under the
new top-level "Libre-SOC Organization" bugzilla product. I understand that this
task requires tact, patience, and a lot of time. I am willing to devote the
necessary effort and time, and would like to be explicitly delegated this task
so that I can work on this officially. I'd like some guidelines from the
project members as to how I should represent Libre-SOC in my communications,
and further input on what I should do, as this will be my responsibility,
however I am not solely 'in charge' of this because that is explicitly not how
our organization is structured.

> yes, basically, each organisation will have some interaction guidelines, and
> i would recommend contacting the organisers privately to ask their advice.
> 
> this will take time.

Your tact is something I will ensure to preserve in my communications on behalf
of the project.

-- 
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] daily kan-ban update 12jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-12 16:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8C5FCBF1-15B4-4C3F-8187-63303B03CF3B@getmailspring.com>

On Friday, June 12, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

>
> suggestion. take alu test_pipe_caller.py and cut out absolutely every
> test_* except for one, make sure to pick one with only one assembly
> instruction. (or take copy of tpc.py, call it tpc2.py)


>
short for test_pipe_caller.py when typing on phone at 3am...


>
>

-- 
---
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] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 16:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #11)
> (In reply to Cole Poirier from comment #10)
> > bugzilla product do discuss the specifics of these organizational matters.
> > Can you please create a new component "Libre-SOC Organizational" for
> > "Product: Libre-SOC's first SoC". Or would it be better to create a new
> > bugzilla 'Product' "Libre-SOC Organization and Planning" like we have
> > "Product Libre-riscv website"?
> 
> yep.  toplevel.

done, default cc is libre-soc-org@libre-soc.org and you are the default
assignee, congratulations.

-- 
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] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: Alain D D Williams @ 2020-06-12 16:37 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-307-13-Twpv6GMLqw@https.bugs.libre-soc.org/>

On Fri, Jun 12, 2020 at 03:54:42PM +0000, bugzilla-daemon@libre-soc.org wrote:

> > alain sent something a few days ago.  he was able to ascertain that apache2
> > fastcgi redirection works perfectly, where nginx does not.

It could be my inexperience with nginx - but bugzilla documentation had a strong
preference for apache.

> > rather than waste time working out why i am inclined to recommend a
> > deployment where apache2 operates on port 8080 120.0.0.1 and nginx does a
> > transparent proxy for bugs.libre-soc.org

> Sure, I think apache via nginx is fine. Alain, should the kanban board work
> after this is done?

Well - it worked under Apache so I do not see why not.

I tried this under Debian 10 - the current libre-soc machine runs Debian 9 - but
I would be surprised if it made a difference -- famous last words.

I will also point it at the latest version of buzilla that I installed a few
days ago.

First thing is apache on port 8080, get that to work, then worry about proxying.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>

_______________________________________________
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 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 16:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=376

--- Comment #6 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #5)
> correct.  this is what the original quad core was intended for.
[snip]
> thus, only 1x 32 bit DDR 800 mhz RAM interface would be perfectly
> sufficient... for *that* scenario (hence the $4 target price), and it would
> only need around a 350mW power budget (the DRAMs themselves, that is.  the
> SoC DRAM drivers would i *think* be around an additional 150mW. have to
> check).

Thanks for this clarification, helps a lot for understanding our product's (or
now products' ?) market segmentation.

> the target being discussed here, by virtue of having interfaces that at full
> speed consume an estimated 8 watts, these are far outside a
> tablet/smartphone 100 million+ volumes power budget.
> 
> it is basically a radically different market: GPU Graphics Card market,
> basically.

Oh, that also makes a lot more sense. Kanban will definitely help me keep track
of and make sense of these related but separate 'tracks'.
> 
> *if correct*, with the (unconfirmed, anticipated) higher power demands, a
> plastic package is in no way going to be adequate.
> 
> it will have to be ceramic, with a metal top.  i'd also suggest a minimum 25
> mm square, to help with thermal dissipation.
> 
> the actual pincount, due to the SERDES, might be quite reasonable (except
> there's a lot of them): maybe 400 to 500 or so.
> 
> we will need people who know exactly what they are doing, here, who have
> done this type of high power high speed ASIC before.
> 
> Rudi is the person who springs to mind, not just from the technical
> capability and 25+ years experience, he also likes what we are doing.
> 
> we need some numbers.

Wow that is radically different, and very, very exciting! I'm gladdened to hear
of Rudy's experience as well as his affinity towards our project. Is it
possible that he may know some other people that would be interested in either
assisting him, or working on another part of the project?  Of course receiving
donations for all of their completed tasks. Or if we are able to find some more
investors, we can pay them for new project requirements that are not covered
under the scope of our existing NLNET 2018 and 2019 grants?

-- 
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 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 16:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #10)
> (In reply to Luke Kenneth Casson Leighton from comment #9)
> > (In reply to Cole Poirier from comment #8)
> > > I like bugzilla and think it's fit for purpose,
> > 
> > i like it other than it's centralised (has no option to store its data in a
> > git repository).
> 
> Interesting... What is required for such decentralization? In other words
> why can't bugzilla be backed by a git data store?

probably simply because nobody came up with the idea.  bugseverywhere which
does exactly that is not very commonly used.

>  
> > > but I'd also like to be able to view some of the information on a much more
> > > structured (visually) form,
> > 
> > yes me too.  i installed graphviz on the server (xdot) so that dependency
> > graphs now work.
> > 
> > however a kanban board is much superior.
> 
> Saw that, it's cool, but not quite as useful as the board as it does not
> show that >300 of the <400 total bugs are assigned to you... among other
> things :)
> 
> > alain sent something a few days ago.  he was able to ascertain that apache2
> > fastcgi redirection works perfectly, where nginx does not.
> > 
> > rather than waste time working out why i am inclined to recommend a
> > deployment where apache2 operates on port 8080 120.0.0.1 and nginx does a
> > transparent proxy for bugs.libre-soc.org
> 
> Sure, I think apache via nginx is fine. Alain, should the kanban board work
> after this is done?
> 
> > yes.
> > 
> > example: not having a visual tracker stops people from appreciating that of
> > the 370 bugs on here, well over 300 of them are specifically assigned to me.
> 
> Indeed. I think we need a space separate from the "libre-riscv website"

ah ok

> bugzilla product do discuss the specifics of these organizational matters.
> Can you please create a new component "Libre-SOC Organizational" for
> "Product: Libre-SOC's first SoC". Or would it be better to create a new
> bugzilla 'Product' "Libre-SOC Organization and Planning" like we have
> "Product Libre-riscv website"?

yep.  toplevel.

-- 
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 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 16:25 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=379

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #0)
> Cole Poirier:
> > > Will also work on a blurb for soliciting new members, and research some
> > > possible methods of publicising our search for memebers.
> 
> lkcl:
> > my partner marie has a contact at HK University, please do point her at it
> > when you have it written. (a short wiki page is great).
> 
> Will do, thanks this is a great place to start. Also will be contacting U of
> T, my sister is a 3rd year ECE student there. Planning on contacting as many
> CS and ECE listservs as I can find. Is this permitted?

they're generally unwelcome except in this case we actually have donations
available.

it is however necessary to carefully research each organisation and find out.

for example, the FSF takes a dim view of recruitment spam on its losts.  they
have a special "jobs" board.  you have to give a small donation to use it.

except... we are not *looking* for "jobs" because we are not a commercial
entity.

sigh.

so on that one we fall between two stools.

yes, basically, each organisation will have some interaction guidelines, and i
would recommend contacting the organisers privately to ask their advice.

this will take time.

-- 
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] daily kan-ban update 12jun2020
From: Cole Poirier @ 2020-06-12 16:18 UTC (permalink / raw)
  To: Libre-RISCV General Development
  Cc: Marie Raymond, Libre-RISCV General Development
In-Reply-To: <CAPweEDwd+TKSpNb1_Ha1n56OLvv8YdFxZhCBK+UAgMM0haytFg@mail.gmail.com>

On Jun 12 2020, at 8:53 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> i believe i did this initially :)
> 
> btw *do* create save files and actually save them regularly.  gtkwave
> has a
> habit of segfaulting, particularly if you use tabs.

Ooof. Thank you for this timely tip, before I've had to experience the
inconvenience of gtkwave segfaulting myself.

> if you do that on code that you have yourself written, and also viewed the
> graphviz diagrams, this cross-association will go faster.
> 
> can i suggest looking at the bperm unit test vcd files, first?

That is an excellent idea. Thank you. I think you suggested it on bug
#325 TRAP pipeline, but I was reading in chronological order and was
working based off of your earlier suggestion in comment #74 "ok. 
suggestion. take alu test_pipe_caller.py and cut out absolutely every
test_* except for one, make sure to pick one with only one assembly
instruction. (or take copy of tpc.py, call it tpc2.py) then run it and
load the generated alu_simulator.gtk in gtkwave." By the way I couldn't
find anything that contained either 'tpc' or 'tpc2' using grep and find.
Will look at bpermd in gtkwave now :)

> my partner marie has a contact at HK University, please do point her
> at it
> when you have it written. (a short wiki page is great).
> 
> we have something on the front page already however it is embedded
> *in* the
> front page and so is not really clear.
> 
> we also cannot call it "jobs" because sigh that implies salaries, per-hour
> payments, employment, that we will cover their insurance costs, holidays
> and so on.  wark-wark.

Appreciated. Created a bug report so that this doesn't get lost in "old
style 'keeping track of things' (an oxymoron) with email".
https://bugs.libre-soc.org/show_bug.cgi?id=379

_______________________________________________
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 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 16:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=376

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---


> On Friday, June 12, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
> On Jun 12 2020, at 7:06 am, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> > It's just possibe that we may not *need* 4k at 120 fps.
> > Certainly there are many potential applications for our chip that
> > don't need that kind of video. 

> I concur. If we are planning on selling 100 million units, shouldn't we
> have several different levels of IO/GPU capablilty, each targeting
> different power requirements? For example, a phone or a tablet doesn't
need 4k 120HZ video right?

correct.  this is what the original quad core was intended for.  RGBTTL
connecting directly to an 800x600 low cost LCD, or, via a TI SN75LVDS83b, to a
1024x600 or 1280x800 LCD.  or a Solomon SSD2828 to do MIPI.

the GPU and framebuffer requirements for such portable devices are far lower. 
you can even get away with only a 30fps update speed, halving the framebuffer
power and GPU requirements.

thus, only 1x 32 bit DDR 800 mhz RAM interface would be perfectly sufficient...
for *that* scenario (hence the $4 target price), and it would only need around
a 350mW power budget (the DRAMs themselves, that is.  the SoC DRAM drivers
would i *think* be around an additional 150mW. have to check).


the target being discussed here, by virtue of having interfaces that at full
speed consume an estimated 8 watts, these are far outside a tablet/smartphone
100 million+ volumes power budget.

it is basically a radically different market: GPU Graphics Card market,
basically.

*if correct*, with the (unconfirmed, anticipated) higher power demands, a
plastic package is in no way going to be adequate.

it will have to be ceramic, with a metal top.  i'd also suggest a minimum 25 mm
square, to help with thermal dissipation.

the actual pincount, due to the SERDES, might be quite reasonable (except
there's a lot of them): maybe 400 to 500 or so.

we will need people who know exactly what they are doing, here, who have done
this type of high power high speed ASIC before.

Rudi is the person who springs to mind, not just from the technical capability
and 25+ years experience, he also likes what we are doing.

we need some numbers.

-- 
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 379] New: Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 16:09 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=379

            Bug ID: 379
           Summary: Create wiki page for recruitment letter to
                    Universities (& etc.) to point to
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Conferences
          Assignee: lkcl@lkcl.net
          Reporter: colepoirier@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

Cole Poirier:
> > Will also work on a blurb for soliciting new members, and research some
> > possible methods of publicising our search for memebers.

lkcl:
> my partner marie has a contact at HK University, please do point her at it
> when you have it written. (a short wiki page is great).

Will do, thanks this is a great place to start. Also will be contacting U of T,
my sister is a 3rd year ECE student there. Planning on contacting as many CS
and ECE listservs as I can find. Is this permitted? Are there any procedures,
regulations, or recommendations when it comes to cold contacting mailing list
registrars with a request to share our letter informing students (and faculty?)
of the opportunity to "work on complex and interesting libre hardware/software
and receive tax deductible charitable donations for their contributions?"

After university engineering and computer science mailing lists, maybe I should
try tech and hardware forums? Perhaps both the professional and enthusiast tech
forums, because people like Jacob and I watch things like Gamer's Nexus on
youtube, so there may be others that we can find there?

> we have something on the front page already however it is embedded *in* the
> front page and so is not really clear.

I agree. I'll write something up and post it on the wiki, will post the link
here when its up.

> we also cannot call it "jobs" because sigh that implies salaries, per-hour
> payments, employment, that we will cover their insurance costs, holidays
> and so on.  wark-wark.

Don't worry, I got on that same page... months ago? It's hard to forget when
it's been discussed so many times on list.

-- 
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 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 15:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #10 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> (In reply to Cole Poirier from comment #8)
> > I like bugzilla and think it's fit for purpose,
> 
> i like it other than it's centralised (has no option to store its data in a
> git repository).

Interesting... What is required for such decentralization? In other words why
can't bugzilla be backed by a git data store?

> > but I'd also like to be able to view some of the information on a much more
> > structured (visually) form,
> 
> yes me too.  i installed graphviz on the server (xdot) so that dependency
> graphs now work.
> 
> however a kanban board is much superior.

Saw that, it's cool, but not quite as useful as the board as it does not show
that >300 of the <400 total bugs are assigned to you... among other things :)

> alain sent something a few days ago.  he was able to ascertain that apache2
> fastcgi redirection works perfectly, where nginx does not.
> 
> rather than waste time working out why i am inclined to recommend a
> deployment where apache2 operates on port 8080 120.0.0.1 and nginx does a
> transparent proxy for bugs.libre-soc.org

Sure, I think apache via nginx is fine. Alain, should the kanban board work
after this is done?

> yes.
> 
> example: not having a visual tracker stops people from appreciating that of
> the 370 bugs on here, well over 300 of them are specifically assigned to me.

Indeed. I think we need a space separate from the "libre-riscv website"
bugzilla product do discuss the specifics of these organizational matters. Can
you please create a new component "Libre-SOC Organizational" for "Product:
Libre-SOC's first SoC". Or would it be better to create a new bugzilla
'Product' "Libre-SOC Organization and Planning" like we have "Product
Libre-riscv website"?

-- 
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] daily kan-ban update 12jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-12 15:53 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Marie Raymond
In-Reply-To: <96D745C1-889B-4E67-82B4-39F479E5E309@getmailspring.com>

On Friday, June 12, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

> Yesterday: Frustration with gtkwave timiming diagrams...
>
> Today: Frustration with my self for not thinking to zoom the gtkwave
> timing diagrams out far enough to be able to see the changes in wire
> state.... *bangs head on desk* Oh well, at least now I've figured it out
> and can start making forward progress.


i believe i did this initially :)

btw *do* create save files and actually save them regularly.  gtkwave has a
habit of segfaulting, particularly if you use tabs.




>  Will spend today trying to
> understand the relationship between a simple alu test in nmigen and the
> corresponding timing diagram in gtkwave.


 if you do that on code that you have yourself written, and also viewed the
graphviz diagrams, this cross-association will go faster.

can i suggest looking at the bperm unit test vcd files, first?

 Will also work on a blurb for
> soliciting new members, and research some possible methods of
> publicising our search for memebers.


my partner marie has a contact at HK University, please do point her at it
when you have it written. (a short wiki page is great).

we have something on the front page already however it is embedded *in* the
front page and so is not really clear.

we also cannot call it "jobs" because sigh that implies salaries, per-hour
payments, employment, that we will cover their insurance costs, holidays
and so on.  wark-wark.

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] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 15:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #8)
> I think having the kanban board will help centralize our
> communication/planning for the the source code, but be especially helpful
> for working on the interfaces and final product specifications as well as
> with visualizing timelines.

yes.

> I like bugzilla and think it's fit for purpose,

i like it other than it's centralised (has no option to store its data in a git
repository).

> but I'd also like to be able to view some of the information on a much more
> structured (visually) form,

yes me too.  i installed graphviz on the server (xdot) so that dependency
graphs now work.

however a kanban board is much superior.

> and be able to put a lot of the info that's
> spread across various bug reports and wiki pages into a central interface
> for a more high-level overhead view of the various tracks of the project.
> What's the status of this bug report currently Alain?

alain sent something a few days ago.  he was able to ascertain that apache2
fastcgi redirection works perfectly, where nginx does not.

rather than waste time working out why i am inclined to recommend a deployment
where apache2 operates on port 8080 120.0.0.1 and nginx does a transparent
proxy for bugs.libre-soc.org


> Once it's up and
> running I'll work on taking the information from wiki pages and mailing list
> discussions and integrating it into the specs for the interface bugs on
> bugzilla. Do you (libre-soc devs) think this an action will be useful?

yes.

example: not having a visual tracker stops people from appreciating that of the
370 bugs on here, well over 300 of them are specifically assigned to me.

-- 
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 377] possible bug in Simulator Mem ld/st function
From: bugzilla-daemon @ 2020-06-12 15:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-377-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=377

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
problem "solved":

diff --git a/src/soc/decoder/isa/caller.py b/src/soc/decoder/isa/caller.py
index f76afda..7dfcec1 100644
--- a/src/soc/decoder/isa/caller.py
+++ b/src/soc/decoder/isa/caller.py
@@ -51,6 +51,7 @@ class Mem:
     def _get_shifter_mask(self, wid, remainder):
         shifter = ((self.bytes_per_word - wid) - remainder) * \
             8  # bits per byte
+        shifter = remainder * 8
         mask = (1 << (wid * 8)) - 1
         print ("width,rem,shift,mask", wid, remainder, hex(shifter),
hex(mask))
         return shifter, mask

is this something that we need to put under the control of a BE/LE MSR flag?

-- 
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 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 15:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=376

Cole Poirier <colepoirier@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |colepoirier@gmail.com

--- Comment #4 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3) 
> i am inclined to seriously recommend at least two separate OMI interfaces
> (with the option to use them in parallel), one to be connected to a video
> DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> with the option to say "i don't care about that, just use one or both for
> general shared memory"

I think this is an especially good idea given the performance loss APUs usually
suffer from using system RAM. I think it also makes sense to have the faster
wider memory bus for the graphics data so we can have a less power hungry
'general' data bus (as in no 3D graphics, or anything requiring MASSIVE data
paths, and therefore lots of power hungry SERDES). Is this correct?

> in SBC circumstances, where power is a concern and speed is not, a single
> lane would be used, to a single OMI chip.
[snip]
> in the "video card" scenario, the two lanes would again connect to separate
> OMI DRAMs, *however*, the framebuffer would *specifically* be mapped to
> *only* one of those OMI DRAMs, and the OS memory specifically mapped to
> the *other* OMI DRAM.

I think this reconfiguration is key to expanding the market segments the chip
is suitable for use in.

> supporting this would need some quite complex dynamic Wishbone Bus Arbiters,
> with an awful lot of MUXes on the address and data lines.  great care will
> be needed to ensure that latency is not introduced.

Should be quite an interesting and very complex challenge, hopefully for some
new recruits and not just you to do Luke.

-- 
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 378] New: Additional project management infrastructure
From: bugzilla-daemon @ 2020-06-12 15:17 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=378

            Bug ID: 378
           Summary: Additional project management infrastructure
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: colepoirier@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

Hi Libre-SOC members, there was discussion of using a kanban board on top of
buzilla a few weeks ago (bug #307). I'd like to know if there is additional
project management infrastructure that anyone thinks is needed or could help us
be better organized and more productive? I genuinely have no idea, but I know
some of you have extensive experience working on very large and complex
projects, so I think it's worth while to ask. Luke, I know you need more people
helping with the technical code, I'm going to start trying to recruit more devs
today. Do you also need help with project management and organizational things?
Do you have any suggestions of things that I could do or implement to help
here?

-- 
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 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 15:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=376

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #2)
> > 4k is 1200 megabytes per second: 37.5% *percent* of the total memory
> > bandwidth consumed by a 4k 60fps framebuffer!  and if people wanted
> > 120 fps instead, that's now a staggering 75% of a single OMI interface
> > dedicated to the framebuffer!
> 
> Raptor was saying that they were really looking for 1080p @60fps.
> So we shouldn't be worried about 4k for now.

ok great.  so that's only (!) 500 mbytes / sec.  just to check:
>>> 1920*1080*4
8294400
>>> 1920*1080*4*60
497664000
>>> 1920*1080*4*60/1e6
497.664

500*8 = 4 gigabits / sec.  so any PCIe (or other SERDES) would need to be
a minimum 4 GHz just to transfer the memory required to keep the framebuffer
100% occupied.

i am inclined to seriously recommend at least two separate OMI interfaces
(with the option to use them in parallel), one to be connected to a video
DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
with the option to say "i don't care about that, just use one or both for
general shared memory"

in SBC circumstances, where power is a concern and speed is not, a single
lane would be used, to a single OMI chip.

in SBC circumstances where power is not a concern and speed is, but there
is a requirement for higher-performance general-purpose CPU/GPU workloads
without demanding video, the two lanes would be dedicated to talk in parallel
to a single dual-ported OMI chip

*or*

the two lanes would be connected to *striped* memory (interleave odd/even
banks using low-bits of the address), across two separate OMI DRAMs

in the "video card" scenario, the two lanes would again connect to separate
OMI DRAMs, *however*, the framebuffer would *specifically* be mapped to
*only* one of those OMI DRAMs, and the OS memory specifically mapped to
the *other* OMI DRAM.

supporting this would need some quite complex dynamic Wishbone Bus Arbiters,
with an awful lot of MUXes on the address and data lines.  great care will
be needed to ensure that latency is not introduced.

-- 
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 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 15:09 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=307

Cole Poirier <colepoirier@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |colepoirier@gmail.com

--- Comment #8 from Cole Poirier <colepoirier@gmail.com> ---
I think having the kanban board will help centralize our communication/planning
for the the source code, but be especially helpful for working on the
interfaces and final product specifications as well as with visualizing
timelines. I like bugzilla and think it's fit for purpose, but I'd also like to
be able to view some of the information on a much more structured (visually)
form, and be able to put a lot of the info that's spread across various bug
reports and wiki pages into a central interface for a more high-level overhead
view of the various tracks of the project. What's the status of this bug report
currently Alain? Once it's up and running I'll work on taking the information
from wiki pages and mailing list discussions and integrating it into the specs
for the interface bugs on bugzilla. Do you (libre-soc devs) think this an
action will be useful?

-- 
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 377] possible bug in Simulator Mem ld/st function
From: bugzilla-daemon @ 2020-06-12 14:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-377-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=377

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|lkcl@lkcl.net               |mtnolan2640@gmail.com

-- 
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 377] New: possible bug in Simulator Mem ld/st function
From: bugzilla-daemon @ 2020-06-12 14:58 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=377

            Bug ID: 377
           Summary: possible bug in Simulator Mem ld/st function
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

michael, hi,

it looks like there might be a bug in caller.py Mem ld/st.  by accident
i asked a byte-store (stb) to write to address 0x9.  the memory-dump
(fu/compunits/test/test_compunit.py) dumps out the internal dictionary
(sim.mem.mem.items()) however it uses sim.mem.ld to initialise the
nmigen Memory object.

* bytes per word is 8
* address 9 divided by 8 is 1
* remainder is also 1.

does this mean that the LD/ST is being word-order realigned?


Writing 0xee to ST 0x9 memaddr 0x1/1
width,rem,shift,mask 1 1 0x30 0xff
mem @ 0x1: 0xabeeef0187654321
None
carry already done? 0b0
get_cu_outputs 2 0
after got outputs, rd_rel, wr_rel, wrmask:  0b0 0b0 0b0
busy 1
busy 1
busy 1
busy 0
check cu outputs stb 3, 1(2) {}
check extra output 'stb 3, 1(2)' 0 0
sim mem dump
         0 5432123412345678
         1 abeeef0187654321
         4 1828384822324252
nmigen mem dump
         0 5432123412345678
         1 abcdef018765ee21
         2 0000000000000000
         3 0000000000000000
         4 1828384822324252
         5 0000000000000000

-- 
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

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