diff --git a/presentations/llrf_2022/Makefile b/presentations/llrf_2022/Makefile
new file mode 100644
index 0000000000000000000000000000000000000000..9a60a29b5a4f5b8823f7d7b8aa461f81051f7e66
--- /dev/null
+++ b/presentations/llrf_2022/Makefile
@@ -0,0 +1,10 @@
+all : js_llrf_2022.pdf
+
+.PHONY : all clean
+
+js_llrf_2022.pdf : js_llrf_2022.tex
+	pdflatex $^; \
+	pdflatex $^
+
+clean :
+	rm -f *.vrb *.eps *.pdf *.dat *.log *.out *.aux *.dvi *.ps *.toc *.snm *.nav *~
diff --git a/presentations/llrf_2022/js_llrf_2022.tex b/presentations/llrf_2022/js_llrf_2022.tex
new file mode 100644
index 0000000000000000000000000000000000000000..0c73c8fd4762f4a0a494d543f5af4c63a20c5105
--- /dev/null
+++ b/presentations/llrf_2022/js_llrf_2022.tex
@@ -0,0 +1,348 @@
+\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}
+
+\newcommand{\backupbegin}{
+   \newcounter{framenumberappendix}
+   \setcounter{framenumberappendix}{\value{framenumber}}
+}
+\newcommand{\backupend}{
+   \addtocounter{framenumberappendix}{-\value{framenumber}}
+   \addtocounter{framenumber}{\value{framenumberappendix}} 
+}
+
+
+\graphicspath{ {../../figures/} }
+
+\title[Open Hardware at CERN\hspace{11em}\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[LLRF Workshop 2022] %(optional, should be abbreviation of conference name)
+{Low Level RF Workshop\\
+12 October 2022
+}
+% - 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}{Quick disclaimer}
+  CERN is big. Most of what I will say is based on my particular experience
+  working with people, mostly in the Accelerators and Technology Sector, and
+  open-sourcing software, firmware, gateware and hardware over the last 15
+  years.
+\end{frame}
+
+\begin{frame}{Outline}
+  \tableofcontents
+  % You might wish to add the option [pausesections]
+
+\end{frame}
+
+
+
+\section{CERN and Open Source}
+\subsection{}
+
+\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.75\textheight]{misc/cern_and_openness.jpg}
+  \end{center}
+\tiny{This and other figures courtesy of Tomasz W\l{}ostowski}
+\end{frame}
+
+\section{Open Hardware (and Gateware)}
+\subsection{}
+
+\begin{frame}{Challenges we saw in Open Hardware in the beginning of our
+    journey}
+  \begin{block}{Curated repositories of \textbf{high-quality designs} with version control and
+      forums}
+    We created ohwr.org. Nowadays, lots of great options.
+  \end{block}
+\pause
+  \begin{block}{Discussions with commercial companies on \textbf{business
+        models}}
+    Mostly based on hybrid (open/proprietary) catalogues. Golden rule: in
+    public/private partnerships no actor should be asked to do something
+    ``unnatural'' to them. Corollary: we don't tell companies how they should be
+    doing business.
+  \end{block}
+\end{frame}
+
+
+\begin{frame}{Challenges we saw in Open Hardware in the beginning of our
+    journey}
+  \begin{block}{\textbf{Free and Open Source Software tools} to design hardware and easily share those designs}
+    We contributed greatly to KiCad development. We were less successful with
+    HDL simulators.
+  \end{block}
+  \pause
+  \begin{block}{A sound legal basis for sharing in the form of a good set of \textbf{Open Hardware Licences}}
+    CERN OHL v2 (\href{https://cern.ch/cernohl}{https://cern.ch/cernohl}) comes
+    in three variants: permissive, weakly-reciprocal and strongly-reciprocal. It
+    works for PCBs and HDL.
+  \end{block}
+\end{frame}
+
+\begin{frame}{CERN OHL v2 for HDL designs}
+ \begin{center}
+   \includegraphics[width=\textwidth]{misc/cern_ohl_variants_hdl.jpg}
+ \end{center} 
+\end{frame}
+
+\section[Open Source and KT]{Open Source and Knowledge Transfer}
+\subsection{}
+
+\begin{frame}{Open Source and Knowledge Transfer}
+  \begin{block}{KT's mission at CERN is to maximise impact}
+    \begin{itemize}
+     \item Open source may not be optimal in some cases (e.g. when private
+       investor is needed and they insist in keeping technology proprietary)
+     \item Most apparent in hardware projects, less so in software and gateware
+    \end{itemize}
+  \end{block}
+  \pause
+  \begin{block}{Revenue generation also part of the picture}
+    \begin{itemize}
+     \item One mode of operation consists in reinvesting benefits to pursue
+       further KT work
+     \item Traditionally, monetising open source has been seen as harder
+    \end{itemize}
+  \end{block}
+\end{frame}
+
+\begin{frame}{Two ways forward}
+  \begin{block}{Operate outside the money circuit}
+    \begin{itemize}
+     \item We got full support for this at CERN!
+     \item May result in a disconnect from KT for some projects/groups though
+    \end{itemize}
+  \end{block}
+  \pause
+  \begin{block}{Explore ways of bringing funds to a project}
+    \begin{itemize}
+     \item Foundations, consortia, collaborations\ldots
+     \item Could help with other issues, e.g. sustainability
+     \item We are exploring this in White Rabbit now. See \href{https://white-rabbit.tech}{https://white-rabbit.tech}
+    \end{itemize}
+  \end{block}
+\end{frame}
+
+
+\appendix
+\backupbegin
+
+\begin{frame}
+  Backup Slides
+\end{frame}
+
+
+\begin{frame}{The importance of FOSS tools for hardware design}
+  \begin{center}
+    \includegraphics[width=\textwidth]{misc/sam_smith_kicad_v3.png}
+  \end{center}
+\end{frame}
+
+\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}
+	\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}
+
+  \begin{block}{Patents}
+   Much more prevalent in hardware than in software
+  \end{block}
+
+  \begin{block}{Reciprocity}
+   What should a reciprocal licence do for a hardware design? What is the scope
+   of reciprocity?
+  \end{block}
+
+  \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)
+
+   \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}
+
+   \item Drafted by Myriam Ayass, Andrew Katz and Javier Serrano
+
+   \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}
+
+  \begin{block}{Patents}
+   Two-way patent licensing clauses
+  \end{block}
+
+  \begin{block}{Reciprocity}
+   Have URL travel with object and use concepts of Product and Available
+   Component to establish limits of reciprocal obligations
+  \end{block}
+
+  \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}
+
+
+\backupend
+
+\end{document}