- 02 Dec, 2014 7 commits
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
commit inspited by commit from spec-sw repo: kernel/wr_nic: fix rx timestamps c246c3ceSigned-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
This change adds warnings, but they will disappear after move to 3.14, where %pa is supported. Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
-
Adam Wujek authored
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 27 Oct, 2014 6 commits
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 18 Sep, 2014 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 13 Aug, 2014 5 commits
-
-
Federico Vaga authored
There should not be any side effect on resetting the FGPA every time we program it. Confirmed by Tomasz Wlostowski <tomasz.wlostowski@cern.ch> Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-nof -by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 07 Aug, 2014 1 commit
-
-
Federico Vaga authored
With some kernel configuration the previous locking policy can generate a deadlock on the spec->irq_lock spinlock. For example, this will happen sistematically if the option CONFIG_DEBUG_SHIRQ_FIXME is enabled. In this case, the handler is called immediatly an it is not a separeted thread. This patch move out from the locking section what doesn't need protection and is 'cause' of the deadlock. The deadlock was introduced with patch d4bbcc73 by using a large locking section. In realty the PCI request_irq is protected anyway thanks to the proctection of the variable 'first_time' and the 'spec_vic_irq_request' function. [more explaination about patch d4bbcc73] The purpose of that patch was to protect the initialization of the first VIC handler and the release of the last one. It was happening that while we are releasing the last VIC handler, some one was registering a new one but the spec->vic is still there. The result was that sometimes the PCI handler was removed (last VIC handler) but not re-requested for the incoming request. Signen-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 01 Aug, 2014 2 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 25 Jul, 2014 1 commit
-
-
Federico Vaga authored
Sometimes (expecially in cross-compilation context) t is necessary to use different environments. Instead of complicate this makefile, include an external one with user code. Create a local file named Makefile.specific, and write here your code. Bear in mind that Makefile.specific will run before the Makefile. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 23 Jul, 2014 7 commits
-
-
Federico Vaga authored
Note by Federico Vaga <federico.vaga@cern.ch> This is not exactly the same set of patches from garcialasheras <javier@garcialasheras.com>. I did few modification in order to: - do not introduce new dependecies. Vendor and Device ID are constant for life, so we can safely write them two times and avoid a file dependencies between kernel and userspace code. - squash FIX patches in 1d8bb157. There were consecutive patches where the FIX patch just fix the previous patch, so squash them. This will produce an useful git-blame and bit-bisect - una patch for each behavioral modification
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Before this patch, on spec_check_id() error spec_scan() returns that it found a SPEC, but it is not true. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
garcialasheras authored
-
garcialasheras authored
-
garcialasheras authored
-
garcialasheras authored
-
- 22 Jul, 2014 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 14 Jul, 2014 1 commit
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 08 Jul, 2014 5 commits
-
-
Federico Vaga authored
-
Federico Vaga authored
Protecting the handlers' vector is not enough. Managing the interrupts involves other tasks that must be serialized. Mainly to handle the first request and the last free of a VIC handler. The VIC internal locking (vec_lock) is not useful anymore, but I do not remove it because theoretically the VIC should be an independent bunch of code. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
When possible, avoid statement-scope variable for a better maintanability of the code. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
If there are no reasons for a *_free() function to return an error, change the return type to void Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The spec->irq_lock is a SPEC spinlock, but we must protect VIC variables. In order to make the VIC code independent, use a dedicated VIC spinlock Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 02 Jul, 2014 3 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Make the VIC code indipendently as much as possible Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Use the specular name: we used init, we should use exit Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-