►
From YouTube: CHIPS Alliance TSC Meeting - 2021-11-30
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
B
F
F
G
It's
a
bit
muffled,
sometimes
so
kind
of
sorry.
If
I
asked
my
phone
sure
okay,
um
so
let
me
just
kind
of
close
a
few
things
in
my
desktop
just
so
they
don't
share
too
much,
but
uh
one
of
the
things
that
we've
been
working
with
uh
recently-
and
I
can
give
you
a
broader
context,
because
the
two
bullets,
like
the
agenda,
somewhat
related.
G
uh
So,
as
you
know,
we've
been
heavily
involved
with
fpgas
and
different
kinds
of
tools
for
fpgas
and
making
fpgas
more
like
software,
which
means
that
we
need
open
source
tools
as
well
as
ip
as
well
as
other
things.
But
tools
have
been
a
particular
focus,
especially
that
you
know,
tools
is
also
one
of
the
things
that
chips
works
with.
So
much
of
this
work
has
been
historically
done
as
part
of
a
sim
project
called
symbiflow,
which
was
independent
of
anything.
It
was
obviously
supported
by
google.
G
It
was
supported
by
micro
and
a
bunch
of
other
entities,
but
it
wasn't
specifically
a
chips.
Alliance,
um
quicklogic
has
also
kind
of
participated
and
has
been
participating,
they're
also
a
member
and,
generally
speaking,
it
has
been
an
enabler
for
the
community,
because
anyone
that
designs,
asics
also
kind
of
works
with
fpgas
by
default.
G
That
framework
is
essentially
focused
around
making
sure
that
whatever
we
build
in
terms
of
open
source
tooling
continues
to
work
and
continues
to
perform.
We
can
see
how
it
behaves
confirmed
with
you
know,
other
kinds
of
tools
there's
also
multiple
choices
in
the
open
source,
fpga
world,
for
example,
vtr
or
next
pnr
for
placing
route.
uh
So
you
know
you
want
to
see
how
well
they
behave
against
different
designs
and
also
you
want
to
compare
different
designs
and
see
where
the
holes
are
and
just
kind
of
uh
continue
moving
forward.
G
So
the
fpga
toolbar
has
been
a
very
useful
and
instrumental
in
us
kind
of
making
progress
and
not
going
backwards.
It's
kind
of
like
sv
tests
for
system
dialogue,
um
so
we've
built
this
framework.
um
I
actually,
I
should
have
probably
prepared
some
material
just
to
show
you
uh
the
results,
but
I
think
we
can
probably
find
them
online
to
be
honest,
uh
uh
so
originally
yeah.
The
fba
toolkit
is
of
course
living
inside
of
sims
law
right.
It
has
its
own
like
documentation,
we're
testing,
different
kinds
of
designs
and
devices.
G
So
symbiflow
as
such
was
like
always
a
temporary.
uh
You
know,
name
and
temporary
uh
situation,
we're
looking
for
a
place.
So
that's
the
the
sorry.
The
results
are
not
really
there.
uh
So
we
are
working
and
looking
at
how
do
we
make
this
tool
chain
sustainable?
How
do
we
contribute
the
things
that
we're
building
into
a
body
that
would
take
good
care
of
them
and
chips,
alliance,
kind
of
appeared
and
grew?
In
the
meantime,
it
became
a
good
place
hosting
kind
of
a
lot
of
interest.
G
You
know
useful
projects
and
we
think
you
know
all
the
fpga
stuff
we're
doing
fits
there
very
well.
We
also
have,
as
you
know,
a
number
of
fpga
vendors,
either
in
or
applying
to
become
part
of
a
chips
alliance,
and
one
of
their
interests
is
in
in
that
particular
body
of
work.
So
so
yeah.
Essentially
that's
the
history
of
fpga
tool
perth.
It's
not
the
only
project
to
be
applying,
but
it's
kind
of
big
enough
and
separate
enough
that
we
decided
to
to
kind
of
make
it
into
a
separate
application.
G
G
uh
But
at
the
same
time
the
project
is
kind
of
a
separate
tool
that
deserves
like
its
own
life
and
perhaps,
of
course,
over
time,
we'll
decide
that
hey,
let's
like
merge
this
and
that
project
together,
but
for
now
we
think
it's
kind
of
useful
to
have
it
as
a
separate
tool
and
then
over
time.
Other
simplified
tools
will
also
be
joining.
G
G
There
is
already
the
fpga
interchange
format,
um
that's
part
of
uh
chip's
alliance,
that
mache
is
uh
heading
um
so
yeah.
This
is
the
second
project
in
the
series.
It's
not
gonna
be
50
projects
right.
I
think
in
total
it's
probably
going
to
be
four
at
most,
but
uh
uh
just
mentioning
this
uh
that's
kind
of
our
proposed
solution.
We
we
did
a
sandbox
application
for
now,
because
we
thought
it's
kind
of
it's
a
good.
um
What
you
call
it.
G
It's
a
good
practice
right
to
get
the
soundback
operation
through
first
and
then
figure
out
the
remaining
stuff
for
the
graduation
obligation,
but
yeah.
That's
that's
the
whole
background
and
I
wanted
to
perhaps
like
I
initially
wanted
to
kind
of
put
it
forward
for
a
vote,
but
uh
before
the
meeting.
But
then
I
thought
you
know
it's
better
to
have
a
short
discussion
here
and
hear
your
thoughts
and
then
kind
of
do
a
vote
interactively
if
we're
ready.
A
B
G
G
You
know
it
doesn't
do
anything
really
but
of
course
we're
going
to
apply
for
the
next
level
almost
immediately
right
so
kind
of
by
then
it's
pretty
good
to
know
what
you're
voting
for,
but
just
saying
that
the
vote
today
is
not
going
to
be
like
very
dramatic.
It's
uh
essentially
on
allowing
this
project
to
to
transfer
into
and
join
chip's
alliance.
G
G
I
G
B
G
F
F
G
E
G
A
G
G
G
G
B
G
For
uh
just
rolling
back,
I
appreciate
it.
I
think
that's
a
meaningful
addition,
because
that's
the
kind
of
thing
we
want
to
encourage
and
that
it's
obvious
for
me,
but
it's
it
might
not
be
obvious
for
someone
else
reading
this
application.
You
know
so
thanks
for
asking
the
question,
because
it
allowed
us
to
improve
the.
G
G
So
probably
not
everybody
on
this
call
knows
about
it,
but
it's
strictly
because
we're
working
with
a
lot
of
different
things
right.
So
it's
similar
with
other
projects
that
have
been
joining
before
it's
like
not
everyone
at
dsc
will
necessarily
be
able
to
be
aware
of
all
the
projects
right
because,
uh
let's
say
there's
some
chisel-related
stuff,
if,
if
you're
not
using
it
like
for
you,
it's
always
going
to
be
a
new
thing.
Yeah.
G
Yeah
in
that
sense,
I
think
it's
based
on
trust,
in
the
sense
that,
of
course,
if
someone
sees
legitimate
reasons
why
you
know
we
need
more
time
to
decide
it's.
You
know
it's
good
to
raise
it.
I
think
that
the
whole
point
of
sandbox
applications
is
that
uh
we're
gonna
pass
it
through
sandbox
and
then
and
and
that's
only
an
expression
of
intent
right
and
then.
A
G
G
B
G
So
it's
kind
of
a
non-harmful
vote,
let's
say
and
of
course
then
we'll
put
forward
a
vote
via
uh
email
right
and
then,
of
course,
uh
everyone.
Even
people
that
are
not
on
this
call
today
will
be
able
to
participate
in
that
vote,
and
then
I
mean
we
could
go
straight
for
you
know
for
for
the
main
application
right.
There
is
no
reason
why
we
couldn't
do
this,
but
I
didn't
want
to
have
the
discussion
first
of
all,
because
we're
going
to
make
tom
the
leader
so
that
we
don't
have
too
many
people.
G
You
know
sitting
in
the
tsc.
uh
Secondly,
are
just
a
heads
up:
uh
it's
isc
license.
That's
one
thing:
uh
it's
I
see
license
like
many
of
our
projects,
but
we
have
come
up
with
a
way
to
uh
incorporate
non-apache
license
projects
and
that
basically
boils
down
to
a
procedure,
a
due
diligence
procedure
where
we
get
everyone
to
sign
the
chip's
line,
cla
right
also
for
muhammad's
information.
So
you
have
a
project.
If
you
have
a
project,
that's
open
source,
but
not
following
apache.
G
What
you
need
to
do
to
be
able
to
include
this
project
is
to
get
everyone
to
that.
Has
over
one
percent
of
contributions
to
sign
the
cra
so
for
any
project
that
we
kind
of
propose
this
way,
we
will
have
already
done
this
because
you
know
there's
no
point
in
trying
to
apply
a
project
and
then
finding
out
that
someone
doesn't
sign
a
cla
so
for
this
particular
project
we
have
already
performed
this
and
there's,
I
think,
there's
only
three
authors
or
something.
G
So
it
was
very
simple,
but
um
just
just
a
heads
up
and
and
the
sandbox
is
where
this
is
not
yet
required
right.
But
the
next
vote
is
where
uh
this
is
actually
a
like
a
legal
requirement
for
the
due
diligence
to
be
positive,
like
for
us
to
be
able
to
say
nobody
that
owns
more
than
one
percent
of
the
code
hasn't
signed,
the
cla
everyone
that
that
kind
of
has
any
claim
to
say
I
did.
This
has
signed
the
chipsea,
so
they
can't
go
after
us
and
say:
oh
I
changed
my
mind.
G
C
I
just
guess:
yeah
yeah.
No,
I'm
just
going
to
add
that
the
corporate
legal
team
that
helps
chips
alliance
has
come
up
or
formulated
a
set
of
pre-approved
licenses
about
10
licenses
that
are
just
effective.
You
know
carte
blanche,
effective
for
acceptance
of
projects
into
chips.
Now
there
are
many
open
source
licenses,
as
we
all
know,
and
they
will
certainly
entertain
other
licenses
too,
but
it's
just
that
they're
providing
a
list
of
what
is
acceptable
up
front.
G
It's
valid
that
we
should
perhaps
you
know,
kind
of
uh
think
about
putting
that
information
down
somewhere
in
this
repository
right.
It
could
be
a
good
idea
to.
uh
I
don't
remember
the
whole
structure
of
this,
but,
generally
speaking,
you
know
we
have
the
clas,
that's
where
the
projects
live.
That's
where
you
make
the
pull
requests
right.
G
G
G
G
G
G
C
B
G
G
B
G
A
G
G
K
K
C
G
C
G
A
G
G
G
Just
just
a
heads
up,
that's
it's!
Basically
anyone
can
join
the
gc
meetings
like
it
is.
An
open
meeting
uh
is
being
recorded
and
so
on,
but
to
vote
you
have
to
kind
of
lead
the
project.
I
was
somehow
convinced
that
you
were-
and
you
probably
will
be
at
some
point
uh
when
something
gets
contributed
uh
from
from
the
area
that
kind
of
you're
managing.
But
at
this
point
we
only
have
eight
voting
members.
C
G
G
Later,
uh
okay,
um
so
that
was
the
the
vote
that
we
wanted
to
take
today,
and
the
broader
context
is
the
dfpg
tools
uh
that
we
want
to
uh
donate
into
chips
alliance.
um
Perhaps
one
kind
of
uh
aspect
of
this
is
also
the
naming
pattern.
uh
Essentially
we're
checking
this
with
this
foundation.
Legal,
I
don't
know,
rob
if
you've
had
no
identification
if
the
name
works.
C
G
So
one
of
the
most
prominent
parts
of
the
entire
tool
chain
are
kind
of
already
in
chips
and,
of
course,
quick
logic
is
a
user
micro
is
developing
and
google
who's
kind
of
also
developing
the
tools
and
using
the
tools
as
well
uh
are
members
right,
and
the
plan
is
to
based
on
the
interchange,
work
that
we're
doing
the
plan
is
to
also
get
stylings
and
lattice
and
others
potentially
to
to
join
us.
That's
the
rough
sketch
of
a
plan
for
for
our
fpga
working
group
that
we're
setting
up.
J
J
Yes,
so
we
are
going
to
publish
these
two
um
to
repositories
into
so
some
type
under
the
chip
science
project,
and
this
will
be
the
infrastructure
of
our
associate
design
and
we
are
trying
to
rewrite
a
new
risk
for
52
imac,
b
b
um
core
and
a
tanning
based
soc,
but
we
might
rewrite
style
timing.
So
um
these
two
repositories
will
be
our
our
infrastructure
and
we
are
going
to
have
a
lot
of
tests
on
them,
but
currently
it
might
be
a
little
stored
by
the
sun
type
publishing
flow.
G
C
C
F
So
I
I
brought
this
up
several
months
ago,
because
the
chisel
working
group
also
wants
this.
Basically
any
group
that
is
trying
to
publish
java
based
like
jvm
based
artifacts
is
going
to
want
to
use
maven
to
do
so,
which
means
interacting
with
sonotype,
and
if
we
want
these
artifacts
to
be
published
under
the
sort
of
umbrella
of
the
entity
of
chip's
alliance,
then
there's
some
amount
of
central
organization
is
needed
in
that,
like
a
chips,
alliance,
email
has
to
be
used
to
register
the
organization
with
sona
type.
F
I
I've
paged
out
what
whatever
the
other
requirements
were,
but
basically
it
wasn't
something
I
had
well.
I
technically
approve
of
the
direction
and
think
it's
going
to
be
a
popular
choice
for
jvm-based
projects,
which
includes
scala,
for
example,
which
the
the
tools
zhao
young
is
talking
about.
Use.
F
F
uh
They
also
were
requesting
this
because
they
would
rather
start
they've
been
publishing
past
releases,
I
think
uh
from
chisel.org
or
something,
but
they
would
rather
use.
You
know-
or
I
should
say
org.chisel
because
it's
like
jvm
strings,
but
they
would
rather
use
like
org,
dot
chips,
alliance.chisel
or
something
like
that.
C
J
J
Oh
yeah
they're
using
berkeley.
Yes,
and
these
two,
the
repository
is
still
experimental
and
I
just
pulled
them
up
out
of
a
rocket
chip
and
we
are
going
to
have
an
intensive
test
on
them.
So
before
this
test
and
before
uh
203.5
release,
this
won't
block
us
at
all.
But
hopefully
I
think
if
we
can
make
these
two
repository
repository,
publish
it
at
23.5.
J
G
G
uh
I
could
raise
one
potential
topic
that
I
think
is
kind
of
useful
to
to
discuss
is
uh
we're
discussing,
of
course,
plans
for
2022,
and
one
of
the
things
that
we
have
been
debating
is
how
to
handle
events.
uh
One
of
the
ideas
that
has
been
circulated
is
to
create
you
know.
I
mean
we
still
want
some
independent
events
that
we'll
we're
gonna
run,
but
uh
we'd
also
like
to
try
kind
of
uh
sticking.
You
know
our
events
to
other
popular
events
that
might
be
happening.
G
Generally
speaking,
of
course,
it
depends
on
what's
possible
how
much
things
cost
and
so
on.
We
don't
want
to
necessarily
generate
a
lot
of
costs,
but
it's
more
more
a
way
of
leveraging
the
existing
marketing
and
community
and
attendance
of
shows
that
already
have
uh
you
know
people
attending
them
anyway,
and
they
might
be
interested
in
some
of
the
topics
that
we're
working
on
and
that's,
of
course,.
G
G
C
I
don't
think
it
hurts
to
mention
it
just
for
awareness,
so
I
mean
we
do
uh
talk
about,
for
example,
working
with
open
power,
possibly
on
a
joint
event.
So
I'm
going
to
chat
with
james
talina
about
that.
I
think
also
given
the
size
of
chips
right
now.
We
don't
have
enough
budget
to
uh
host
or
foster
an
entire
event
on
our
own,
but
we
can
certainly
partner
with
others
uh
to
help
raise
awareness
and
help
build
the
community
so
mike-
and
I
have
had
some
conversations
about
that.
C
Yes,
I
did
yes,
I
did
uh
boris
uh
the
camera,
the
other
two
folks
names.
uh
We
we
chatted
last
wednesday
uh
about
this
idea
and
I
think,
there's
good
alignment
in
terms
of
uh
you
know,
philosophy
and
what
you
know.
Both
organizations
are
trying
to
do
so.
Issc
this
year
budgeted
a
hundred
thousand
dollars
for
uh
mpw's
amongst
the
different
submissions
that
they
had
and
uh
yeah.
I
can
send
you
the
summary
note
that
I
wrote
on
this,
but
uh
you
know,
but
uh
you
know
basically
I
think,
there's
good
alignment
and
definitely.
D
D
D
C
D
I
think
so
yeah.
I
think
it's
it's
worth
exploring
that
um
because
uh
we
try
and
you
know,
you're
aware
of
the
workshop.
So
um
so
that's
um
you
know
we're
planning
to
do
that,
but
like
trying
to
make
this
happen
would
be
great
as
well
and
chips
alliance
would
be,
uh
you
know,
pushing
for
the
open
source,
ic
design,
and
that
would
be
really
helpful
to
get
some
visibility
in
the
circuit
community
circuits
community.
C
Right,
I
agree
right
right
because
I
know
you
know
we,
as
you
well
know
too
right.
We
just
chatted
about
the
overall
challenge
of
getting
people
interested
in
in
the
circuit
world
right
or
the
design
world,
and
uh
you
know
trying
to
get
uh
you
know
new
students
or
folks
uh
younger.
You
know
folks
involved
and
interested
in
it.
So
I
think
the
open
source
mechanism
is
a
great
way
to
accomplish
that.
B
C
B
And
there's
also
on
the
side,
also
stanford.
Also,
they
have
lines
that
they
submitted
as
well.
That
are
open
sourced,
so
they're,
multiple
and
a
lot
of
them
are
a
good
portion
of
them
is
animal,
so
we
it
it's
a
part
of
that
and
I
agree
uh
like,
for
example,
uh
one
of
the
things
that
so
this
is
the
magazine.
B
The
circuit
sensor,
I'm
sorry
set
circuits
magazine,
so
this
one
had
an
article
presenting
four
of
these
10
and
these
projects,
so
the
opportunity
to
have
some
something
marketed
with
the
chips
alliance,
obviously
uh
is
important.
We
need
to
have
a
process
for
one-off
projects,
okay,
because
you
may
end
up
with
a
like
a
small
ip.
How
do
you
handle
that
you
know?
B
And
so
we
need
to
talk
about
that,
for
you
know
some
time
later
or
whatever,
but
um
because
not
all
of
them
necessarily
going
to
be
the
uh
something
major
that
has
a
team
to
do
and
then
contributing
the
project
is
at
the
university
or
is
it
the
solstice
circuits
because
they
paid
whatever
so
there
are?
There
are
things
to
be
addressed
here,
but
I
think
boris
would
be
open
to
it.
B
C
B
C
B
B
C
B
B
That
said,
by
the
way
I've
been
talking
to
different
people
about
the
options.
So
there
are,
there
are
companies.
There
are
new
startups,
for
example,
that
are
trying
to
build
open
source
surveys,
or
things
like
that.
So
I've
been
having
like
conversations
in
the
background
related
to
that
anyway.
I.
I
D
G
I
think
one
of
the
things
to
do
is
definitely
just
you
know,
going
through
the
pull
requests
and
issues
in
the
tfc
repo
and
just
uh
adding
things
to
the
google
doc,
where
we
keep
the
notes
in
kind
of
pasting,
a
table
with
the
attendance
and
like
little
things
that
just
kind
of
make
things
run
smoothly.
We
definitely
need
to
improve
on
that.
uh
I
kind
of
put
into
agenda
items,
but
of
course
I
only
did
this.
G
You
know
like
half
a
day
before
the
meeting,
so
uh
of
course
we
should
kind
of
plan
to
do
it
a
bit
earlier.
I
think
it
was
one
of
the
challenges
was
that
we
were
voting
on
the
time
for
this
meeting
until
was
the
very
last
moment,
so
nobody
knew
that
it
was
happening
with
a
huge
advance
notice,
but
I
I
assume
we
should
plan
the
next
one
with
enough
advanced
notice
that
everyone
knows
when
it's
happening
and
kind
of
everyone
can
put
forward
whatever
they
want
to
talk
about.
D
Yeah,
that
sounds
good,
michael.
I
I,
I
think.
One
thing
you
know
going
through
the
the
issues
is
nice,
but
then
we
need
to
you
know.
If
we
have
an
elaborated
plan,
we
probably
want
to
progress
that,
like
we
have,
we
need
to
set
up
basically
the
goals
and
how
to
achieve
those
goals,
and
uh
I
feel
like
we,
you
know
we're
trying
to
collaborate,
and
this
is
the
goal
of
chip's
alliance.
That's
my
understanding,
but
it
doesn't
feel
like
you
know.
We
are.
We
are
there
yet.
G
Yes,
of
course,
in
a
broader
sense,
it
makes
absolute
sense
to
try
to
push
a
broader
plan.
It's
uh
I
think
it
is
something
that
kind
of
uh
we've
been
having
discussion
in
the
board
as
well
right
where
we're
debating
what's
the
best
way
to
spend
our
energy
and
uh
we're
in
general
agreement,
but
like
the
devil's
in
the
details
and.
A
G
Vision
needs
to
then
be
communicated
to
the
tsc
and
kind
of
we
should
be
involved
in
making
it
happen
uh
on
the
technical
level,
and
I'm
not
saying
we
have
no
influence
on
the
vision
right.
I
think
we
should
as
a
steering
committee
um
but
yeah.
Certainly
that's
something
that
we'd
be
very
happy
to
kind
of.
G
D
G
D
G
D
G
I
feel
like
it's
hard
to
work
with
an
empty
piece
of
paper.
Other
than
saying
we
want
to
write
about
the
technical
updates,
which
of
course
is
a
very
generic
thing
to
say,
but
if
you
say
in
open,
foster
we'd
manage
to
do
this
this
and
this
and
someone
else
says
in
the
analog
work
group.
We
did
this
and
this
then
you
know
in
total,
you
look
at
the
bullets
and
you
say:
oh,
the
overarching
theme
seems
to
be
this.
Let's
kind
of
write
the
note
in
the
uh
in
this
direction
right.