Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
O
OHR Meta Project
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
OHR Meta Project
Commits
700dafbf
Commit
700dafbf
authored
Feb 02, 2021
by
Javier Serrano
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
First version of slides for OpenUK talk
parent
bd5af2f1
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
490 additions
and
0 deletions
+490
-0
synchrotron.jpg
figures/misc/synchrotron.jpg
+0
-0
Makefile
presentations/openuk_2021/Makefile
+10
-0
js_openuk_2021.tex
presentations/openuk_2021/js_openuk_2021.tex
+480
-0
No files found.
figures/misc/synchrotron.jpg
0 → 100644
View file @
700dafbf
197 KB
presentations/openuk_2021/Makefile
0 → 100644
View file @
700dafbf
all
:
js_openuk_2021.pdf
.PHONY
:
all clean
js_openuk_2021.pdf
:
js_openuk_2021.tex
pdflatex
$^
;
\
pdflatex
$^
clean
:
rm
-f
*
.vrb
*
.eps
*
.pdf
*
.dat
*
.log
*
.out
*
.aux
*
.dvi
*
.ps
*
.toc
*
.snm
*
.nav
*
~
presentations/openuk_2021/js_openuk_2021.tex
0 → 100644
View file @
700dafbf
\documentclass
[compress,red]
{
beamer
}
%\documentclass[compress,red, handout]{beamer}
\mode
<presentation>
\setbeamertemplate
{
navigation symbols
}{}
\usetheme
{
Warsaw
}
%\hypersetup{pdfpagemode=FullScreen} % makes your presentation go automatically to full screen
% define your own colors:
\definecolor
{
Red
}{
rgb
}{
1,0,0
}
\definecolor
{
Blue
}{
rgb
}{
0,0,1
}
\definecolor
{
Green
}{
rgb
}{
0,1,0
}
\definecolor
{
magenta
}{
rgb
}{
1,0,.6
}
\definecolor
{
lightblue
}{
rgb
}{
0,.5,1
}
\definecolor
{
lightpurple
}{
rgb
}{
.6,.4,1
}
\definecolor
{
gold
}{
rgb
}{
.6,.5,0
}
\definecolor
{
orange
}{
rgb
}{
1,0.4,0
}
\definecolor
{
hotpink
}{
rgb
}{
1,0,0.5
}
\definecolor
{
newcolor2
}{
rgb
}{
.5,.3,.5
}
\definecolor
{
newcolor
}{
rgb
}{
0,.3,1
}
\definecolor
{
newcolor3
}{
rgb
}{
1,0,.35
}
\definecolor
{
darkgreen1
}{
rgb
}{
0, .35, 0
}
\definecolor
{
darkgreen
}{
rgb
}{
0, .6, 0
}
\definecolor
{
darkred
}{
rgb
}{
.75,0,0
}
\xdefinecolor
{
olive
}{
cmyk
}{
0.64,0,0.95,0.4
}
\xdefinecolor
{
purpleish
}{
cmyk
}{
0.75,0.75,0,0
}
\useoutertheme
[subsection=false]
{
smoothbars
}
% include packages
\usepackage
{
subfigure
}
\usepackage
{
multicol
}
\usepackage
{
amsmath
}
% \usepackage{epsfig} % Erik: didn't work with Miktex
\usepackage
{
graphicx
}
\usepackage
[all,knot]
{
xy
}
\xyoption
{
arc
}
\usepackage
{
url
}
\usepackage
{
multimedia
}
\usepackage
{
hyperref
}
\usepackage
{
helvet
}
\usepackage
[english]
{
babel
}
\usepackage
[utf8]
{
inputenc
}
\usepackage
{
multirow
}
%%%%%%%%%%%%5
%\usepackage{geometry}
%\geometry{verbose,letterpaper}
%\usepackage{movie15}
%\usepackage{hyperref}
\graphicspath
{
{
../../figures/
}
}
\title
[Open Hardware at CERN\hspace{9em}\insertframenumber/\inserttotalframenumber]
{
Open Hardware at CERN
}
%\subtitle{An Introduction}
\author
{
Javier Serrano
}
% - Give the names in the same order as the appear in the paper.
% - Use the \inst{?} command only if the authors have different
% affiliation.
\institute
%[Universities of Somewhere and Elsewhere] % (optional, but mostly needed)
{
%\inst{1}%
% BE-CO Hardware and Timing section\\
CERN, Geneva, Switzerland
%\and
%\inst{2}%
%Department of Theoretical Philosophy\\
%University of Elsewhere
}
% - Use the \inst command only if there are several affiliations.
% - Keep it simple, no one is interested in your street address.
\date
[Future Leaders' training]
%(optional, should be abbreviation of conference name)
{
OpenUK's Future Leaders' training
\\
5 February 2021
}
% - Either use conference name or its abbreviation.
% - Not really informative to the audience, more for people (including
% yourself) who are reading the slides online
%\subject{Theoretical Computer Science}
% This is only inserted into the PDF information catalog. Can be left
% out.
% If you have a file called "university-logo-filename.xxx", where xxx
% is a graphic format that can be processed by latex or pdflatex,
% resp., then you can add a logo as follows:
%\pgfdeclareimage[height=1cm]{ohr-logo}{ohr_logo.jpg}
%\logo{\pgfuseimage{ohr-logo}}
% Delete this, if you do not want the table of contents to pop up at
% the beginning of each subsection:
\AtBeginSection
[]
{
\begin{frame}
<beamer>
{
Outline
}
\tableofcontents
[currentsection]
\end{frame}
}
% If you wish to uncover everything in a step-wise fashion, uncomment
% the following command:
%\beamerdefaultoverlayspecification{<+->}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\begin{frame}
{
Outline
}
\tableofcontents
% You might wish to add the option [pausesections]
\end{frame}
\section
[Intro to CERN]
{
Introduction to CERN
}
\subsection
{}
\begin{frame}
{
Accelerators
}
\begin{center}
\includegraphics
[height=0.85\textheight]
{
misc/accelerator
_
map.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
Detectors
}
\begin{center}
\includegraphics
[height=0.85\textheight]
{
misc/atlas.jpeg
}
\end{center}
\end{frame}
\begin{frame}
{
Dissemination
}
\begin{center}
\includegraphics
[height=0.8\textheight]
{
misc/cern
_
council.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
How to interpret one's dissemination mandate in the 21
\textsuperscript
{
st
}
century
}
\begin{center}
\includegraphics
[height=0.8\textheight]
{
misc/cern
_
and
_
openness.jpg
}
\end{center}
\end{frame}
\section
{
Open Hardware
}
\subsection
{}
\begin{frame}
{
Democratisation
}
\begin{center}
\includegraphics
[height=0.85\textheight]
{
misc/ben
_
with
_
talon
_
beast.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
OSHW definition
}
\begin{block}
{
Check out
\href
{
http://www.oshwa.org/definition/
}{
http://www.oshwa.org/definition/
}}
\begin{itemize}
\item
Inspired by the Open Source definition for software
\item
Focuses on ensuring freedom to study, modify, distribute, make
and sell designs or hardware based on those designs
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Challenges in Open Hardware
}
\begin{itemize}
\item
Curated repositories of
\textbf
{
high-quality designs
}
with version control and
forums
\item
Discussions with commercial companies on
\textbf
{
business models
}
\item
\textbf
{
Free and Open Source Software tools
}
to design hardware and easily share
those designs
\item
A sound legal basis for sharing in the form of a good set of
\textbf
{
Open
Hardware Licences
}
\end{itemize}
\end{frame}
\section
[White Rabbit]
{
White Rabbit
}
\subsection
{}
\begin{frame}
{
The need for synchronisation in a particle accelerator
}
\begin{center}
\includegraphics
[height=6.5cm]
{
misc/synchrotron.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
White Rabbit: an
\emph
{
extension
}
of Ethernet
}
\begin{columns}
[c]
\column
{
.5
\textwidth
}
\begin{itemize}
\item
Standard Ethernet network
\item
Ethernet features (VLAN)
\&
protocols (SNMP)
\end{itemize}
\begin{itemize}
\item
\color
{
Blue
}{
Sub-ns synchronisation
}
\item
\color
{
Red
}{
Guaranteed (by design) upper bound in frame latency
}
\end{itemize}
\column
{
.6
\textwidth
}
\begin{center}
\includegraphics
[height=1.05\textwidth]
{
network/wr
_
network-enhanced
_
pro.jpg
}
\end{center}
\end{columns}
\end{frame}
\begin{frame}
{
The need for synchronisation in a particle accelerator
}
\begin{center}
\includegraphics
[height=6.5cm]
{
protocol/ptp
_
exchange.pdf
}
\end{center}
\end{frame}
\begin{frame}
[t,fragile]
{
White Rabbit Switch
}
\begin{center}
\includegraphics
[width=\textwidth]
{
switch/wrSwitch
_
v3
_
3.jpg
}
\begin{itemize}
\item
Central element of WR network
\item
18 port gigabit Ethernet switch with WR features
\item
Fully open design, commercially available
\end{itemize}
\end{center}
\end{frame}
\begin{frame}
{
WR Node: SPEC board
}
\begin{center}
\includegraphics
[width=7cm]
{
node/spec.jpg
}
\end{center}
\begin{columns}
[c]
\column
{
.01
\textwidth
}
\column
{
.98
\textwidth
}
\begin{block}
{
Carrier/mezzanine Hardware Kit
}
\begin{itemize}
% \item Carrier boards in PCI-Express, VME, PXIe
\item
All carrier cards are equipped with a White Rabbit port
\item
Mezzanines provide different functions (e.g. ADC)
\end{itemize}
\end{block}
\column
{
.01
\textwidth
}
\end{columns}
\end{frame}
\begin{frame}
{
White Rabbit application examples
}
\begin{columns}
[c]
\column
{
0.7
\textwidth
}
\begin{itemize}
\item
<1->
\color
<2->
{
black!50
}{
CERN and GSI
}
\item
<2->
\color
<3->
{
black!50
}{
The Large High Altitude Air Shower Observatory
}
\item
<3->
\color
<4->
{
black!50
}{
KM3NET: European deep-sea neutrino telescope
}
\item
<4->
{
MIKES: Centre for metrology and accreditation
}
\end{itemize}
\column
{
0.45
\textwidth
}
\begin{center}
\includegraphics
<1>[width=0.80
\textwidth
]
{
applications/gsiANDcern.pdf
}
\pause
\includegraphics
<2>[width=1
\textwidth
]
{
applications/lhaaso.pdf
}
\pause
\includegraphics
<3>[width=1
\textwidth
]
{
applications/KM3NeT.pdf
}
\pause
\includegraphics
<4->[width=.5
\textwidth
]
{
applications/mikes.pdf
}
\end{center}
\end{columns}
\pause
{
\small
More WR collaborators/users:
\url
{
http://www.ohwr.org/projects/white-rabbit/wiki/WRUsers
}}
\end{frame}
\begin{frame}
{
Open source and the unexpected
}
\begin{center}
\includegraphics
[width=\textwidth]
{
../../figures/applications/wr
_
other
_
apps.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
Open source and standardisation
}
\begin{block}
{
Benefits
}
\begin{itemize}
\item
Inertia!
\item
Impact
\end{itemize}
\end{block}
\pause
\begin{block}
{
Issues
}
\begin{itemize}
\item
It takes a lot of effort
\item
There is a fundamental tension between standard-essential patents and
reciprocal open source licences
\end{itemize}
\end{block}
\pause
\end{frame}
\section
{
Open Hardware Licensing
}
\subsection
{}
\begin{frame}
{
Software licensing: our starting point
}
\begin{block}
{
Mostly copyright licences
}
\begin{itemize}
\item
Very uniform legal landscape worldwide
\item
Modern licences also deal with patents
\end{itemize}
\end{block}
\pause
\begin{block}
{
Three licensing regimes
}
\begin{itemize}
\item
Permissive (BSD, MIT, Apache v2)
\item
Weakly reciprocal (MPL v2, LGPL v3)
\item
Strongly reciprocal (GPL v3, AGPL v3)
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Challenges in hardware licensing
}
\begin{block}
{
Rights for hardware
}
Copyright does not generally apply to physical objects
\end{block}
\pause
\begin{block}
{
Patents
}
Much more prevalent in hardware than in software
\end{block}
\pause
\begin{block}
{
Reciprocity
}
What should a reciprocal licence do for a hardware design? What is the scope
of reciprocity?
\end{block}
\pause
\begin{block}
{
The hardware design ecosystem
}
Dominated by proprietary tools, parts of which sometimes go into the design itself
\end{block}
\end{frame}
\begin{frame}
{
The CERN Open Hardware Licence v2
}
\begin{itemize}
\item
Based on rights mainly applying to the design sources (e.g. circuit
schematics or CAD drawings)
\pause
\item
Specifies conditions for:
\begin{itemize}
\item
Copying designs
\item
Modifying designs
\item
Distributing modified or unmodified designs
\item
Making hardware out of those designs
\item
Distributing that hardware
\end{itemize}
\pause
\item
Drafted by Myriam Ayass, Andrew Katz and Javier Serrano
\pause
\item
Comes in three variants:
\begin{itemize}
\item
CERN-OHL-P-2.0 (permissive)
\item
CERN-OHL-W-2.0 (weakly reciprocal)
\item
CERN-OHL-S-2.0 (strongly reciprocal)
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}
{
Challenges in hardware licensing
}{
How CERN OHL v2 deals with them
}
\begin{block}
{
Rights for hardware
}
CERN OHL v2 makes no assumption about rights
\end{block}
\pause
\begin{block}
{
Patents
}
Two-way patent licensing clauses
\end{block}
\pause
\begin{block}
{
Reciprocity
}
Have URL travel with object and use concepts of Product and Available
Component to establish limits of reciprocal obligations
\end{block}
\pause
\begin{block}
{
The hardware design ecosystem
}
Components which are shipped with design tools qualify as Available Components
\end{block}
\end{frame}
\begin{frame}
{
CERN OHL v2 for PCB designs
}
\begin{center}
\includegraphics
[width=\textwidth]
{
misc/cern
_
ohl
_
variants
_
pcb.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
CERN OHL v2 for HDL/FPGA/ASIC designs
}
\begin{center}
\includegraphics
[width=\textwidth]
{
misc/cern
_
ohl
_
variants
_
hdl.jpg
}
\end{center}
\end{frame}
\section
{
Public institutions
}
\subsection
{}
\begin{frame}
{
Public institutions
}
\begin{block}
{
They serve the interests of a whole society
}
\begin{itemize}
\item
Try to maximise positive impact of decisions.
\item
Not always easy.
\end{itemize}
\end{block}
\pause
\begin{block}
{
Can be ``tractor'' institutions
}
\begin{itemize}
\item
To help take projects to a mature state where they can
be sustained commercially.
\item
Liaising with other public institutions to reach
critical mass.
\item
Also with their procurement hat.
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Issues with ``coopetition''
}
Research groups sometimes (often?) end up behaving as private
companies (but with public money!) because of wrong incentives by
funding agencies.
\end{frame}
\begin{frame}
{
The funding agencies conundrum
}
\begin{center}
\includegraphics
[height=0.8\textheight]
{
misc/flags.jpg
}
\end{center}
\end{frame}
\begin{frame}
{
Things I believe we did right in the White Rabbit
project
}
\begin{block}
{
For the WR community
}
\begin{itemize}
\item
Open source
\item
Lively welcoming environment via mailing list and periodic workshops
\end{itemize}
\end{block}
\pause
\begin{block}
{
For companies
}
\begin{itemize}
\item
Growing open source core
\item
Space in the periphery for proprietary innovation
\end{itemize}
\end{block}
\end{frame}
\begin{frame}
{
Things I believe we did right in the White Rabbit
project
}
\begin{block}
{
For tax payers
}
\begin{itemize}
\item
Enlarge the scope of our original project
\item
Use standard technologies and standardise our enhancements
under IEEE 1588
\item
Open source
\end{itemize}
\end{block}
And, in general, ensuring a coordinating and facilitating role to
make sure the whole project runs smoothly.
\end{frame}
\end{document}
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment