- 07 Apr, 2015 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 05 Jan, 2015 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>
-
- 28 Jul, 2014 1 commit
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 12 Jun, 2014 3 commits
-
-
Federico Vaga authored
src point to the source code. Obj point to the object. Sometimes they live toghether but users can decide to build the object outside the source tree (e.g. O=/output/path/). Signed-off-by: Federico Vaga <federico.vaga@cern.ch> Acked-by: Alessandro Rubini <rubini@gnudd.com>
-
Federico Vaga authored
Remove binaries on clean Signed-off-by: Federico Vaga <federico.vaga@cern.ch> Acked-by: Alessandro Rubini <rubini@gnudd.com>
-
Federico Vaga authored
The main reason to introduce this EXTRACFLAGS variable is to allow people to cross compile on x86 architectures over 32bits and 64bits make EXTRACFLAGS="-m32" make EXTRACFLAGS="-m64" Signed-off-by: Federico Vaga <federico.vaga@cern.ch> Acked-by: Alessandro Rubini <rubini@gnudd.com>
-
- 21 Feb, 2014 2 commits
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Tomasz Wlostowski authored
This completes the show_sdb_tree functionality, with the new informative fields. The output for a verbose module is now like this (long lines are unavoidable): SDB: 00000651:e6a542c9 WB4-Crossbar-GSI SDB: 0000ce42:00000601 WB-DMA.Control (00001000-0000103f) SDB: 0000ce42:779c5443 WB-OneWire-Master (00001100-000011ff) SDB: 0000ce42:00000603 WB-SPEC-CSR (00001200-0000121f) SDB: 0000ce42:00000013 WB-VIC-Int.Control (00001300-000013ff) SDB: 0000ce42:d5735ab4 WB-DMA.EIC (00001400-0000140f) SDB: 00000651:eef0b198 WB4-Bridge-GSI (bridge: 00002000) SDB: 00000651:e6a542c9 WB4-Crossbar-GSI SDB: 0000ce42:123c5443 WB-I2C-Master (00003000-000030ff) SDB: 0000ce42:e503947e WB-SPI.Control (00003100-0000311f) SDB: 0000ce42:123c5443 WB-I2C-Master (00003200-000032ff) SDB: 0000ce42:00000608 WB-FMC-ADC-Core (00003300-0000337f) SDB: 0000ce42:779c5443 WB-OneWire-Master (00003400-000034ff) SDB: 0000ce42:26ec6086 WB-FMC-ADC.EIC (00003500-0000350f) SDB: 0000ce42:00000604 WB-Timetag-Core (00003600-0000367f) SDB: Synthesis repository: git://ohwr.org/fmc-projects/fmc-adc-100m14b4cha.git SDB: Bitstream 'spec_top_fmc_adcmc-projects/fmc-adc-100m14b4cha.git' \ synthesized 20140116 by mcattin (ISE version 133), commit f0a539dffe6d Signed-off-by: Tomasz Wlostowski <tomasz.wlostowski@cern.ch> Acked-by: Alessandro Rubini <rubini@gnudd.com>
-
- 14 Feb, 2014 2 commits
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 11 Feb, 2014 1 commit
-
-
Alessandro Rubini authored
This allows easier modification to the eeprom than loading the fmc-write-eeprom module. The carrier driver will likely refuse writing if the FPGA is not running the golden gateware image. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 28 Jan, 2014 1 commit
-
-
Joe Perches authored
This 444 should have been octal. Signed-off-by: Joe Perches <joe@perches.com>
-
- 21 Jan, 2014 1 commit
-
-
Alessandro Rubini authored
The code reported wrong addresses in the sdb dumps. All sdb addresses are relative, but the code was adding the base address twice. Bug exposed by a gateware image with two bridge levels. Reported-by: Juan David Gonzalez Cobas <dcobas@cern.ch> Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 18 Nov, 2013 1 commit
-
-
Alessandro Rubini authored
At registration and unregistration time, I was checking fmc->flags for FMC_DEVICE_NO_MEZZANINE, to skip initialization and cleanup for empty slots. But the check was wrong (see previous commit) and the conditional was never triggered. I think we should register slots with no mezzanines, because the carrier may offer some support anyways (the SPEC does), so the commit removes the conditionals instead of fixing them. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 04 Nov, 2013 1 commit
-
-
Alessandro Rubini authored
The flag must be checked with "&", not "==". When I tested it was the only flag, so I didn't notice. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 01 Jul, 2013 3 commits
-
-
Dan Carpenter authored
The call to kzalloc() wasn't checked. The dev_info() message dereferenced freed memory on error. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Alessandro Rubini <rubini@gnudd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Dan Carpenter authored
If we don't allocate "arr" then the cleanup path will dereference it and oops. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Alessandro Rubini <rubini@gnudd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Arnd Bergmann authored
The use of the 'readl' and 'writel' identifiers here causes build errors on architectures where those are macros. This renames the fields to read32/write32 to avoid the problem. Reported-by: kbuild test robot <fengguang.wu@intel.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Alessandro Rubini <rubini@gnudd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- 07 Jun, 2013 2 commits
-
-
Juan David González Cobas authored
For traceability purposes, we include commit descriptions as MODULE_VERSION information in drivers that are deployed in CERN control system. Ideally, the commit description should be added to all the binary blobs installed, but the kernel module is critical in this connection, as it is crucial to trace back quickly the whereabouts of installed .ko sources.
-
Alessandro Rubini authored
Change suggested by Emilio Cota, whose coccicheck is newer than mine. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 30 May, 2013 3 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>
-
- 27 May, 2013 1 commit
-
-
Michel Arruat authored
If a client registered with a null fmc-hwdev, there was a small memory leak.
-
- 21 May, 2013 2 commits
-
-
Alessandro Rubini authored
For multi-mezzanine environments, the hwdev name (the carrier) is not very meaningful, so use fmc->dev for messages as soon as the device is registered. Change suggested by David Cobas. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Multi-slot boards like the svec may have one ore more empty slots. This patch makes the core ignore empty slots, but otherwise succeed. Carriers are not expected to register completely-empty mezzanine sets (but if that happens registration succeeds with no effect). Change suggested by David Cobas. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 20 May, 2013 1 commit
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 16 May, 2013 2 commits
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
After correctly allocating the the manufacturer or device name, and correctly copying the not-null-terminated string from ipmi-fru, I put the termination '\0' at string[len + 1] . If you build a recent kernel under slob (which is the default), it may fail miserably at unexpected places. For example, if your string is 15 bytes, I allocated 16 but wrote to the 17th. slob has 16-byte alloc areas, and so I was corrupting the next area. This never happened with slab (which I prefer and run) because the smalles allocation chunk there is 32 bytes -- I would experience the same with a 31-long manufacturer or device name. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 15 May, 2013 6 commits
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com> Conflicts: doc/fmc-bus.in
-
Alessandro Rubini authored
This is only exposed by building for older kernels, as currently err.h is pulled in by other headers I use, it seems 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
The example files and configuration matches what is current in the fdelay driver, to be released soon after this very package. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 26 Apr, 2013 1 commit
-
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 17 Apr, 2013 4 commits
-
-
Alessandro Rubini authored
This allows easy access to the eeprom of each mezzanine. For example I see one at /sys/bus/fmc/devices/FmcDelay1ns4cha-f001/eeprom (fakedev with a fine-delay eeprom image). Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
The device is freed while its same work queue is running. I don't know if this is safe, but definitely using a static work queue is. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
My previous code for device management was wrong, because I didn't understand the allocation. This fixes the thing, by properly using the release function. This change however requires that all fmc devices are allocated separately (not as an array) and are not freed by the registering entity. So this introduces an incompatible change in the prototype for register_n and unregister_n -- which is noted at build time, but also an incompatible change in how a device must be allocated/freed by the carrier that registers a single device. This change is not introducing a build error, but I hope the only external users by now are the SPEC and the SVEC. fmc-fakedev is fixed by this same commit. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
The fmc devices are now children of their own device. This is what we had with fmc-fakedev and 1 mezzanine using a custom eeprom: tha lead to custom names): spusa.root# ls -l /sys/bus/fmc/devices/ FmcDelay1ns4cha-f001 -> ../../../devices/fmc/FmcDelay1ns4cha-f001/ And this is what we have now: spusa.root# ls -l /sys/bus/fmc/devices/ FmcDelay1ns4cha-f001 -> ../../../devices/fake-fmc-carrier/FmcDelay1ns4cha-f001/ Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-