- 12 3月, 2020 8 次提交
-
-
由 AKASHI Takahiro 提交于
We want to always run RSA library test on sandbox build in Travis CI. Just adding CONFIG_RSA_VERIFY_WITH_PKEY would be good enough for this purpose. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
In this patch, a very simple test is added to verify that rsa_verify() using rsa_verify_with_pkey() work correctly. To keep the code simple, all the test data, either public key and verified binary data, are embedded in the source. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
This function, and hence rsa_verify(), will perform RSA verification with two essential parameters for a RSA public key in contract of rsa_verify_with_keynode(), which requires additional three parameters stored in FIT image. It will be used in implementing UEFI secure boot, i.e. image authentication and variable authentication. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 AKASHI Takahiro 提交于
In the current implementation of FIT_SIGNATURE, five parameters for a RSA public key are required while only two of them are essential. (See rsa-mod-exp.h and uImage.FIT/signature.txt) This is a result of considering relatively limited computer power and resources on embedded systems, while such a assumption may not be quite practical for other use cases. In this patch, added is a function, rsa_gen_key_prop(), which will generate additional parameters for other uses, in particular UEFI secure boot, on the fly. Note: the current code uses some "big number" routines from BearSSL for the calculation. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>
-
由 AKASHI Takahiro 提交于
For FIT verification, all the properties of a public key come from "control fdt" pointed to by fdt_blob. In UEFI secure boot, on the other hand, a public key is located and retrieved from dedicated signature database stored as UEFI variables. Added two fields may hold values of a public key if fdt_blob is NULL, and will be used in rsa_verify_with_pkey() to verify a signature in UEFI sub-system. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 AKASHI Takahiro 提交于
In the next couple of commits, under new CONFIG_RSA_VERIFY_WITH_PKEY, rsa_verify() will be extended to be able to perform RSA decryption without additional RSA key properties from FIT image, i.e. rr and n0inv. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 AKASHI Takahiro 提交于
Introduce new configuration, CONFIG_RSA_VERIFY which will decouple building RSA functions from FIT verification and allow for adding a RSA-based signature verification for other file formats, in particular PE file for UEFI secure boot. Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Eugeniu Rosca 提交于
On Feb. 16, 2020, Tom reported [1] build failure of U-Boot in-tree tooling after applying https://patchwork.ozlabs.org/cover/1229663/ ("[v6,0/7] rsa: extend rsa_verify() for UEFI secure boot"). Later on, Heinrich stressed the urgency of the issue in https://patchwork.ozlabs.org/patch/1250858/#2379069: >>>>>>>>> We should finalize the topic as it stops EFI patches from being merged >>>>>>>>> On the surface, the problem is caused by U-Boot commits [2-3], which employed 'u32' in 'include/image.h', while historically U-Boot tooling stayed agnostic on the {u,s}{8,16,32} types. Thanks to Tom, Yamada-san and Heinrich, the following solutions have been put head-to-head ('+' pros, '-' cons): A. Use an equivalent fixed-size type, i.e. s/u32/uint32_t/ in both android function prototypes (image.h) and definitions (c file): + quick and low-line-count - creates a 'soup' of fixed-sized types in the Android C file - will confuse contributors - is going against Linux kernel best practices [4] B. Guard Android functions by '!defined(USE_HOSTCC)' in image.h: + quick and low-line-count + reflects the reality (no android function is used by tooling) + zero impact on other subsystems - ifdeffery may look annoying (pre-existing problem of image.h) C. Make {u8,u16,u32} available in U-Boot tooling: + quick and low-line-count + [Yamada-san][5]: * forbidding u32 for tools is questionable to me * Linux kernel and Barebox use {u8,u16,u32} for the tools space - breaks U-Boot tradition? - has larger impact than [A] and [B] - adds type complexity/inconsistency in the tooling space D. [Yamada-san] Refactor the headers to minimize the code shared between U-Boot space and tooling space: + probably the long-term solution - high effort - can be seen/done as an incremental update on top of [B] Looking at the above, [B] looks like the natural way to go forward. [1] https://patchwork.ozlabs.org/patch/1238245/#2363052 [2] commit 7f253150 ("image: android: Add routine to get dtbo params") [3] commit c3bfad82 ("image: android: Add functions for handling dtb field") [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e6176fa4728fb6d ("checkpatch: add --strict warning for c99 fixed size typedefs : int<size>_t") [5] https://patchwork.ozlabs.org/patch/1238245/#2363340 Cc: Masahiro Yamada <masahiroy@kernel.org> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de> Cc: Sam Protsenko <joe.skb7@gmail.com> Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Simon Glass <sjg@chromium.org> Cc: AKASHI Takahiro <takahiro.akashi@linaro.org> Reported-by: NTom Rini <trini@konsulko.com> Signed-off-by: NEugeniu Rosca <erosca@de.adit-jv.com> Tested-by: NHeinrich Schuchardt <xpyron.glpk@gmx.de>
-
- 11 3月, 2020 5 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-mmc由 Tom Rini 提交于
- DM support for CAxxxx SoCs - eMMC board for presidio-asic - Add defer probe for mmc sdhci - TI SoCs mmc misc update
-
由 Sam Shih 提交于
The binman-option BINMAN_FDT is introduced by this commit: commit 3c10dc95 ("binman: Add a library to access binman entries") BINMAN_FDT being selected when BINMAN=y that resulting in mt7623 and mt7622 are unable to boot. The root cause of this issue is commit: commit cbd2fba1 ("arm: MediaTek: add basic support for MT7629 boards") select BINMAN=y in all mediatek SoCs, and others mediatek SoCs not expect to use BINMAN_FDT. This patch remove BINMAN=y option when ARCH_MEDIATEK=y and move this to the specify SoCs part config. Signed-off-by: NSam Shih <sam.shih@mediatek.com> Tested-by: NFrank Wunderlich <frank-w@public-files.de>
-
由 Anatolij Gustschin 提交于
Currently when booting the kernel on i.MX8 U-Boot hangs in an endless loop when switching off dma, connectivity or lsio power domains during device removal. It hapens first when removing gpio0 (gpio@5d080000) device, here its power domain device 'lsio_gpio0' is obtained for switching off power. Since the obtained 'lsio_gpio0' device is removed afterwards, its power domain is also switched off and here the parent power domain device 'lsio_power_domain' is optained for switching off the power. Thereafter, when the obtained 'lsio_power_domain' is removed, device_remove() removes its first child 'lsio_gpio0'. During this child removal the 'lsio_power_domain' device is obtained again for switching and when removing it later, the same child removal is repeated, so we are stuck in an endless loop. Below is a snippet from dm tree on i.MX8QXP for better illustration of the DM devices relationship: Class Index Probed Driver Name ----------------------------------------------------------- root 0 [ + ] root_driver root_driver ... simple_bus 0 [ + ] generic_simple_bus |-- imx8qx-pm power_doma 0 [ + ] imx8_power_domain | |-- lsio_power_domain power_doma 1 [ + ] imx8_power_domain | | |-- lsio_gpio0 power_doma 2 [ + ] imx8_power_domain | | |-- lsio_gpio1 Do not remove a power domain device if it is a parent of the currently controlled device. Fixes: 52edfed6 ("dm: core: device: switch off power domain after device removal") Signed-off-by: NAnatolij Gustschin <agust@denx.de> Reported-by: NOliver Graute <oliver.graute@gmail.com> Reported-by: NFabio Estevam <festevam@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com> Tested-by: NFabio Estevam <festevam@gmail.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-imx由 Tom Rini 提交于
Fixes for 2020.04 ----------------- - DM : mx6sabresd - mx6ul_14x14_evk: fix video - mx8qxp; fix console for booting - sync DTS with kernel (imx6sx) - drop obsolete woodburn (mx35) Travis: https://travis-ci.org/sbabic/u-boot-imx/builds/660550811
-
https://gitlab.denx.de/u-boot/custodians/u-boot-atmel由 Tom Rini 提交于
First set of u-boot-atmel fixes for 2020.04 cycle: - Includes two small configuration fixes that will solve the SPL booting on sama5d3_xplained board.
-
- 10 3月, 2020 22 次提交
-
-
-
由 Pedro Jardim 提交于
This fixes the following warning: ===================== WARNING ====================== This board does not use CONFIG_DM_ETH (Driver Model for Ethernet drivers). Please update the board to use CONFIG_DM_ETH before the v2020.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/migration.rst for more info. ==================================================== Signed-off-by: NPedro Jardim <jardim.c.pedro@gmail.com> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-
由 Pedro Jardim 提交于
This fixes the following warning: ===================== WARNING ====================== This board does not use CONFIG_DM_ETH (Driver Model for Ethernet drivers). Please update the board to use CONFIG_DM_ETH before the v2020.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/migration.rst for more info. ==================================================== Signed-off-by: NPedro Jardim <jardim.c.pedro@gmail.com> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-
由 Fabio Estevam 提交于
Booting a mainline kernel in secure mode on i.MX7D causes only one CPU to be brought up. Change it to booting in non secure mode by default, which allows the two CPUs to be brought up. It does have a side effect of not probing the CAAM driver. If CAAM driver is needed then a secure world OS such as OPTEE needs to be used. Signed-off-by: NFabio Estevam <festevam@gmail.com>
-
由 Oliver Graute 提交于
Set CONFIG_SYS_BOOTMAPSZ to the amount of memory available which is needed to relocate the kernel, device tree and initrd. Remove 'fdt_high' and 'initrd_high' environment variables from default environment which prevents relocation of FDT and initrd. Signed-off-by: NOliver Graute <oliver.graute@kococonnector.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <festevam@gmail.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Simon Glass <sjg@chromium.org> Cc: Ye Li <ye.li@nxp.com> Cc: uboot-imx <uboot-imx@nxp.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Alifer Moraes 提交于
Instead of resetting the ethernet phy through functions in imx8mq_evk.c, let the driver reset the phy via dts description adding a reset duration of 10 ms following atheros 8031's datasheet recommendation. Signed-off-by: NAlifer Moraes <alifer.wsdm@gmail.com>
-
由 Alifer Moraes 提交于
Convert imx6sabresd ethernet to driver model to fix the following warning: ===================== WARNING ====================== This board does not use CONFIG_DM_ETH (Driver Model for Ethernet drivers). Please update the board to use CONFIG_DM_ETH before the v2020.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/migration.rst for more info. ==================================================== Signed-off-by: NAlifer Moraes <alifer.wsdm@gmail.com> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-
由 Fabien Lehoussel 提交于
Uboot size is incorrect. Uboot SPL use CONFIG_SYS_MONITOR_LEN to read uboot from NAND : 0x80000 With sama5d3_xplained_nandflash_defconfig : u-boot.bin size is ~800Ko 0xC0000 So I increased size to 1MB : 0x100000 Signed-off-by: NFabien Lehoussel <fabien.lehoussel@medianesysteme.com>
-
由 Fabien Lehoussel 提交于
SPL boot cannot find dtb if CONFIG_SPL_SEPARATE_BSS is disabled : CONFIG_SPL_SEPARATE_BSS=n RomBOOT <debug_uart> Missing DTB ### ERROR ### Please RESET the board ### RomBOOT CONFIG_SPL_SEPARATE_BSS=y RomBOOT <debug_uart> U-Boot SPL 2019.04-linux4sam_6.2-icp-dirty (Feb 24 2020 - 15:34:35 +0100) Trying to boot from NAND <debug_uart> Signed-off-by: NFabien Lehoussel <fabien.lehoussel@medianesysteme.com>
-
由 Clemens Gruber 提交于
The PHY models of the Marvell 88E151x series are not reliably distinguishable by their uid / PHY identifiers. The 88E1510, 88E1512, 88E1514 and 88E1518 all have the same OUI and model number and bits 3:0 in the PHY Identifier 2 (Page 0, Reg 3) are described as HW revision number, but both 88E1510 and 88E1518 PHYs were observed with the same HW rev number (1). Before commit 83cfbeb0 ("net: phy: Fix mask so that we can identify Marvell 88E1518"), the 88E151x were detected because the HW revision bits were masked from the uid. After that change, 88E1510/12/18 were all detected as 88E1518 and the 88E1510 specific code was no longer run. I modified the mask to again ignore all four HW revision bits, removed the 88E1510 specific code (board-specific LED/INTn setup), which was not called since late 2016 anyway and renamed the config function and phy_driver struct to the better fitting 88e151x. The uid and mask bits 3:0 are now again the same as in the Linux kernel. Signed-off-by: NClemens Gruber <clemens.gruber@pqgruber.com>
-
由 Heinrich Schuchardt 提交于
When printing unsigned numbers use %u. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Michal Simek 提交于
This patch adds ability to switch beetween two PHY SGMII modes. Some hardware, for example, FPGA IP designs may use 6-wire mode which enables differential SGMII clock to MAC. Patch description, dt flags have been done in mainline Linux by commit a2111c460c0c ("net: phy: dp83867: Add documentation for SGMII mode type") and by commit 507ddd5c0d47 ("net: phy: dp83867: Add SGMII mode type switching") Signed-off-by: NMichal Simek <michal.simek@xilinx.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Michal Simek 提交于
U-Boot is having DT which doesn't cover all options currently supported by driver. DT binding is aligned with Linux kernel version available here. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/net/ti,dp83867.txt Based on my talk with Grygorii Strashko better will be to remove it. Also Linux kernel bindings are being converted to yaml that's another reason to do it only at one place. Signed-off-by: NMichal Simek <michal.simek@xilinx.com> Reviewed-by: NGrygorii Strashko <grygorii.strashko@ti.com>
-
由 Alex Marginean 提交于
The helper is used to reset PHYs on connect and it determines the clause to use (C22/C45) based on interface type. This fixes 'PHY reset timed out' warnings in console for USXGMII/XFI PHYs. Signed-off-by: NAlex Marginean <alexandru.marginean@nxp.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Andre Przywara 提交于
Commit 27c3f70f ("net: phy: Increase link up delay in genphy_update_link()") increased the per-iteration waiting time from 1ms to 50ms, without adjusting the timeout counter. This lead to the timeout increasing from the typical 4 seconds to over three minutes. Adjust the timeout counter evaluation by that factor of 50 to bring the timeout back to the intended value. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Fixes: net: phy: Increase link up delay in genphy_update_link() ("27c3f70f") Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NMatthias Brugger <mbrugger@suse.com> Tested-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Andre Przywara 提交于
doc/README.drivers.eth seems like a good source for understanding U-Boot's network subsystem, but is only talking about legacy network drivers. This is particularly sad as proper documentation would help in porting drivers over to the driver model. Rewrite the document to describe network drivers in the new driver model world. Most driver callbacks/methods are almost identical in their semantic, but recv() differs in some important details. Also keep some parts of the original text at the end, to help understanding old drivers. Add some hints on how to port drivers over. This also uses the opportunity to reformat the document in reST, on the way moving it into doc/driver-model and adding it into the structure there. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Alex Marginean 提交于
The driver now unconditionally prints some information that's not universally useful. Replace printf with debug. Signed-off-by: NAlex Marginean <alexandru.marginean@nxp.com> Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Alex Marginean 提交于
Use either USXGMII or XFI in aquantia_set_proto and drop XGMII as a valid protocol configuration. The PHY doesn't support it, it's just used as an alias for one of the other two protocols. Signed-off-by: NFlorin Chiculita <florinlaurentiu.chiculita@nxp.com> Signed-off-by: NAlex Marginean <alexandru.marginean@nxp.com> Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Pankit Garg 提交于
Make sure the gd struct is up-to-date. Signed-off-by: NPankit Garg <pankit.garg@nxp.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Samuel Mendoza-Jonas 提交于
Add NC-SI to the usual phy handling. This makes two notable changes: - Somewhat similar to a fixed phy, phy_connect() will create an NC-SI phy if CONFIG_PHY_NCSI is defined. - An early return is added to phy_read() and phy_write() to handle a case like the NC-SI phy which does not define a bus. Signed-off-by: NSamuel Mendoza-Jonas <sam@mendozajonas.com> Reviewed-by: NJoel Stanley <joel@jms.id.au> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Samuel Mendoza-Jonas 提交于
This introduces support for the NC-SI protocol, modelled as a phy driver for other ethernet drivers to consume. NC-SI (Network Controller Sideband Interface) is a protocol to manage a sideband connection to a proper network interface, for example a BMC (Baseboard Management Controller) sharing the NIC of the host system. Probing and configuration occurs by communicating with the "remote" NIC via NC-SI control frames (Ethernet header 0x88f8). This implementation is roughly based on the upstream Linux implementation[0], with a reduced feature set and an emphasis on getting a link up as fast as possible rather than probing the full possible topology of the bus. The current phy model relies on the network being "up", sending NC-SI command frames via net_send_packet() and receiving them from the net_loop() loop (added in a following patch). The ncsi-pkt.h header[1] is copied from the Linux kernel for consistent field definitions. [0]: https://github.com/torvalds/linux/tree/master/net/ncsi [1]: https://github.com/torvalds/linux/blob/master/net/ncsi/ncsi-pkt.hSigned-off-by: NSamuel Mendoza-Jonas <sam@mendozajonas.com> Reviewed-by: NJoel Stanley <joel@jms.id.au> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Tom Rini 提交于
We keep both of these jobs in sync as much as possible even when the primary motivation is to keep Travis from exceeding the build time limit there. With that in mind: - Use "rk" not "rockchip" to get all Rockchip SoC platforms in one job, rather than just all Rockchip vendor platforms. - The NXP LX216* SoCs have their own job, exclude them from the AArch64 generic job. - SoCFPGA SoCs have their own job, exclude them from the AArch64 generic job. Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 09 3月, 2020 5 次提交
-
-
由 Oliver Graute 提交于
Added missing USDHC Base address defines Signed-off-by: NOliver Graute <oliver.graute@kococonnector.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <festevam@gmail.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Simon Glass <sjg@chromium.org> Cc: Ye Li <ye.li@nxp.com> Cc: uboot-imx <uboot-imx@nxp.com> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-
由 Max Krummenacher 提交于
The FEC in the i.MX8MM doesn't support this feature. So don't pretend one can use it. Signed-off-by: NMax Krummenacher <max.krummenacher@toradex.com> Signed-off-by: NIgor Opaniuk <igor.opaniuk@toradex.com> Acked-by: NPeng Fan <peng.fan@nxp.com> Reviewed-by: NOleksandr Suvorov <oleksandr.suvorov@toradex.com>
-
由 Igor Opaniuk 提交于
Let pinctrl configuration for eMMC node (usdhc1) also be accessible in SPL. Signed-off-by: NIgor Opaniuk <igor.opaniuk@toradex.com> Reviewed-by: NPeng Fan <peng.fan@nxp.com> Reviewed-by: NOleksandr Suvorov <oleksandr.suvorov@toradex.com>
-
由 Giulio Benetti 提交于
Some device may enable CONFIG_CLK but not still support this clock in CC, so better use debug() in place of dev_warn() otherwise a lot of boards will throw useless dev_warn()s. Signed-off-by: NGiulio Benetti <giulio.benetti@benettiengineering.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Frieder Schrempf 提交于
The current implementation in arch/arm/mach-imx/cpu.c uses non-DM code to retrieve the core clock frequency. As the root clock is not listed we currently get: CPU: Freescale i.MX8MMQ rev1.0 at 0 MHz Fix this by adding the missing entry, which results in: CPU: Freescale i.MX8MMQ rev1.0 at 1200 MHz Signed-off-by: NFrieder Schrempf <frieder.schrempf@kontron.de> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-