tag:blogger.com,1999:blog-53079077947237179522024-03-19T04:05:57.610+01:00Romain Perier's blogRomain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-5307907794723717952.post-53699073726864121892020-02-13T19:50:00.001+01:002020-02-13T19:50:20.209+01:00Meetup Debian ToulouseHi there !<br />
<br />
My company <a href="https://www.viveris.fr/">Viveris</a> is opening its office for hosting a Debian Meetup in Toulouse this summer (June 5th or June 12th).<br />
<br />
Everyone is welcome to this event, we're currently looking for volunteers for presenting demo, lightning talks or conferences (following the talks any kind of hacking session is possible like bugs triaging, coding sprints etc).<br />
<br />
Any kind of topic is welcome.<br />
<br />
See the <a href="https://lists.debian.org/debian-devel-french/2020/02/msg00002.html">announcement</a> (in french) for more details.Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-84655679577396671032020-01-11T20:20:00.001+01:002020-01-11T20:20:10.467+01:00Add support for F2FS filesystem to GRUB and initramfs-toolsHi there,<br />
<br />
For these like me who want to change their root filesystem to F2FS, I have enabled support for adding the F2FS module in the EFI signed image of grub in Debian <a href="https://salsa.debian.org/grub-team/grub/commit/146d21cc9db01cca6f945e466e4adc31d165782b">(commit)</a>. So the grub EFI image can load configuration, kernel images and initrd from a /boot that is formatted in F2FS (the upstream grub supports the filesystem since 2.04).<br />
<br />
Now that the kernel is loading it must be able to mount the rootfs. In Debian, a lot of features like some filesystems or some drivers are built as modules, this allow to be able to boot and work on a lot of different machines without have to build-in statically everything into the linux kernel image. This is why we use an initramfs , it offers a variety of cool features and detects magically some details for you like "load the brtfs module or your favorite emmc driver as module". If you want to use F2FS as your main filesystem on your rootfs, we need to add F2FS as base module into initramfs-tools (that handles all the scripts and the magic stuffs for your initramfs). It has been done by this <a href="https://salsa.debian.org/kernel-team/initramfs-tools/commit/4df27e2cc6527d3b462ba7f22da465a662712f31">commit.</a><br />
<br />
<br />
See you !Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com1tag:blogger.com,1999:blog-5307907794723717952.post-25460622825902426902019-12-23T15:09:00.003+01:002019-12-23T15:20:51.944+01:00My Raspberry PI 4 4GBHi,<br />
<br />
I have received my Raspberry PI 4 4GB that has been funded by the Debian project. I would like to thank the DPL and Gunnar Wolf for this (who vouched for me).<br />
<br />
So today, I have unpacked the board and tested it with the default flashed noobs/raspbian, so I check that everything is working as expected (from the hw point of view, I already had bad suprises in the past with some evaluation boards). <br />
<br />
Interesting topics will come soon, mostly about booting a debian testing/sid on it , adding support to raspi-firmware and the linux kernel for enabling support for the pi 4 and some variants drivers for the bcm2711.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgcjiuydQNNy7ieLAZLsvDW_MweZIdTEk2iemkFIhFhzoUlWO-FGhrpUa2Gh1Tg53G-RfnLabdGPZYKhkFyU7V6zzD4vvfH4FOOUyNwRkw-0GFxSaqFT3hYW4_hw4BiKD4mzvSDXIpY3F4O/s1600/IMG-2005.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1200" data-original-width="1600" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgcjiuydQNNy7ieLAZLsvDW_MweZIdTEk2iemkFIhFhzoUlWO-FGhrpUa2Gh1Tg53G-RfnLabdGPZYKhkFyU7V6zzD4vvfH4FOOUyNwRkw-0GFxSaqFT3hYW4_hw4BiKD4mzvSDXIpY3F4O/s320/IMG-2005.jpg" width="320" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-kuPRGngE5alVog2o5zchGP7bcIqsD_X1Op810zpHS_Nf0BNq4GWRdx4lCcNFAbG7vJzjY7H_lAw2mQ1y0IIsUyJ3rnMKx8S1FXzOoLvnJ5F74URdJR88FsuavPebJo2Z-jgHTE4D96WI/s1600/IMG-2006.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1200" data-original-width="1600" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-kuPRGngE5alVog2o5zchGP7bcIqsD_X1Op810zpHS_Nf0BNq4GWRdx4lCcNFAbG7vJzjY7H_lAw2mQ1y0IIsUyJ3rnMKx8S1FXzOoLvnJ5F74URdJR88FsuavPebJo2Z-jgHTE4D96WI/s320/IMG-2006.jpg" width="320" /></a></div>
<br />
<br />
<br />
See you !Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-86746974820638576332019-11-26T13:24:00.001+01:002019-11-26T13:24:17.832+01:00RaspberryPi 3 desktop image running Debian Buster 10.2Hi !<br />
<br />
The Capitole Du Libre 2019 happened two weekend ago on 16th-17th November. I have helped the <a href="https://france.debian.net/">DebianFrance</a> team on the Debian booth. It was a super event with a lot of cool and interesting people !<br />
We promoted the Debian project and I have also presented a demo of a Raspberry PI 3 running a fresh debian 10.2 with a mainline linux kernel (for instance 4.19.x) with V3D or llvmpipe. The different persons I met were very interested by the availability of the image, so I have decided to write a debos recipe from scratch for ARM64-based RaspberryPI.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihYwbDSSCh8x4mdMkZqHi2cBnmPsQqhFGLuvBDzILVi_3UjrfVswXcYpkVMfpn053a7hajHUiPRItstcC8_mm73ZZwwt7MugbWYNTMQ0fatWhNPF8w3WSYLspvKWQo6oeWqDFnLOb0e0_v/s1600/IMG-1988.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1200" data-original-width="1600" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihYwbDSSCh8x4mdMkZqHi2cBnmPsQqhFGLuvBDzILVi_3UjrfVswXcYpkVMfpn053a7hajHUiPRItstcC8_mm73ZZwwt7MugbWYNTMQ0fatWhNPF8w3WSYLspvKWQo6oeWqDFnLOb0e0_v/s320/IMG-1988.jpg" width="320" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkBgVy7jBSd5KtmjS1QT0aV0Udp0KaPHn7O6hGOvg7u1MsM_p0Q1ow25csSXbm-R_ZDiERDdZeVsIhsWQDDPHsuYbKqoeqp60AFqijqVM24RW8z3x4X4m66FMkCB66deNqwiKE8ZicXNhz/s1600/IMG-1989.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1200" data-original-width="1600" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkBgVy7jBSd5KtmjS1QT0aV0Udp0KaPHn7O6hGOvg7u1MsM_p0Q1ow25csSXbm-R_ZDiERDdZeVsIhsWQDDPHsuYbKqoeqp60AFqijqVM24RW8z3x4X4m66FMkCB66deNqwiKE8ZicXNhz/s320/IMG-1989.jpg" width="320" /></a></div>
<br />
<br />
This is a desktop oriented image. It will start an lxde session automatically with the "pi" user. The root accound is locked but you can use sudo with the "pi" user. <br />
<br />
You can find the recipe <a href="https://salsa.debian.org/raspi-team/image-specs/commit/c245be293e6d00773880ddb8f61dd23e9bc6fc65">here</a> . You can build an image ready to flash with the following commands:<br />
<pre><code>
$ git clone https://salsa.debian.org/raspi-team/image-specs.git
$ cd image-specs/debos
$ debos raspberrypi-desktop_arm64.yaml
</code>
</pre>
It should produce an image <b>raspberrypi-desktop_buster_arm64.img.gz</b>. Then, supposing that the device associated with your sdcard is <i>/dev/mmcblk0</i> , you can then flash this image by typing:<br />
<pre><code>
$ zcat raspberrypi-desktop_buster_arm64.img.gz | sudo dd of=/dev/mmcblk0 bs=4M status=progress
$ sync
</code></pre>
<br />
The VC4 graphical stack being still unstable in some cases, it is recommended to use llvmpipe for now (I have to investigate, I don't know yet if this is a bug in the DRI driver in mesa or a bug in the drm/kms driver).<br />
<br />
A recipe for running bullseye should come quickly :) <br />
<br />
<br />
Enjoy !Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-7674087251682425112019-11-15T19:36:00.000+01:002019-11-15T21:19:29.621+01:00Capitole du Libre 2019Hi !<br />
<br />
The <a href="https://2019.capitoledulibre.org/">Capitole Du Libre</a> is a french event that takes place at <a href="http://www.enseeiht.fr/">INP-ENSEEIHT</a> in Toulouse. It is an event dedicated to free and open source softwares. The Capitole Du Libre 2019 will happen this weekend on 16th-17th November.<br />
<br />
There will be a Debian booth with the <a href="https://france.debian.net/">DebianFrance</a> team, I will be there to help them. A lot of interesting talks will be presented, see the schedule <a href="https://2019.capitoledulibre.org/programme/#schedule">here</a>.<br />
<br />
<a href="https://www.viveris.fr/">Viveris</a>, my company, is a gold sponsor this year. During the year, some of my contributions are sponsorised by my company. <a href="https://www.viveris.fr/">Viveris</a> also sponsorised the demo I am going to present at the Debian booth, many thanks to her !Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-59818198870383526032019-10-27T12:29:00.000+01:002019-10-27T14:20:35.596+01:00Announcing official IRC channel for Raspberry PI in DebianHi !<br />
<br />
<br />
Debian for Raspberry Pi exists since few months on IRC, but nothing were done for creating an official channel (see <a href="https://wiki.debian.org/IRC">https://wiki.debian.org/IRC</a>) nor communication for announcing this channel on planet. The creation of #debian-raspberrypi, the official Debian channel for topics related to the Raspberry Pi boards in Debian, was done two weeks ago, so this is the right moment to announce it officially !<br />
<br />
<br />
Join us and say hello !<br />
<br />Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-29366181660255526102019-08-05T20:32:00.000+02:002019-08-05T20:32:06.680+02:00Free software activities in May, June and July 2019Hi Planet, it is been a long time since my last post. <br />
Here is an update covering what I have been doing in my free software activities during May, June and July 2019.<br />
<h2>
May</h2>
Only contributions related to Debian were done in May<br />
<ul>
<li> linux: Update to 5.1 (including porting of all debian patches to the new release)</li>
<li>linux: Update to 5.1.2</li>
<li>linux: Update to 5.1.3</li>
<li>linux: Update to 5.1.5</li>
<li>firmware-nonfree: misc-nonfree: Add GV100 signed firmwares (Closes: #928672)</li>
</ul>
<h2>
June </h2>
<h3>
Debian</h3>
<ul>
<li>linux: Update to 5.1.7</li>
<li>linux: Update to 5.1.8</li>
<li>linux: Update to 5.1.10</li>
<li>linux: Update to 5.1.11</li>
<li>linux: Update to 5.1.15</li>
<li>linux: [sparc64] Fix device naming inconsistency between sunhv_console and sunhv_reg (Closes: #926539)</li>
<li>raspi3-firmware: New upstream version 1.20190517</li>
<li>raspi3-firmware: New upstream version 1.20190620+1</li>
</ul>
<h3>
Kernel Self Protection Project</h3>
I have recently joined the kernel self protection protect, which basically intends to harden the mainline linux kernel the most as possible by adding subsystems that improve the security or make internal subsystems more robust to some common errors that might lead to security issues.<br />
<br />
As a first contribution, Kees Cook asked me to check all the NLA_STRING for non-nul terminated strings. Internal functions of NLA attrs expect to have standard nul-terminated strings and use standard strings functions like strcmp() or equivalent. Few drivers were using non-nul terminated strings in some cases, which might lead to buffer overflow. I have checked all the NLA_STRING uses in all drivers and forwarded a status for all of these. Everything were already fixed in linux-next (hopefully).<br />
<h3>
</h3>
<h2>
July</h2>
<h3>
Debian</h3>
<ul>
<li>linux: Update to 5.1.16</li>
<li>linux: Update to 5.2-rc7 (including porting of all debian patches to the new release)</li>
<li>linux: Update to 5.2</li>
<li>linux: Update to 5.2.1</li>
<li>linux: [rt] Update to 5.2-rt1</li>
<li>linux: Update to 5.2.4</li>
<li>ethtool: New upstream version 5.2</li>
<li>raspi3-firmware: Fixed lintians warnings about the binaries blobs for the raspberry PI 4</li>
<li>raspi3-firmware: New upstream version 1.20190709</li>
<li>raspi3-firmware: New upstream version 1.20190718</li>
</ul>
The following CVEs are for buster-security: <br />
<ul>
<li>linux: [x86] x86/insn-eval: Fix use-after-free access to LDT entry (CVE-2019-13233)</li>
<li>linux: [powerpc*] mm/64s/hash: Reallocate context ids on fork (CVE-2019-12817)</li>
<li>linux: nfc: Ensure presence of required attributes in the deactivate_target handler (CVE-2019-12984)</li>
<li>linux: binder: fix race between munmap() and direct reclaim (CVE-2019-1999)</li>
<li>linux: scsi: libsas: fix a race condition when smp task timeout (CVE-2018-20836)</li>
<li>linux: Input: gtco - bounds check collection indent level (CVE-2019-13631)</li>
</ul>
<h3>
Kernel Self Protection Project</h3>
I am currently improving the API of the internal kernel subsystem "tasklet". This is an old API and like "timer" it has several limitations regarding the way informations are passed to the callback handler. A future patch set will be sent to upstream, I will probably write a blog post about it. Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-15968398670174308662019-05-02T20:21:00.002+02:002019-05-02T20:21:45.069+02:00My work on Debian (April 2019)Hi,<br />
<br />
This is a summary of what I have done in April 2019 on Debian<br />
<br />
<h2>
Changes</h2>
<ul>
<li>I have uploaded raspi3-firmware 1.20190215-2 to sid </li>
<li>I have bumped raspi3-firmware to 1.20190401-1</li>
<li>I have bumped the preempt_rt kernel to 4.19.37-rt19 in sid</li>
<li>I have bumped the experimental kernel to 5.0.7</li>
<li>I have bumped the experimental preempt_rt kernel to 5.0.7-rt5</li>
<li>I have bumped the experimental kernel to 5.0.8</li>
<li>I have bumped the experimental kernel to 5.0.9</li>
<li>I have bumped the experimental kernel to 5.0.10 </li>
</ul>
<h2>
</h2>
<h2>
Issues</h2>
<ul>
<li>I have removed extra binary files from the orig tarball in raspi3-firmware, this closes #924315</li>
</ul>
<ul>
<li> I have enabled support for the coreboot memconsole in kernel 5.0.x. It has been backported into sid and should be part of buster. This closes bug #872069</li>
</ul>
<br />
<h2>
</h2>
Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-27508235376101471802019-04-06T19:07:00.004+02:002019-04-06T19:12:15.686+02:00My work on Debian (March 2019)This is a summary of what I have done in March 2019 on Debian (well, a bit late)<br />
<h2>
Changes</h2>
<ul>
<li>I have bumped linux to 4.19.27 in sid, see <a href="https://salsa.debian.org/kernel-team/linux/commit/8864787e6406530cd712de26a61b3815f1835f76">commit</a> </li>
</ul>
<ul>
<li>I have bumped linux to 4.19.28 in sid, see <a href="https://salsa.debian.org/kernel-team/linux/commit/340ed90d8e3bee860d75c306d28bfa0636714138">commit</a> </li>
</ul>
<ul>
<li>I have bumped linux to 5.0.5 in master, see <a href="https://salsa.debian.org/kernel-team/linux/commit/ac931a228d7b4e00417817a8f29a8fb3116ceeb2">commit</a></li>
</ul>
<ul>
<li>I have bumped ethtool to 5.0, see <a href="https://salsa.debian.org/kernel-team/ethtool/commit/dafc48451cf300da90cbe7ec546230e6fe8502a0">commit</a></li>
</ul>
<h2>
New features</h2>
<ul>
<li>I have re-worked the commit to get support for Raspberry PI 1 and Raspberry PI Zero for armel mergeable in the Linux kernel, see <a href="https://salsa.debian.org/kernel-team/linux/commit/f24c6b7b6088c8cd6b6c80f1b7bf8cb51f84bca4">commit</a></li>
<li>Patch for enabling support for CRASH_DUMP for armel and armhf was merged, see <a href="https://salsa.debian.org/kernel-team/linux/commit/693bbd783dbd681d88a628f6bc8444f5ad8a76a2">commit</a> </li>
<li>Patch for enabling support for STRICT_MODULE_RWX in the Linux kernel was merged, see <a href="https://salsa.debian.org/kernel-team/linux/commit/6b175bc9fd304d1cfed6bf81e43b911889970494">commit</a></li>
</ul>
<h2>
</h2>
<h2>
Issues</h2>
<ul>
<li>Changed raspi3-firmware to make the consoles easily configurable in cmdline.txt, this closes bug #926325, see <a href="https://salsa.debian.org/debian/raspi3-firmware/commit/582a801f86b4a9f2d206974a4d95784bb2d532dd">commit</a></li>
</ul>
<ul>
<li>Changed raspi3-firmware to use arm_64bit instead of the arm_control
bitfields for controlling 64bits mode, this closes bug #925062, see <a href="https://salsa.debian.org/debian/raspi3-firmware/commit/53624b47865a3efbdc372a0294a29faf0347d212">commit</a> </li>
</ul>
<ul>
<li> Switched raspi3-firmware to use package.maintscript, that solves lintian warnings, see <a href="https://salsa.debian.org/debian/raspi3-firmware/commit/62f2932cc861397870aafc2f2dad621bb421d924">commit</a> </li>
</ul>
<h2>
</h2>
<h2>
</h2>
Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0tag:blogger.com,1999:blog-5307907794723717952.post-58826969453599300132019-03-15T19:07:00.000+01:002019-03-15T20:50:10.485+01:00Hello planet !<h2>
Introducing myself </h2>
<br />
My name is Romain, I have been nominated to the status of Debian Maintainer recently. I am part of the debian-kernel team (still a padawan) since few months, and, as a DM, I will co-maintain the package raspi3-firmware with Gunnar Wolf.<br />
<br />
<h2>
Current contributions</h2>
<div class="planet-title">
As a kernel and linux en enginner, I focus on embedded stuffs and kernel development. This is a summary of what I have done in the previous months. <br />
<h3>
Kernel team</h3>
As a contributor, I work a various things, I try to work where help is the more needed. I have wrote a python script for generating debian changelog in firmware-nonfree, I have bumped the package for new releases. I bump the linux kernel for new upstream releases, I help to close and resolve bugs, I backport new features when it makes sense for doing so, enable new hardware and recently I have added new flavour for the RPI 1 and RPI Zero in armel ! (spoil)<br />
<h3>
Raspi3-firmware</h3>
I have recently added a new mode in the configuration file of the package that let you device what you would like to boot from the firmware. You can either boot a linux kernel directly, passing the adress of the initramfs to use, a baremetal application, or a second level bootloader like u-boot or barebox (personnally I prefer u-boot). From u-boot then, you can use extlinux and get a nice generated menu by uboot menu. I have also added the support for using the devicetree-blob of the RPI 1 and the RPI Zero W when the firmware boots the kernel directly. I am also participating for reducing lintian warnings, new upstream release and improvements in general.<br />
<h3>
U-Boot</h3>
I have recently sent a MR for enabling support for the RPI Zero W in uboot for armel and it was accepted (thanks to Vagrant). As I use U-Boot everyday on my boards, I will probably send others MR ;) </div>
<h3 class="c-welcome__title">
Raspberry Pi Zero</h3>
<div class="planet-title">
As written described above, I have added a flavour for enabling support for the RPI1 and RPI Zero in armel for Linux 4.19.x. Like the Raspberry PI 3, there are no official images for this, but you can use debos or vmdb2 for building a buster image for your PI Zero. I have personally tried it, at home. I was able to run an LXDE session, with llvmpipe (I am still investigating if vc4 in gallium works for this SoC or not, while it's working perfectly fine for the PI3, it fallback to llvmpipe on the PI Zero).</div>
<h3 class="planet-title">
Raspberry Pi 3</h3>
<div class="planet-title">
<span style="font-weight: normal;">As posted on planet recently by Gunnar, you can find an unofficial image for the PI 3 if you want to try it. On buster you will be able to run a kernel 4.19.x LTS with an excellent DRM/KMS support and Gallium support in mesa. I was able to run a LXDE session with VC4 gallium here !</span></div>
<div class="planet-title">
<br />
<h2>
Future work</h2>
<br />
I will try my best to get an excellent support for all Raspberry PI in Debian (with unofficial images at the beginning). Including kernel support, kernel bugs fixes or improvements, debos and/or vmdb2 recipes for generating buster images easily, and even graphical stack hacks :) . I will continue my work in the kernel-team, because there are a tons of things to do, and of courses as co-maintainer, maintain raspi3-firmware (that will be probably renamed to something more generic, *spoil*).</div>
<br />Romain Perierhttp://www.blogger.com/profile/13641086798671459455noreply@blogger.com0