From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 304] Define minimum viable interface set for 180nm ASIC
Date: Tue, 12 May 2020 12:13:06 +0000
Message-ID: <bug-304-13-g6ccZD1cE6@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=304
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
yehowshua i added a stub/starting-point ls180
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/ls180.py;h=77c5f1f7f7923cb8292499bac189ff1ce8f3b6ff;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c
also added a stub / dummy LPC function:
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/pinfunctions.py;h=e46be8d114f00bbf571092c4e7a9ec5ece39d04b;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c#l52
it will need its pin naming correcting, and also in ls180.py everything
including LPC moving to a single column.
we need to move quickly on this because Rudi is waiting for us
to communicate back to him the required peripheral set, and he
is experienced enough to know that we are well beyond the industry
standard time for making these decisions.
--
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
next prev parent reply index
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 11:15 [libre-riscv-dev] [Bug 304] New: " bugzilla-daemon
2020-05-08 14:36 ` [libre-riscv-dev] [Bug 304] " bugzilla-daemon
2020-05-08 14:37 ` bugzilla-daemon
2020-05-12 12:12 ` bugzilla-daemon
2020-05-12 12:13 ` bugzilla-daemon [this message]
2020-05-12 12:14 ` bugzilla-daemon
2020-05-20 22:14 ` bugzilla-daemon
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=bug-304-13-g6ccZD1cE6@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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