[FE training-materials-updates] Replace LXR by Elixir
Michael Opdenacker
michael.opdenacker at free-electrons.com
Mon May 15 17:18:59 CEST 2017
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=01d3b31f5d6faf9eb791f10f9c03cb507f888255
>---------------------------------------------------------------
commit 01d3b31f5d6faf9eb791f10f9c03cb507f888255
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Mon May 15 17:18:59 2017 +0200
Replace LXR by Elixir
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
01d3b31f5d6faf9eb791f10f9c03cb507f888255
agenda/kernel-agenda.tex | 3 +--
agenda/kernel-fr-agenda.tex | 3 +--
labs/boottime-kernel/boottime-kernel.tex | 2 +-
labs/kernel-debugging/kernel-debugging.tex | 2 +-
.../kernel-i2c-communication.tex | 6 +++---
.../kernel-sources-exploring.tex | 4 ++--
slides/about-us/about-us.tex | 4 ++--
slides/boottime-kernel/boottime-kernel.tex | 4 ++--
slides/kernel-source-code-management/elixir.png | Bin 0 -> 100692 bytes
.../kernel-source-code-management.tex | 18 +++++++++---------
slides/kernel-source-code-management/lxr.png | Bin 125181 -> 0 bytes
11 files changed, 22 insertions(+), 24 deletions(-)
diff --git a/agenda/kernel-agenda.tex b/agenda/kernel-agenda.tex
index d8345f2..63f4b2a 100644
--- a/agenda/kernel-agenda.tex
+++ b/agenda/kernel-agenda.tex
@@ -184,8 +184,7 @@ Embedded Linux kernel and driver development training\\
\item Coding standards
\item Retrieving Linux kernel sources
\item Tour of the Linux kernel sources
- \item Kernel source code browsers: cscope, Kscope, Linux Cross
- Reference (LXR)
+ \item Kernel source code browsers: cscope, Kscope, Elixir
\end{itemize}
}
{Lab - Kernel sources}
diff --git a/agenda/kernel-fr-agenda.tex b/agenda/kernel-fr-agenda.tex
index ad00065..f87ce53 100644
--- a/agenda/kernel-fr-agenda.tex
+++ b/agenda/kernel-fr-agenda.tex
@@ -195,8 +195,7 @@ Session de 5 jours
\item Conventions de codage
\item Récupération des sources du noyau
\item Aperçu des sources du noyau
- \item Outils de navigation dans les sources : cscope, Linux Cross
- Reference (LXR)
+ \item Outils de navigation dans les sources : cscope, Elixir
\end{itemize}
}
{TP - Code source du noyau}
diff --git a/labs/boottime-kernel/boottime-kernel.tex b/labs/boottime-kernel/boottime-kernel.tex
index 44d8a26..57d265c 100644
--- a/labs/boottime-kernel/boottime-kernel.tex
+++ b/labs/boottime-kernel/boottime-kernel.tex
@@ -109,7 +109,7 @@ a function in the kernel sources. Try to find out in which source file
each function is defined\footnote{You can do it with utilities such as
\code{cscope}, which your instructor will be happy to demonstrate,
or through our on-line service to explore the Linux kernel sources:
-\url{http://lxr.free-electrons.com}}, and what each driver corresponds
+\url{http://elixir.free-electrons.com}}, and what each driver corresponds
to.
Then, you can look the source code and try look for obvious causes which
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 0ba7fdc..d246c50 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -91,7 +91,7 @@ register contains the location of the instruction being executed, find
in which function does the crash happen, and what the function call
stack is.
-Using LXR or the kernel source code, have a look at the definition of this
+Using Elixir or the kernel source code, have a look at the definition of this
function. This, with a careful review of the driver source code should
probably be enough to help you understand and fix the issue.
diff --git a/labs/kernel-i2c-communication/kernel-i2c-communication.tex b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
index 9cff335..427d3c6 100644
--- a/labs/kernel-i2c-communication/kernel-i2c-communication.tex
+++ b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
@@ -194,11 +194,11 @@ In the probe routine (run every time a matching device is found):
\code{0xf0} instead. This works across all brands of nunchuks
(including Nintendo ones).}.
Make sure you check the return value of the function you're
- using. This could reveal communication issues. Using LXR, find
+ using. This could reveal communication issues. Using Elixir, find
examples of how to handle failures properly using the same
function.
\item Let the CPU wait for 1 ms by using the \code{msleep()} routine.
- You may need to use LXR again to find the right C headers to
+ You may need to use Elixir again to find the right C headers to
include.
\item In the same way, send the \code{0xfb} and \code{0x00} bytes now.
This completes the nunchuk initialization.
@@ -252,7 +252,7 @@ Using boolean operators, write code that initializes a \code{zpressed}
integer variable, which value is \code{1} when the \code{Z} button is
pressed, and \code{0} otherwise. Create a similar \code{cpressed}
variable for the \code{C} button\footnote{You may use the \code{BIT()}
-macro, which will make your life easier. See LXR for details.}.
+macro, which will make your life easier. See Elixir for details.}.
The last thing is to test the states of these new variables at the end
of the \code{probe()} function, and log a message to the console
diff --git a/labs/kernel-sources-exploring/kernel-sources-exploring.tex b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
index caed737..7a683bc 100644
--- a/labs/kernel-sources-exploring/kernel-sources-exploring.tex
+++ b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
stable kernel version (from the \code{stable} kernel tree).
\item Explore the sources and search for files, function headers or
other kinds of information\ldots
-\item Browse the kernel sources with tools like \code{cscope} and LXR.
+\item Browse the kernel sources with tools like \code{cscope} and Elixir.
\end{itemize}
\section{Choose a particular stable version}
@@ -65,7 +65,7 @@ files).
Now that you know how to do things in a manual way, let's use more
automated tools.
-Try LXR (Linux Cross Reference) at \url{http://lxr.free-electrons.com}
+Try Elixir at \url{http://elixir.free-electrons.com}
and choose the Linux version closest to yours.
If you don't have Internet access, you can use \code{cscope} instead.
diff --git a/slides/about-us/about-us.tex b/slides/about-us/about-us.tex
index 7038e5c..a5174a9 100644
--- a/slides/about-us/about-us.tex
+++ b/slides/about-us/about-us.tex
@@ -32,8 +32,8 @@
\url{http://linkedin.com/groups/Free-Electrons-4501089}
\item Quick news (Twitter):\\
\url{http://twitter.com/free_electrons}
- \item Linux Cross Reference - browse Linux kernel sources on-line:\\
- \url{http://lxr.free-electrons.com}
+ \item Elixir - browse Linux kernel sources on-line:\\
+ \url{http://elixir.free-electrons.com}
\end{itemize}
\end{frame}
diff --git a/slides/boottime-kernel/boottime-kernel.tex b/slides/boottime-kernel/boottime-kernel.tex
index aea5733..af61dc5 100644
--- a/slides/boottime-kernel/boottime-kernel.tex
+++ b/slides/boottime-kernel/boottime-kernel.tex
@@ -49,8 +49,8 @@ take most time to execute.
Start working on the functions consuming most time first. For each
function:
\begin{itemize}
-\item Look for its definition in the kernel source code. You can use LXR
- (for example \url{http://lxr.free-electrons.com}).
+\item Look for its definition in the kernel source code. You can use
+ Elixir (for example \url{http://elixir.free-electrons.com}).
\item Remove unnecessary functionality:
\begin{itemize}
\item Look for kernel parameters in C sources and Makefiles, starting
diff --git a/slides/kernel-source-code-management/elixir.png b/slides/kernel-source-code-management/elixir.png
new file mode 100644
index 0000000..afd2fba
Binary files /dev/null and b/slides/kernel-source-code-management/elixir.png differ
diff --git a/slides/kernel-source-code-management/kernel-source-code-management.tex b/slides/kernel-source-code-management/kernel-source-code-management.tex
index 25b0dce..547486a 100644
--- a/slides/kernel-source-code-management/kernel-source-code-management.tex
+++ b/slides/kernel-source-code-management/kernel-source-code-management.tex
@@ -32,26 +32,26 @@
\end{frame}
\begin{frame}
- \frametitle{LXR: Linux Cross Reference}
+ \frametitle{Elixir: browsing the Linux kernel sources}
\begin{itemize}
- \item Generic source indexing tool and code browser
+ \item \url{https://github.com/free-electrons/elixir}
+ \item Generic source indexing tool and code browser.
+ Inspired by the LXR project (Linux Cross Reference).
\item Web server based, very easy and fast to use
\item Very easy to find the declaration, implementation or usage
of symbols
\item Supports C and C++
- \item Supports huge code projects such as the Linux kernel (431 MB
- of source code in version 3.0).
+ \item Supports huge code projects such as the Linux kernel
\item Takes a little time and patience to setup (configuration,
indexing, web server configuration)
- \item You don't need to set up LXR by yourself. Use our
- \url{http://lxr.free-electrons.com} server!
- \item \url{http://sourceforge.net/projects/lxr}
+ \item You don't need to set up Elixir by yourself. Use our
+ \url{http://elixir.free-electrons.com} server!
\end{itemize}
\end{frame}
\begin{frame}
- \frametitle{LXR screenshot}
+ \frametitle{Elixir screenshot}
\begin{center}
- \includegraphics[height=0.8\textheight]{slides/kernel-source-code-management/lxr.png}
+ \includegraphics[height=0.8\textheight]{slides/kernel-source-code-management/elixir.png}
\end{center}
\end{frame}
diff --git a/slides/kernel-source-code-management/lxr.png b/slides/kernel-source-code-management/lxr.png
deleted file mode 100644
index bab49f2..0000000
Binary files a/slides/kernel-source-code-management/lxr.png and /dev/null differ
More information about the training-materials-updates
mailing list