 Hello everyone. Thank you to attend this meeting. Why today is possible to switch to an open hardware Genneulinux PowerPC laptop? My name is Roberto Inocenti from Power Progress Community and a Profit Association. I'll give you a brief history. The beginning, six years ago, there was already other open-hardware notebook projects. There was a good number of Linux distro. We was a little group of opists. Nobody knew our project and we had already briefed the feasibility of the project. We have to solve the notebook chassis body problem. You can see a few pictures about the core team members and the founders members. In 2016, we have founded the association because it was needed to set up the project to collect the donation. We have continued that year to try to solve the notebook chassis body solution. At that moment, we used a video card with a development kit based on our PowerPC processor. In any case, our association that was set up four years ago had a different goal. One is to design open hardware accessible to the widest number of people. Another point is to facilitate and reuse of dismissal of cost hardware. Another point is to encourage people to use open software. The last one is to promote innovation in library scientific progress, supporting multi-cipity and variety in order to avoid monopolies. We are hobbyists. We work for fun on this project, on engineering our projects in our spare time. We are not getting paid, and so our project is realized thanks to engineers that we need to pay. So we have a very flexible business plan because it depends on donations. We have the need from the beginning to organize the nation campaign that doesn't depend on crown funding rules. And so we have set up our platform to receive donations. So we are around 50 volunteers, only few of us are electronic experts, and we have enough spare time to design an entire motherboard. And so the donation campaign are needed to pay the engineers. We have started three years ago the first donation campaign. We have set up a platform, our own platform to collect donations without a limit of time. And in that year 2017, we had defined a list of hardware requirements, and we was able to run the buy-in for power PC64 bit in our DevKit with the same processor of our motherboard. In 2018, we have started to design the electrical schematic, so the motherboard, and we have collected the needed donation to do it. And so the schematic was in progress in 2019. The electrical schematics was realized. We have started to visit the PCB donation campaign and the design of the PCB. And now we are very near to complete this project. One different difficult situation that we encountered was difficult to have a notebook chassis for a reduced number of pieces, because our projects cannot arrive to thousands of people. And so the numbers are so small that it is impossible to afford the cost to produce our own notebook chassis body from scratch. So we have one important task was to find a supplier that can give us a reduced number of pieces of notebook chassis already built for other architectures. It takes time, but we have found, two years ago, a slim book that allowed us to have this notebook chassis. And so this year we have designed our board to fit exactly in the slim book eclipse chassis. So thanks to the collaboration between our association, Slimbook and Acube System that designed the motherboard and we'll produce it. We was able to solve this difficult task. We have already, a few days ago, published the board layout of our motherboard. It is designed to fit in the Slimbook Eclipse body. This chassis is enough big to host our motherboard, even if it was not so simple to design the motherboard because we use a MXM graphics card and the original Slimbook Eclipse not, so it was not so simple to. We had in these last two years make a few steps to certify our motherboard our open source hardware. In any case, the certification process will be done after we finish to produce the design. And in any case, we have already clear that thanks to the collaboration of New York Technical Love and Policy Clinic, we have clear that the certification allow any open hardware project to have some part of the design that is not open source in case is not possible for us to force the vendors to permit us to open source everything. So nowadays, we have already contacted the more the major chip vendor of the biggest chip that we use in our motherboard. And at the moment, we have not received any stop about publish all the schematics and PCB. In any case, in case is not under our control to share everything. In any case, the certification is not lost because we need to do everything we can do to share what is needed to permit to other to modify read and improve our design. So we have selected the CERN license, the publication that we have done of the schematic are in ORCAD format because the designers use this. The selection of CERN open hardware license is because it's more written for hardware instead of GPL or other licensing. We have a see that there is a better protection for the licensor. Better, I mean, there are even other hardware license, open hardware license like TPR open hardware license, but the CERN look like more in protection to the licensor. So in this case, power provider community is the licensor and the producer will be the licensi. So licensi could modify our work, but modification must be available in the same equivalent license. So licensor is protected. Other important note related to this CERN open hardware license, that firmware driver any other software would require the home license. Intellectual property belongs to the licensor. The documentation must be provided in the right format to be modified. So we need to publish the source as we have already done with the schematics and we will do at the end of the process of the PCB design with the source of the PCB design. So it was not simple the choice of the processor because the processor that we have fined in six years ago, at the moment even today, was a processor Bigendian only, but in the same time that the hear pass or many of the distribution that use our PC architecture have dropped the support for Bigendian variant. And so for us it's very difficult to solve these Endian issues. And so there is a problem because, in fact, for us it's difficult to adopt a Bigendian processor, but we have not chose for notebook sector. And in the same time as in these years there are not other Bigendian hardware. So even the PowerPC distribution have not supported the Bigendian and so nowadays support PowerPC 64. In any case, for our point of view, if a software is designed from source only for an Endian architecture, I mean Bigendian only for Little Endian, in some way this block the possibility to reuse hardware to reuse the software. And so it's not good even for the environment, even for the possibility to not use only a few hardware solutions to have the possibility to choice. So we want to ask the developer to take care about some good code practices that we will illustrate later. And in any case we are working to this activity to port the software in Bigendian and Little Endian, I mean that run to patch the software in the way that the software can run even in different Endian. And so we have started to work in particular to take care to port this software that is more influential in dependency. I mean that library like library that many other software use. So we are working to convert to patch these libraries, but we need the help because we are a few and there is a huge work to permit to other software that depend from these libraries to be compiled. So Endian is what is Endian is, is the way of the data is placed inside a memory computer. Effect Integer that is bigger than one byte, could be a problem when to architecture exchange data. And it is important for a developer to keep in mind when writing portable code. We see there is here an example of the data Bigendian, they read the left to right. And this is the example when the data is written right to left in Little Endian. There are a couple of methods to swap Endianess, a manual swapping or how to swapping. Here there are two different examples, one for 16 bit, another for 32 bit. You can see this different function for swap between Endian. So it is best to use this implementation. There are some useful tools that come from, for example, Endian.h and this is an example regarding this solution. There are useful automatic tools that make conversion in particular way because networking is Bigendian. And so every time the data will be exchanged in the network, it should be converting Bigendian. Here there are lists of standard Bigendian conversion and even there are not standard functions that are very useful. And there are a few examples about, for example, there is the work that some of us have done patching WebRG audio processing. There is here the example. So the data are stored in Little Endian and there is this approach to convert it. You can see different. Here there is one situation is when you write the data. And here there are more consideration and even other more that is about the header of the health file. Here there is a patch to translate one by one the content of other files. It is huge work. So we need the help. This, as this talk is not deep technical. I don't go deeper in this example even because I have no competence and even because it's not the primary topic. But in any case, if there are people that want to go more deep, they can contact us and our developer can go more deeper in this topic. And there is, you can find many of our patch that we have done in, to some libraries. So we have, you can see the examples. How to finance it? All this project is complex that have a different part. How to finance it? We have done already the two donation campaigns. We are in the third one and we have the next one that are the prototypes that are something very, very, very interesting. We have selected the donation campaign because we doesn't product anything because we have do an activity to support the design. But we are not a company. We are, as I already explained, a nonprofit association. So we cannot show before any prototype. We will arrive to the prototype now after already done donation campaign. If we have divided, as you can see before, sorry, we have divided in different phase, a donation in different campaign. So if a phase fail, we cannot give back the money because they are not refundable. No profit association in Italy that are not commercial cannot give back the donation. The donation are free, I mean for free, not forever in to receive anything in change. So in any case, donor, in case a phase fails, donor together decide the destination to be found to other projects of the association itself. We have a work to patch the PowerPCC64 packages. There is even a project about an open source laptop such a chassis design. And there are even activity to reuse dismisses computer for the schools. In any case, association activity are decided by its member. So potential donor might want to join PowerProgress community by paying the yearly membership fee. So anyone that want to join the association can. There are people that collaborate with the creation of multimedia design advertisement, people that help on translation, other on spreading the project on blog, form and social. Some other can assist us about Louvre and to support the licensing that we have. Other can help on maintain update software and other can help on make seminar in high schools and university. So we can spread the knowledge about design and open hardware mother board. Thank you. Now we have the possibility to talk together so you can ask me, we can go more deeper on the topics. Thank you.