Select Git revision
Search by author
- Any Author
- authors
-
Adam Wujek awujek
-
Adrian Savencu a.savencu
-
Alessandro Rubini rubini
-
Aravind Subbiah asubbiah
-
Benoit Rat benoit
-
Cesar Prados bradomyn
-
Christos Gentsos cgentsos
-
Enkhbold Ochirsuren ebold
-
Erik van der Bij erikvanderbij
-
Evangelia Gousiou egousiou
-
Fabian Mauchle fmauchle
-
Federico Vaga FedericoVaga
-
Grzegorz Daniluk greg.d
-
Harvey Leicester hleicest
-
Ilia Slepnev islepnev
-
Javier Serrano serrano
-
Jean-Claude BAU baujc
-
José López Jiménez jose.lopez
-
José Luis Gutiérrez jlgutierrez
-
Juan David González Cobas dcobas
- Dec 01, 2016
-
-
Adam Wujek authored
Disable the Bad Block Table (BBT) because the BBT uses the 4 last PEBs of nand flash, which overwrites UBIFS. BBT was disabled in the old kernel. There is not so much performance penalty due to that (see the last sentence in the citation below). There is no impact on the reliability of a flash because this is just a table of bad blocks which is otherwise recreated in the ram at every boot. The MTD layer supplies upper layers (including UBI) with information about bad PEBs. It keeps so-called bad block table in RAM, which is usually 1 bit per PEB. When the driver initializes, it has to build this table by scanning whole flash media, which normally includes reading OOB area of 1st NAND page of each PEB. This takes time and may be improved by using on-flash BBT (bad block table). In this case the bad PEB map is stored on flash and MTD does not have to do any scanning. See the NAND_USE_FLASH_BBT constant in the Linux source codes. But note, bad PEB scanning is usually minor comparing to the UBI scan time, so on-flash BBT is not probably going to give much. (http://www.linux-mtd.infradead.org/faq/ubi.html#L_attach_faster ) Signed-off-by:
Adam Wujek <adam.wujek@cern.ch>
-
Signed-off-by:Federico Vaga <federico.vaga@cern.ch>
-
Adam Wujek authored
Since the buildroot anyway downloads .xz archive of the kernel for linux-headers we can avoid downloading the gz archive for our kernel compilation. Signed-off-by: -
Adam Wujek authored
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
-
Signed-off-by: -
Adam Wujek authored
include CROSS_COMPILE Signed-off-by: -
The configuration was installing the kernel headers from version 4.4 but we were using 2.6.39 and now we are using 3.16.37. Fix this by configuring the 3.16.37 as Linux versin to use to get headers Signed-off-by: -
Signed-off-by:Federico Vaga <federico.vaga@gmail.com>
-
Signed-off-by: -
It happens that headers have different sources: buildroot and our own kernel. For the standard path we have headers from buildroot which include also some kernel header. For the kernel, we have direct access to those headers. this means that we mya have conflict in our user-space programs. This patch does not solve the problem but it just reduce its effects. Signed-off-by: -
The Linux kernel 3.16.37 does not export, or does not have, anymore some hardware headers. Here I copy all the values we need. The real fix should be to create a set of WRS headers with all the symbols we need so that we do not depend anymore on other projects. Signed-off-by: -
Signed-off-by: -
The USB gadget framework has changed from Linux v2.6.39. As far as I understood it's now more modular, so it's not anymore enough to load just the g_serial.ko driver. Now we have to load also it's dependencies. I'm not an expert about USB gadget, this patch is the result of my understanding in debugging the loading failure of the g_serial.ko module. Perhaps it will be necessary some adjustments to make it work the way we want. But for the time begin I will leave it like this until is clear what we have to adjust. Note that these dependecies depends also on the configfs file-system. I had problems to get this work because apparently by using a different corss-compiler some symbols where removed from the kernel, so our modules were not able to load because of "undefined symbols". Using the toolchain compiled within this project solved this issue. Signed-off-by: -
The aim of this module is to register all the FPGA devices Signed-off-by: -
Actually, this is not what I want. I would like to just use an IRQ resource with the correct IRQ number. What I want is to hide the IRQ domain knowledge elsewhere. For instance, in the wrs_device module that register all our devices. But, since I have to update the kernel with the least number of changes I will leave this for the future. Signed-off-by: -
Copy the vic IRQ controller from the coht-vic repository. The maintainer prefers to have a copy instead of a submodule. Signed-off-by: -
Many mach headers has been moved out of scope. Of course they are still accessible by in an ugly way. Here I'm following the ugly way in order to get something working. What to do with this headers, perhaps, needs a discussion. I personally think that we need our local headers with hardware definitions. The reason is that we saw that in future kernel version some of these headers complitely disappear. The hardware definitions never change so we can safely copy them and remove a dependency with an external project. Signed-off-by: -
Instead of using clocksource_register() we use clocksource_register_hz() as suggested From kernel patch c7f798e3722610d486e951f04bbc00b6ba124d62 clocksource: Get rid of clocksource_calc_mult_shift() No one is using this, so encourage the use of clocksource_register_hz/khz(), and drop this helper. Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by:Yong Zhang <yong.zhang0@gmail.com> [jstultz: tweaked commit message] Signed-off-by:
John Stultz <john.stultz@linaro.org> Signed-off-by:
-
Signed-off-by: -
The version 3.16.37 is going to be supporter until 2020 Signed-off-by: -
Adam Wujek authored
Also remove link to at91_softpwm.h Signed-off-by: -
Adam Wujek authored
By this we drop support of wrs < 3.30. At least its fan. Signed-off-by: -
On modern switches the fan are driver by a dedicated FPGA core that does the PWM. This module is not necessary anymore and not even the kernel patches to make this module work. Signed-off-by: -
Adam Wujek authored
Our software runs only on a single kind of CPU, so we don't need to calculate it at every boot. The way how daemons are spawned at boot changed since the function shw_udelay_init was written. Before daemons were spawned one after another, now they are spawned at the same time and compete during initialization phase for the CPU. The loop calculating loops_per_msec was interrupted by few context switches. When using the kernel 2.6.39, the problem was not visible and usually loops_per_msec was estimated correctly. However, introduction new kernel 3.16 lowered probability of getting correct results. Probably due to the different behaviour of the scheduler. Bug was found because HAL was not able to detect SFP with vn=ZyXEL pn=SFP-BX1310-10-D vs=S131151000226 Signed-off-by: -
Adam Wujek authored
Explicitly define which version of buildroot should be used. It solves problem when there is more than one directory matching build/buildroot-2* Signed-off-by: -
Adam Wujek authored
Signed-off-by: -
Signed-off-by: -
The variable is unused because there is no need to use it. The color is white by default; indeed, this variable was set to "WHITE" everytime, but then not used. Signed-off-by: -
Today it is not really important to do this because all our modules are within the project itself. But, at somepoint, we may use submodules in order to integrate drivers from external sources; so, we need to export our default values because we will not have control over the other projects Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
We want '/dev/shm' to be empty at boot time. It may happen that while working with rootfs over NFS this directory is not empty. With this patch we remove all files from this directory because they should not be there at all. What if I put something there on purpose? When using tmpfs, files in '/dev/shm' will be automatically removed on shutdown. We are keeping the same behavior. Put your own development files in '/dev/shm' after the execution of this script by copying them from another location. Again, if we use rootfs over NFS and if tmpfs does not work then the system will use the NFS and the system should continue to work. In this case the performances will be much worst Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
This way, next time we want to update the kernel we have just to change the version without touching too much the code Signed-off-by: -
The kernel version is hardcoded here. Take it at runtime by using `uname -r`. This will reduce incompatibilities on kernel updates Signed-off-by: -
Adam Wujek authored
Complement of a commit: 02bb6153 rootfs: use /etc/ppsi.conf not /wr/etc/ppsi.conf Signed-off-by:
-
