summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Release version 1.8HEADv1.8masterStephen Warren2018-06-181-1/+1
| | | | | | | | | | | | Changelog: - Support for production devices with PKC - Support for --gen-signed-msgs, --signed-msgs, and --download-signed-msgs options. - Support for --usb-timeout option. - Various man page and code cleanups. - Compilation fix when cryptopp isn't installed system-wide. Signed-off-by: Stephen Warren <swarren@nvidia.com>
* Don't assume cryptopp is system-wide installedThomas Petazzoni2017-10-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The current build system adds "-isystem /usr/include/$(CRYPTOLIB)" to AM_CPPFLAGS, but this is wrong because cryptopp might not be installed in this location. Instead, the build system should simply include <cryptopp/...> or <crypto++/...> and rely on the compiler include path. The tricky part is that it can be <cryptopp/...> or <crypto++/...>. To solve this, we use a solution similar to the one used in https://github.com/bingmann/crypto-speedtest/blob/master/m4/cryptopp.m4 and https://github.com/bingmann/crypto-speedtest/blob/master/src/speedtest_cryptopp.cpp: the configure script fills in a variable called CRYPTOLIB_HEADER_PREFIX, and we use that in the C++ code to include the right header file. It is worth mentioning that doing #include <CRYPTOLIB_HEADER_PREFIX/foobar.h> doesn't work, and we have to use an intermediate #define'd constant to overcome this C preprocessor limitation. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> (swarren, apply the same change to rsa-pss.cpp) Signed-off-by: Stephen Warren <swarren@nvidia.com>
* Release version 1.7v1.7Stephen Warren2015-10-161-1/+1
| | | | | | | | | | Changelog: - Documented patch submission process in this file - Added better USB debugging message - Require a specific minimum version of libusb - Added --usb-port-path cmdline option Signed-off-by: Stephen Warren <swarren@nvidia.com>
* configure.ac: Request at least libusb 1.0.9Tobias Klauser2015-04-131-1/+1
| | | | | | | | | | | | | tegrarcm needs at least libusb 1.0.9 which introduces libusb_error_name. Otherwise the build fails with the following linker error: usb.o: In function `usb_read': .../tegrarcm/src/usb.c:260: undefined reference to `libusb_error_name' usb.o: In function `usb_write': .../tegrarcm/src/usb.c:233: undefined reference to `libusb_error_name' Signed-off-by: Tobias Klauser <tklauser@distanz.ch> Signed-off-by: Stephen Warren <swarren@nvidia.com>
* tegrarcm: Version 1.6v1.6Allen Martin2014-04-111-1/+1
| | | | | | | | Update version number to 1.6 and update changelog in README for version 1.6 release notes. Signed-off-by: Allen Martin <amartin@nvidia.com> Acked-by: Stephen Warren <swarren@nvidia.com>
* tegrarcm: Bump version to 1.5v1.5Allen Martin2013-09-201-1/+1
| | | | | | | | Update README with change log for version 1.5, and bump version number. Signed-off-by: Allen Martin <amartin@nvidia.com> Reviewed-by: Stephen Warren <swarren@nvidia.com>
* tegrarcm: Bump version to 1.4v1.4Allen Martin2013-06-171-1/+1
| | | | | | | Bump the version number to 1.4 and update change log. Signed-off-by: Allen Martin <amartin@nvidia.com> Acked-by: Stephen Warren <swarren@nvidia.com>
* Bump version to 1.3v1.3Allen Martin2013-05-021-1/+1
| | | | | | Bump the version number to 1.3 and update change log. Signed-off-by: Allen Martin <amartin@nvidia.com>
* Add -lpthread when looking for crypto++Alexandre Courbot2013-05-021-1/+1
| | | | | | | | | On some distributions (e.g. Arch Linux) configure will fail to find crypto++ because of the test program not linking due to undefined references to pthread functions. Signed-off-by: Alexandre Courbot <acourbot@nvidia.com> Acked-by: Allen Martin <amartin@nvidia.com>
* Bump version to 1.2v1.2Allen Martin2012-11-301-1/+1
| | | | | | | | | | Bump the version number to 1.2 and update change log. Signed-off-by: Allen Martin <amartin@nvidia.com> Change-Id: I188eba740904ba5f9cd43179e16a39c077900d19 Reviewed-on: http://git-master/r/164852 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Stephen Warren <swarren@nvidia.com>
* bump version to 1.1v1.1Allen Martin2012-06-261-1/+1
| | | | | | | Signed-off-by: Allen Martin <amartin@nvidia.com> Change-Id: I951992af094c79b610b2a6eb1cb10334780255c2 Reviewed-on: http://git-master/r/111441 Reviewed-by: Automatic_Commit_Validation_User
* drop old AM_INIT_AUTOMAKE styleMike Frysinger2012-06-261-1/+1
| | | | | | | | | | | | The AC_INIT call takes care of setting all these values, so no need to call the old AM_INIT_AUTOMAKE style anymore. Avoids duplication. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Change-Id: I01b31f198273537d55bb7b8db95eb75ba67b8450 Reviewed-on: http://git-master/r/111409 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Allen Martin <amartin@nvidia.com> Tested-by: Allen Martin <amartin@nvidia.com>
* use pkg-config for libusb-1.0 look upMike Frysinger2012-06-261-4/+2
| | | | | | | | | | More friendly to exotic libusb setups. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Change-Id: I36f54f2a6e36773c8cf213c56deea053b1f81083 Reviewed-on: http://git-master/r/111408 Reviewed-by: Allen Martin <amartin@nvidia.com> Tested-by: Allen Martin <amartin@nvidia.com>
* configure: fix double output of filesMike Frysinger2012-06-261-2/+4
| | | | | | | | | | No need to write out the Makefiles twice. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Change-Id: I756e365875d578843b8fdebe92cae23c07788367 Reviewed-on: http://git-master/r/111407 Reviewed-by: Allen Martin <amartin@nvidia.com> Tested-by: Allen Martin <amartin@nvidia.com>
* Handle multiple names for libcrypto++Allen Martin2012-04-031-3/+10
| | | | | | | | | | Add automake code to handle the different names libcrypto++ has on different systems (libcrypto++ vs libcryptopp). Change-Id: I052a9b099138478cf3324f5f99757f34c42eeb67 Reviewed-on: http://git-master/r/94266 Reviewed-by: Allen Martin <amartin@nvidia.com> Tested-by: Allen Martin <amartin@nvidia.com>
* tegra-rcm: Download code to tegra in recovery modeAllen Martin2012-04-031-0/+52
This program is used to download BCT and code to tegra from recovery mode. Only tegras that are configurated for "nvproduction" or "ODM open" mode are supported (no encryption). usage: tegra-rcm --bct=bctfile --bootloader=blfile --loadaddr=<loadaddr> --entryaddr=<entryaddr> bctfile is the name of the BCT (boot configuration table). It contains memory timing and boot device selection. blfile is the name of the booloader file. This is the code that downloaded and executed on the tegra SoC. loadaddr and entryaddr are the load and entry addresses of the bootloader in the tegra address map. Change-Id: I34754d3976f3971bdca1daefc5d1a2c69a56bbb5 Reviewed-on: http://git-master/r/94264 Reviewed-by: Allen Martin <amartin@nvidia.com> Tested-by: Allen Martin <amartin@nvidia.com>
View Lorry Controller Status