aboutsummaryrefslogtreecommitdiffstats
path: root/markdown/2015_07_rmll-feedback-optimus-black-advancement-and-cccamp.md
blob: a40aadc96975b1cb3705ae299715a3a07b0e338f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
tags: Events, Replicant news, Paul Kocialkowski
date: 2015-07-20T23:13:06+00:00
title: RMLL feedback, Optimus Black advancement and CCCamp
authors: Paul Kocialkowski
---
Two weeks ago, I took part in [RMLL][1] as advertised on the Replicant blog
shortly before the event. This year again, it was a really nice event to be a
part of. Lots of people showed interest for Replicant and some even came
specifically to see my talks about the project: what a pleasant surprise! The
videos of my talks are already available on the [RMLL website][2] and they
were also added to the [Conferences][3] page of the Replicant wiki.

Back from the event, the development effort was focused on cleaning up the
[bits and pieces laying around][4] for Optimus Black support in U-Boot, now
that the [merge window is open][5]. A [patch series][6] was sent for review
earlier today and despite being incomplete as of now, it will serve as a solid
base for future additions. Some more work is indeed required to have all the
necessary features supported, but those patches will be written in a non-
upstreamable way for Replicant at first. The current status of those [dirty
patches][7] allows booting CyanogenMod without too much trouble, except for
the occasional random reboot and other oddities that still have to be sorted
out before it can seriously be used for daily use.

Thus, with basic bootloader support out of the way, it's time to start the
Replicant port to the device. Communication with the modem will require some
heavy work on [Hayes-RIL][8], our implementation of the AT protocol radio
interface layer, that is supposed to be more modern and robust than other
implementations. Other fundamental parts required to have Replicant running
with sufficient features to make the device useful should be less trouble.

In a month or so, the [Chaos Communication Camp][9] will take place in
Germany, organized by the almost mythical [Chaos Computer Club][10]. Replicant
is going to [take part in the event][11], hopefully with a lightning talk
and/or less formal self-organized events. The camp will be a great occasion to
chat a bit about the current state of the art of software freedom on mobile
devices, and more! Various other interesting projects will be there as well:
members of the [Neo900 project][12] will hold the [Neo village][13], where
I'll be likely to be found. As usual, I'll also be available to verify the
Replicant release key fingerprint, help newcomers install Replicant on their
device and basically anything else that I can help with!

 [1]: <https://2015.rmll.info/>

 [2]: <https://video.rmll.info/>

 [3]:
<https://redmine.replicant.us/projects/replicant/wiki/Conferences#RMLL-2015>

 [4]:
<http://git.code.paulk.fr/gitweb/?p=u-boot.git;a=shortlog;h=refs/heads/sniper-wip>

 [5]: <http://www.denx.de/wiki/U-Boot/ReleaseCycle>

 [6]: <http://lists.denx.de/pipermail/u-boot/2015-July/219660.html>

 [7]:
<http://git.code.paulk.fr/gitweb/?p=u-boot.git;a=shortlog;h=refs/heads/sniper-next>

 [8]: <http://git.replicant.us/gitweb/?p=replicant/hardware/ril/hayes-ril.git;a=summary>

 [9]: <https://events.ccc.de/camp/2015/>

 [10]: <https://www.ccc.de/>

 [11]: <https://events.ccc.de/camp/2015/wiki/Projects:Replicant>

 [12]: <https://events.ccc.de/camp/2015/wiki/Projects:Neo900>

 [13]: <https://events.ccc.de/camp/2015/wiki/Village:Neo>