Signed-off-by: Andrew F. Davis
---
doc/README.ti-secure | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/doc/README.ti-secure b/doc/README.ti-secure
index 76950253ac..27c0eaa77f 100644
--- a/doc/README.ti-secure
+++ b/doc/README.ti-secure
@@ -138,7 +138,7
Add new defconfig files for the AM65x High Security EVM.
This defconfigs are the same as for the non-secure part, except for:
CONFIG_TI_SECURE_DEVICE option set to 'y'
CONFIG_FIT_IMAGE_POST_PROCESS option set to 'y'
CONFIG_SPL_FIT_IMAGE_POST_PROCESS option set to 'y'
Signed-off-by:
K3 devices have High Security (HS) variants along with the non-HS already
supported. Like the previous generation devices (OMAP/Keystone2) K3
supports boot chain-of-trust by authenticating and optionally decrypting
images as they are unpacked from FIT images. Add support for this here.
On HS devices the 512b region of reset isolated memory called
MCU_PSRAM0 is firewalled by default. Until SYSFW is loaded we
cannot use this memory. It is only used to store a single value
left at the end of SRAM by ROM that will be needed later. Save
that value to a global variable stored in the
K3 HS devices require signed binaries for boot, use the SECDEV tools
to sign the boot artifacts during build.
Signed-off-by: Andrew F. Davis
---
MAINTAINERS | 1 +
arch/arm/mach-k3/config.mk| 25 ++
arch/arm/mach-k3/config_secure.mk | 44
SYSFW version 2019.01 introduces a slightly modified version of this API,
add support for it here.
Signed-off-by: Andrew F. Davis
---
drivers/firmware/ti_sci.c | 25 -
drivers/firmware/ti_sci.h | 9 +++--
TI-SCI message protocol provides support for controlling the firewall
configurations available in SoC.
Introduce support for the set of TI-SCI message protocol APIs that
provide us with this capability of controlling firewalls.
Signed-off-by: Andrew F. Davis
---
drivers/firmware/ti_sci.c
Hello all,
This series brings up HS device support on the AM65x platform. Support
for HS on K3 family devices is a bit different than previous devices
but for the most part all that has been abstracted into the SECDEV
package, allowing for a rather straight forward implementation here.
Thanks,
On 09/02/2019 14:01, Fabio Estevam wrote:
After the conversion to DM the U-Boot binary is called u-boot-dtb.imx,
so fix the README file accordingly.
Signed-off-by: Fabio Estevam
oops send RB from wrong address - one more time
Reviewed-by: Bryan O'Donoghue
On 09/02/2019 14:01, Fabio Estevam wrote:
After the conversion to DM the U-Boot binary is called u-boot-dtb.imx,
so fix the README file accordingly.
Signed-off-by: Fabio Estevam
Reviewed-by: Bryan O'Donoghue
___
U-Boot mailing list
From: Ondrej Jirman
Fix typo in axp_set_dldo() so that it correctly uses AXP818_DLDO1_CTRL
register to configure the voltage instead of setting AXP818_ELDO1_CTRL
register which is obviously incorrect.
Signed-off-by: Ondřej Jirman
---
This was previously sent as a part of other series of
From: Ondrej Jirman
Length may be unitialized when fdt_getprop fails. Return ENOENT when
the property can't be found.
Signed-off-by: Ondřej Jirman
---
This was previously sent as a part of other series of patches, but
it's unrelated to the rest of the patches, so I'm resending it
individually.
From: Ondrej Jirman
Fixes a compilation failure with disabled PXE or DHCP command when using
sunxi platform.
Signed-off-by: Ondřej Jirman
---
This was previously sent as a part of other series of patches, but
it's unrelated to the rest of the patches, so I'm resending it
individually.
v2:
-
I'm having trouble getting verified boot working in SPL on an am3358 based
platform.
The problem I hit is when fit_image_verify_with_data()
calls fit_image_verify_required_sigs(). The 5th argument (sig_blob) is
gd_fdt_blob() which resolves to NULL. This argument should be the FDT
containing the
Hi Vagrant,
Thanks for the report.
Adding Jon and Baruch on Cc in case they could take a look at it.
On Wed, Feb 13, 2019 at 2:52 PM Vagrant Cascadian wrote:
>
> I *think* this board is getting the wrong fdtfile set:
>
> U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +)
>
> CPU: Freescale
On Sat, Feb 9, 2019 at 7:59 PM wrote:
>
Add commit message, it look some fix of using DLDO1 instead of ELDO1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On Sat, Feb 9, 2019 at 7:14 PM wrote:
>
> From: Ondrej Jirman
>
Commit message please.
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
The ADC block requires VDD supply to be on so provide one.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/dts/exynos5422-odroidxu3.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/exynos5422-odroidxu3.dts
b/arch/arm/dts/exynos5422-odroidxu3.dts
index
Add startup time to LDO regulators of S2MPS11 PMIC on Odroid XU3/XU4/HC1
family of boards to be sure the voltage is proper before relying on the
regulator.
The datasheet for all the S2MPS1x family is inconsistent here and does
not specify unambiguously the value of ramp delay for LDO. It
According to datasheet, the output on LDO regulators will start
appearing after 10-15 us.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/regulator/s2mps11_regulator.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/power/regulator/s2mps11_regulator.c
I *think* this board is getting the wrong fdtfile set:
U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +)
CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 37C
Reset cause: WDOG
Board: MX6 Cubox-i
DRAM: 3.8 GiB
MMC:
Changing voltage and enabling regulator might require delays so the
regulator stabilizes at expected level.
Add support for "regulator-ramp-delay" binding which can introduce
required time to both enabling the regulator and to changing the
voltage.
Signed-off-by: Krzysztof Kozlowski
---
From: Krzysztof Kozlowski
Printing the "Type" of board requires proper detection of revision which
can happen only late because regulators are needed.
Signed-off-by: Krzysztof Kozlowski
---
board/samsung/common/board.c | 2 +-
configs/odroid-xu3_defconfig | 2 ++
2 files changed, 3
Fix detection of Odroid HC1 (Exynos5422) after reboot if kernel disabled
the LDO4/VDD_ADC regulator.
The LDO4 supplies both ADC block and the ADC input AIN9. Voltage on
AIN9 will rise slowly, so be patient and wait for it to stabilize.
First reads on Odroid HC1 return 305, 1207, 1297 and
Detection of board revision is done early - before power setup. In case of
Odroid XU3/XU4/HC1 family, the detection is done using ADC which
is supplied by LDO4/VDD_ADC regulator. This regulator could be turned
off (e.g. by kernel before reboot). If ADC is used early, the
regulators are not yet
LDO27 and LDO35 have 25 mV step, not 50 mV.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/regulator/s2mps11_regulator.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/power/regulator/s2mps11_regulator.c
b/drivers/power/regulator/s2mps11_regulator.c
index
Hi,
Changes since v1
1. Move fixes to beginning of patchset.
2. Patch 3: Rework the idea - split revision detection to be executed later.
3. Patch 4: New patch.
4. Patch 6: Apply Simon's comments.
5. Patch 6: Do not delay when changing voltage if regulator is disabled.
6. Patch
When stopping the ADC_V2_CON1_STC_EN should be cleared.
Signed-off-by: Krzysztof Kozlowski
---
drivers/adc/exynos-adc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/adc/exynos-adc.c b/drivers/adc/exynos-adc.c
index d33e3d632afc..12c49fc8cefb 100644
---
From: Shubhrajyoti Datta
Fix the below warning as the core looks for the compatible
string.
[5.198919] i2c i2c-18: of_i2c: modalias failure on
/amba/i2c@ff03/i2c-mux@75/i2c@3/dev@19
[5.207454] i2c i2c-18: Failed to create I2C device for
/amba/i2c@ff03/i2c-mux@75/i2c@3/dev@19
[
From: Amit Kucheria
The idle-states binding documentation[1] mentions that the
'entry-method' property is required on 64-bit platforms and must be
set to "psci".
Linux commit a13f18f59d26 ("Documentation: arm: Fix typo in the idle-states
bindings examples") attempted to fix this earlier but
From: Venkatesh Yadav Abbarapu
As per the zc1275 design x1 mode is enabled so changing the
spi-rx-bus-width property to x1.
Signed-off-by: Venkatesh Yadav Abbarapu
Signed-off-by: Michal Simek
---
arch/arm/dts/zynqmp-zc1275-revB.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Trivial fix.
Signed-off-by: Michal Simek
---
arch/arm/dts/zynq-zc770-xm010.dts | 1 -
arch/arm/dts/zynqmp-zcu100-revC.dts | 1 -
arch/arm/dts/zynqmp-zcu102-revA.dts | 1 -
3 files changed, 3 deletions(-)
diff --git a/arch/arm/dts/zynq-zc770-xm010.dts
b/arch/arm/dts/zynq-zc770-xm010.dts
From: Mounika Grace Akula
This patch adds reset-on-timeout to FPD WDT which will trigger an
interrupt to PMU when watchdog expiry happens and PMU takes the
necessary action. If this property is not enabled, reason will not be
known when watchdog expiry happens.
This patch also modifies the
It will never reach mainline that's why remove it.
Signed-off-by: Michal Simek
---
arch/arm/dts/zynqmp-zcu106-revA.dts | 20
arch/arm/dts/zynqmp-zcu111-revA.dts | 20
2 files changed, 40 deletions(-)
diff --git a/arch/arm/dts/zynqmp-zcu106-revA.dts
From: Luis Araneda
Replace the current value of the model property by a more accurate
description of each board (which includes the manufacturer), as some
of the boards had the same value ("Xilinx Zynq")
Signed-off-by: Luis Araneda
Signed-off-by: Michal Simek
---
arch/arm/dts/zynq-cc108.dts
From: Luis Araneda
Both boards are made by Avnet, Inc. So add an additional
value to the compatible property
Signed-off-by: Luis Araneda
Signed-off-by: Michal Simek
---
arch/arm/dts/zynq-microzed.dts | 2 +-
arch/arm/dts/zynq-zed.dts | 2 +-
2 files changed, 2 insertions(+), 2
mmc name is recommended based on devicetree specification.
Signed-off-by: Michal Simek
---
arch/arm/dts/zynq-7000.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/dts/zynq-7000.dtsi b/arch/arm/dts/zynq-7000.dtsi
index 286059d56e61..e1b0816a3459 100644
---
Hi,
just put together some DT changes and send me all. Most of these patches
are coming from Linux kernel.
Thanks,
Michal
Amit Kucheria (1):
arm64: dts: Fix various entry-method properties to reflect
documentation
Luis Araneda (2):
ARM: dts: zynq: Set correct manufacturer for ZedBoard
On Wed, Feb 13, 2019 at 09:50:44AM +0100, Michael Nazzareno Trimarchi wrote:
> Hi Maxime
>
> On Wed, Feb 13, 2019 at 9:45 AM Maxime Ripard
> wrote:
> >
> > On Tue, Feb 12, 2019 at 05:57:08PM +0100, Michael Trimarchi wrote:
> > > Set two rank timing and exit self-refresh timing seems not done
>
Hi Simon,
Seems that there is an issue in dm test framework (if understood
everything correctly),
I've noticed that dm_root is updated when dm tests are being invoked,
and that's why the new tee udevice is allocated, consequently, the
second invocation of probe in tee driver occurs.
In
On Wed, Feb 13, 2019 at 08:12:44PM +0530, Jagan Teki wrote:
> On Fri, Jan 25, 2019 at 4:09 PM Chen-Yu Tsai wrote:
> >
> > The brand Sinovoip is used for Sinovoip's original VOIP products, while
> > the Bananapi brand is for the single board computers they produce. This
> > has been verified by
Hi Marcel,
> Hi Lukasz
>
> On Sun, 2019-02-03 at 00:02 +0100, Lukasz Majewski wrote:
> > The "m4go" provides exactly the same functionality as the IMX
> > generic "bootaux" command. Remove it to not duplicate the code.
>
> Makes sense but as far as I can tell from its Kconfig so far bootaux
>
Hi Lukasz
On Sun, 2019-02-03 at 00:02 +0100, Lukasz Majewski wrote:
> The "m4go" provides exactly the same functionality as the IMX generic
> "bootaux" command. Remove it to not duplicate the code.
Makes sense but as far as I can tell from its Kconfig so far bootaux is
only for i.MX 7 and i.MX
On Fri, Jan 25, 2019 at 4:09 PM Chen-Yu Tsai wrote:
>
> The brand Sinovoip is used for Sinovoip's original VOIP products, while
> the Bananapi brand is for the single board computers they produce. This
> has been verified by Bananapi. Rename the board from "Sinovoip BPI M2
> Plus" to "Bananapi M2
From: Tien Fong Chee
Update the default configuration file to enable the necessary functionality
to get the SoCFPGA loadfs driver support. This would enable the
implementation of programming bitstream into FPGA from MMC.
Signed-off-by: Tien Fong Chee
---
changes for v8
- Added FIT related
From: Tien Fong Chee
After some series of patches to maximise reusable of memory pool, here come
to result of reasonable size required for whole SDMMC boot working on A10
SoCDK. Size required come from default max cluster(0x1) +
others(0x2000) + additional memory for headroom(0x3000).
From: Tien Fong Chee
Add support for loading FPGA bitstream to get DDR up running before
U-Boot is loaded into DDR. Boot device initialization, generic firmware
loader and SPL FAT support are required for this whole mechanism to work.
Signed-off-by: Tien Fong Chee
---
changes for v7
-
From: Tien Fong Chee
Update the default configuration file to enable the necessary functionality
the get the kit working.
Signed-off-by: Tien Fong Chee
---
changes for v8
- Moved the FIT related configs to the patch of configuration for FPGA
SoCFPGA A10 SoCDK.
changes for v7
- Keep
From: Tien Fong Chee
Add FPGA driver to support program FPGA with FPGA bitstream loading from
filesystem. The driver are designed based on generic firmware loader
framework. The driver can handle FPGA program operation from loading FPGA
bitstream in flash to memory and then to program FPGA.
From: Tien Fong Chee
Adding some function declarations to the header file, so these
functions can be referred by other C files.
Signed-off-by: Tien Fong Chee
---
include/image.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/image.h b/include/image.h
index 83a2d41..f839443
From: Tien Fong Chee
This patch adds description on properties about file name used for both
peripheral bitstream and core bitstream.
Signed-off-by: Tien Fong Chee
---
changes for v8
- Removed explanation about support for altr,bitstream-core
changes for v7
- Provided example of setting
From: Tien Fong Chee
Add default fitImage file bundling FPGA bitstreams for Arria10.
Signed-off-by: Tien Fong Chee
---
changes for v8
- Changed the FPGA node name to fpga-core and fpga-periph for both core and
periph bitstreams respectively.
---
board/altera/arria10-socdk/fit_spl_fpga.its
From: Tien Fong Chee
This version mainly resolved comments from Marek and Dalon L Westergreen in
[v7].
Additonal note:
---
There are a few solutions at this moment for solving the performance issue
1. Using absolute data position to allign the core bistream in fitImage.
2. SPL
[PM]
Hi Vignesh,
On Fri, 8 Feb 2019 18:36:05 +0530
Vignesh R wrote:
> On 07/02/19 6:13 PM, Jagan Teki wrote:
> > On Tue, Feb 5, 2019 at 11:29 AM Vignesh R wrote:
> [...]
> >>
> >> Vignesh R (20):
> >> configs: Move CONFIG_SPI_FLASH into defconfigs
> >> bitops: Fix GENMASK definition for
On Wed, 13 Feb 2019 14:42:57 +0100
Boris Brezillon wrote:
> [PM]
Not so private actually :D.
> Hi Vignesh,
>
> On Fri, 8 Feb 2019 18:36:05 +0530
> Vignesh R wrote:
>
> > On 07/02/19 6:13 PM, Jagan Teki wrote:
> > > On Tue, Feb 5, 2019 at 11:29 AM Vignesh R wrote:
> > [...]
> > >>
>
On Wed, 13 Feb 2019 at 12:47, Tom Rini wrote:
>
> On Wed, Feb 13, 2019 at 12:31:49PM +, Neil Williams wrote:
> > On Wed, 13 Feb 2019 at 12:24, Tom Rini wrote:
> > >
> > > On Wed, Feb 13, 2019 at 02:28:54PM +0530, Manivannan Sadhasivam wrote:
> > >
> > > > Current Hikey configuration allows
On Wed, 13 Feb 2019 at 12:24, Tom Rini wrote:
>
> On Wed, Feb 13, 2019 at 02:28:54PM +0530, Manivannan Sadhasivam wrote:
>
> > Current Hikey configuration allows us to store u-boot environment on uSD
> > card. But this will be useless if uSD card is not inserted, hence use
> > the onboard eMMC
On Wed, Feb 13, 2019 at 02:16:12PM +0100, Heinrich Schuchardt wrote:
>
>
> On 2/13/19 1:25 PM, Tom Rini wrote:
> > On Wed, Feb 13, 2019 at 11:13:19AM +0100, Philipp Tomsich wrote:
> >>
> >>
> >>> On 13.02.2019, at 11:10, David Wu wrote:
> >>>
> >>> Hi Philipp,
> >>>
> >>> 在 2019/2/12 下午9:54,
All options have been moved to Kconfig and there is no need to have
board header files. Mini configurations require them that's why they are
still there.
Signed-off-by: Michal Simek
---
configs/avnet_ultra96_rev1_defconfig | 1 -
configs/xilinx_zynqmp_zc1275_revB_defconfig |
SPD autodetection hasn't been enabled that's why there is zero size
difference if that options are enabled/disabled.
Signed-off-by: Michal Simek
---
include/configs/xilinx_zynqmp_zcu102.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/configs/xilinx_zynqmp_zcu102.h
Replace SDHCI controller listing by Kconfig symbol to let SPL know that
this board is using multiple SDHCIs controllers.
Kconfig help message should explain why this is needed.
Origin symbols were used in full u-boot but with moving to distro boot
this was fixed already.
Signed-off-by: Michal
On 2/13/19 1:25 PM, Tom Rini wrote:
> On Wed, Feb 13, 2019 at 11:13:19AM +0100, Philipp Tomsich wrote:
>>
>>
>>> On 13.02.2019, at 11:10, David Wu wrote:
>>>
>>> Hi Philipp,
>>>
>>> 在 2019/2/12 下午9:54, Philipp Tomsich 写道:
> On 12.02.2019, at 13:38, David Wu wrote:
>
> Hi Philipp,
On Wed, Feb 13, 2019 at 01:02:48PM +, Neil Williams wrote:
> On Wed, 13 Feb 2019 at 12:47, Tom Rini wrote:
> >
> > On Wed, Feb 13, 2019 at 12:31:49PM +, Neil Williams wrote:
> > > On Wed, 13 Feb 2019 at 12:24, Tom Rini wrote:
> > > >
> > > > On Wed, Feb 13, 2019 at 02:28:54PM +0530,
Hi,
anyone ?
On 2019-02-10 19:15, Joan Moreau wrote:
Hi,
I am trying to get a uboot image for a AP143 reference board (Mips)
The "make" gives the error below
Can you help ?
Thank you
[root/ u-boot]# make menuconfig
scripts/kconfig/mconf Kconfig
configuration written to
On Wed, Feb 13, 2019 at 12:31:49PM +, Neil Williams wrote:
> On Wed, 13 Feb 2019 at 12:24, Tom Rini wrote:
> >
> > On Wed, Feb 13, 2019 at 02:28:54PM +0530, Manivannan Sadhasivam wrote:
> >
> > > Current Hikey configuration allows us to store u-boot environment on uSD
> > > card. But this
On 2/13/19 1:15 PM, Chee, Tien Fong wrote:
> On Wed, 2019-02-13 at 13:00 +0100, Marek Vasut wrote:
>> On 2/13/19 9:22 AM, Chee, Tien Fong wrote:
>>>
>>> On Fri, 2019-02-01 at 09:29 +0100, Marek Vasut wrote:
On 2/1/19 5:04 AM, Chee, Tien Fong wrote:
>
>
> On Thu, 2019-01-31 at
From: Tien Fong Chee
This would print out all the FPGA node names setting to fpga property.
Signed-off-by: Tien Fong Chee
---
common/image-fit.c | 14 +++---
1 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/common/image-fit.c b/common/image-fit.c
index
On Wed, Feb 13, 2019 at 11:13:19AM +0100, Philipp Tomsich wrote:
>
>
> > On 13.02.2019, at 11:10, David Wu wrote:
> >
> > Hi Philipp,
> >
> > 在 2019/2/12 下午9:54, Philipp Tomsich 写道:
> >>> On 12.02.2019, at 13:38, David Wu wrote:
> >>>
> >>> Hi Philipp,
> >>>
> >>> 在 2019/2/10 上午2:24,
On Wed, Feb 13, 2019 at 02:28:54PM +0530, Manivannan Sadhasivam wrote:
> Current Hikey configuration allows us to store u-boot environment on uSD
> card. But this will be useless if uSD card is not inserted, hence use
> the onboard eMMC memory for storing environment at Boot1 partition.
> While
On Wed, Feb 13, 2019 at 6:51 AM André Przywara wrote:
>
> On 09/02/2019 13:14, Jagan Teki wrote:
> > Add A31 spi controller support for existing sun4i_spi driver via driver
> > data, this would simply add A31 register along with proper register bits
> > via enum sets.
> >
> > Signed-off-by: Jagan
On Wed, 2019-02-13 at 13:00 +0100, Marek Vasut wrote:
> On 2/13/19 9:22 AM, Chee, Tien Fong wrote:
> >
> > On Fri, 2019-02-01 at 09:29 +0100, Marek Vasut wrote:
> > >
> > > On 2/1/19 5:04 AM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Thu, 2019-01-31 at 15:55 +0100, Marek Vasut wrote:
>
Hi Maxime
On Wed, Feb 13, 2019 at 9:44 AM Maxime Ripard wrote:
>
> On Tue, Feb 12, 2019 at 05:57:07PM +0100, Michael Trimarchi wrote:
> > Change the size create a glitch in the clke signal on second
> > bank.
>
> Which glitch?
>
> > The glitch can generate problem in memory initialiazation
>
>
On 2/13/19 9:22 AM, Chee, Tien Fong wrote:
> On Fri, 2019-02-01 at 09:29 +0100, Marek Vasut wrote:
>> On 2/1/19 5:04 AM, Chee, Tien Fong wrote:
>>>
>>> On Thu, 2019-01-31 at 15:55 +0100, Marek Vasut wrote:
On 1/31/19 3:51 PM, tien.fong.c...@intel.com wrote:
>
>
> From: Tien
Hi Joe,
Thanks for spending time to review the patch.
On Mon, Feb 04, 2019 at 11:48:40PM +, Joe Hershberger wrote:
> On Mon, Jan 28, 2019 at 3:16 AM Shawn Guo wrote:
> >
> > It adds the driver for HIGMACV300 Ethernet controller found on HiSilicon
> > SoCs like Hi3798CV200. It's based on a
On Wed, Feb 13, 2019 at 6:51 AM André Przywara wrote:
>
> On 09/02/2019 13:14, Jagan Teki wrote:
> > Add CLK support to enable AHB and MOD SPI clocks on sun4i_spi driver.
> >
> > Note, that the code will enable and disable clock in claim and release
> > calls to make proper clock and reset
On 22/01/2019 02:12, Simon Glass wrote:
At present this uclass is selected only on x86. In order to add a test for
it, it must also support sandbox. Create a new CONFIG_PCH option and
enable it on x86 and sandbox.
Signed-off-by: Simon Glass
---
arch/Kconfig| 2 ++
drivers/Kconfig
The command line is:
ln target linkname
Currently symbolic links are supported only in ext4 and only if the option
CMD_EXT4_WRITE is enabled.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
Test cases are:
1) basic link creation, verify it can be followed
2) chained links, verify it can be followed
3) replace exiting file a with a link, and a link with a link. verify it
can be followed
4) create a broken link, verify it can't be followed
Signed-off-by: Jean-Jacques Hiblot
This series adds support for the creation of symbolic links on ext4
file-systems.
The motivation behind this work is to have the ability to "do" the job
of update-alternatives in u-boot.
Firmware on TI's platform are usually managed with update-alternatives and
are thus targeted by a symbolic
If the metadata checksums are enabled, all write operations will fail.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
test/py/tests/test_fs/conftest.py | 2 ++
1 file changed, 2 insertions(+)
diff
There is no need to modify the buffer passed to ext4fs_write_file().
The memset() call is not required here and was likely copied from the
equivalent part of the ext4fs_read_file() function where we do need it.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
executes the appropriate fsck tool. It should be called at the end of any
test that modify the
Re-use the functions used to write/create a file, to support creation of a
symbolic link.
The difference with a regular file are small:
- The inode mode is flagged with S_IFLNK instead of S_IFREG
- The ext2_dirent's filetype is FILETYPE_SYMLINK instead of FILETYPE_REG
- Instead of storing the
u-boot does not supports updating the metadata chacksums
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2:
- Prevent write access if metadata checksum is enabled
fs/ext4/ext4_write.c | 12 ++--
Hi Maxime
On Wed, Feb 13, 2019 at 9:49 AM Michael Nazzareno Trimarchi
wrote:
>
> Hi Maxime
>
> On Wed, Feb 13, 2019 at 9:44 AM Maxime Ripard
> wrote:
> >
> > On Tue, Feb 12, 2019 at 05:57:07PM +0100, Michael Trimarchi wrote:
> > > Change the size create a glitch in the clke signal on second
>
From: Christophe Kerello
On response type r1b, if DTIME is not defined or too short,
the Datatimeout and DPSM flag occurs. Like the DPSM is
activated all next data transfer will be frozen.
To avoid this freeze:
-The driver must define a DTIME on all r1b response type.
-DTIME of SDMMC
Update some sdmmc properties which have been updated with
v4.19 DT bindings:
- st,dirpol becomes st,sig-dir
- st,negedge becomes st,neg-edge
- st,pin-ckin becomes st,use-ckin
Signed-off-by: Patrice Chotard
---
Changes in v2: None
arch/arm/dts/stm32mp157c-ed1.dts | 10
This series:
- Update stm32_sdmmc2 driver to be synced with v4.19 kernel DT bindings.
- Fix r1b timeout issue for stm32_sdmmc2 driver.
- Update stm32h743i-eval and stm32mp157c-ed1 DT to be synced with new
sdmmc DT bindings.
Changes in v2:
- Remove a "Reviewed-by: CITOOLS ..."
From: Patrick Delaunay
Some properties name has been updated:
- st,dirpol becomes st,sig-dir
- st,negedge becomes st,neg-edge
- st,pin-ckin becomes st,use-ckin
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
Changes in v2:
- Remove a "Reviewed-by: CITOOLS ..."
From: Patrick Delaunay
Update some sdmmc properties which have been updated with
v4.19 DT bindings:
- st,dirpol becomes st,sig-dir
- st,negedge becomes st,neg-edge
- st,pin-ckin becomes st,use-ckin
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
Changes
> On 13.02.2019, at 11:52, David Wu wrote:
>
> Hi philipp,
>
> 在 2019/2/13 下午6:47, Philipp Tomsich 写道:
>>> On 13.02.2019, at 11:33, David Wu wrote:
>>>
>>>
>>>
>>> 在 2019/2/13 下午6:13, Philipp Tomsich 写道:
> On 13.02.2019, at 11:10, David Wu wrote:
>
> Hi Philipp,
>
>
Please ignore. I didn't send the right branch.
Sorry for the noise
On 13/02/2019 11:48, Jean-Jacques Hiblot wrote:
This series adds support for the creation of symbolic links on ext4
file-systems.
The motivation behind this work is to have the ability to "do" the job
of update-alternatives in
Re-use the functions used to write/create a file, to support creation of a
symbolic link.
The difference with a regular file are small:
- The inode mode is flagged with S_IFLNK instead of S_IFREG
- The ext2_dirent's filetype is FILETYPE_SYMLINK instead of FILETYPE_REG
- Instead of storing the
Hi philipp,
在 2019/2/13 下午6:47, Philipp Tomsich 写道:
On 13.02.2019, at 11:33, David Wu wrote:
在 2019/2/13 下午6:13, Philipp Tomsich 写道:
On 13.02.2019, at 11:10, David Wu wrote:
Hi Philipp,
在 2019/2/12 下午9:54, Philipp Tomsich 写道:
On 12.02.2019, at 13:38, David Wu wrote:
Hi Philipp,
在
The command line is:
ln target linkname
Currently symbolic links are supported only in ext4 and only if the option
CMD_EXT4_WRITE is enabled.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
There is no need to modify the buffer passed to ext4fs_write_file().
The memset() call is not required here and was likely copied from the
equivalent part of the ext4fs_read_file() function where we do need it.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Test cases are:
1) basic link creation, verify it can be followed
2) chained links, verify it can be followed
3) replace exiting file a with a link, and a link with a link. verify it
can be followed
4) create a broken link, verify it can't be followed
Signed-off-by: Jean-Jacques Hiblot
If the metadata checksums are enabled, all write operations will fail.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
test/py/tests/test_fs/conftest.py | 2 ++
1 file changed, 2 insertions(+)
diff
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
executes the appropriate fsck tool. It should be called at the end of any
test that modify the
u-boot does not supports updating the metadata chacksums
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2:
- Prevent write access if metadata checksum is enabled
fs/ext4/ext4_write.c | 12 ++--
101 - 200 of 263 matches
Mail list logo
