Maxime,
I suspect that the issue fixed
in commit c7529dbfastboot: sparse: fix block addressing for
don't care chunk type
complicated the assumptions which led to the implementation of the "sessionId"
in commit 1f8690asparse: Implement several chunks flashing
The fastboot client w
The Pi firmware has changed the default "kernel" load address for 64-bit
mode. The authors have confirmed that this is a deliberate and long-term
change. Adapt U-Boot to the new value.
Signed-off-by: Stephen Warren
---
include/configs/rpi.h | 4
1 file changed, 4 insertions(+)
diff --git a
On Fri, Apr 15, 2016 at 09:50:11AM -0600, Simon Glass wrote:
> Hi Tom,
>
> Unfortunately I'm still unable to apply many of the patches in my
> queue due to build errors. But in the meantime, here are the ones that
> are OK.
>
>
> The following changes since commit ff6552e8cc13c9b2283002144e297d
On Wed, Apr 13, 2016 at 04:38:01PM -0700, Stefan Agner wrote:
> VLAN identifiers are 12-bit decimal numbers, not IP addresses.
>
> Signed-off-by: Stefan Agner
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: Digital signature
___
U-Boot ma
On Wed, Apr 13, 2016 at 09:50:59AM +0530, Lokesh Vutla wrote:
> Not all Keystone2 devices has AEMIF NAND controller. So adding Kconfig
> entry for CONFIG_TI_AEMIF and enabling it in respective defconfigs on
> platforms with AEMIF controller.
>
> Reported-by: Nishanth Menon
> Signed-off-by: Lokes
On Wed, Apr 13, 2016 at 09:57:04AM +0530, Lokesh Vutla wrote:
> commit 62c5674ea136a ("omap: SPL boot devices cleanup and completion")
> cleans up the boot device ids for amx3xx soc. But mistakenly updates wrong
> device IDs for AM43xx USB. Fixing the same here.
>
> Signed-off-by: Lokesh Vutla
On Wed, Apr 13, 2016 at 04:38:02PM -0700, Stefan Agner wrote:
> Ethernet packages with IEEE 802.1Q VLAN support may be up to 1522
> bytes long. Increase the default size used to allocate packet
> storage by 4 bytes. While at it, let git care about history and
> rewrite the comment to represent the
On Wed, Apr 13, 2016 at 09:51:00AM +0530, Lokesh Vutla wrote:
> NAND is not yet enabled on all Keystone2 platforms. So enabled
> CMD_NAND in the respective defconfigs only if available.
>
> Reported-by: Nishanth Menon
> Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
--
Tom
signature.as
Hi Heiko,
On 15/04/2016 12:59, Heiko Schocher wrote:
fix the following build error for m68k boards:
Building current source for 48 boards (2 threads, 1 job per thread)
m68k: + M54455EVB_i66
+arch/m68k/cpu/mcf5445x/start.o: In function `_start':
+arch/m68k/cpu/mcf5445x/start.S:668:(.tex
On 14.04.16 00:29, Tom Rini wrote:
> On Wed, Apr 13, 2016 at 07:42:11PM +0200, Andreas Färber wrote:
> [snip]
>> $fdtfile needs to be the Linux filename. It does not always follow the
>> same pattern as the U-Boot variables you suggest here.
>> CONFIG_DEFAULT_DEVICE_TREE ".dtb" might work better,
This reverts commit b5788dc0dd9570e98552833767f4373db965985d.
Ram size is incorrectly reported as 512MB on a firefly-rk3288 board
with 2GB of ram. Reverting this patch displays the full amount of ram.
Signed-off-by: Vagrant Cascadian
---
arch/arm/mach-rockchip/rk3288/sdram_rk3288.c | 14 ++
From: Stephen Warren
The current code in ARMv8's lowlevel_init() skips the per-CPU GIC
initialization ifndef CONFIG_ARMV8_MULTIENTRY. However, the per-CPU init
should always occur; it's just the one-time init that should only happen
on the master.
Once this consideration is taken into account, t
On Thu, Apr 14, 2016 at 4:15 AM, Roger Quadros wrote:
> Steve,
>
> On 13/04/16 04:55, Steve Rae wrote:
> > On Tue, Apr 12, 2016 at 6:50 AM, Roger Quadros wrote:
> >> Lukasz,
> >>
> >> On 12/04/16 16:37, Lukasz Majewski wrote:
> >>> Hi Roger,
> >>>
> Hi,
>
> On 12/04/16 14:19, Luka
On Thu, Apr 14, 2016 at 3:18 AM, Roger Quadros wrote:
> Hi,
>
> On 13/04/16 19:56, Sam Protsenko wrote:
> > On Wed, Apr 13, 2016 at 3:32 PM, Roger Quadros wrote:
> >> Hi,
> >>
> >> On 13/04/16 15:01, Semen Protsenko wrote:
> >>> From: Sam Protsenko
> >>>
> >>> Some UDC controllers may require b
Am Freitag, 15. April 2016, 12:30:58 schrieb Tom Rini:
> On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
> > Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> > > Fix following warnings for all mips based boards:
> > > mips: + pic32mzdask
> > >
> > > +Warning (unit_address_v
Hi Stephen,
2016-04-16 0:55 GMT+09:00 Stephen Warren :
> On 04/15/2016 05:41 AM, Masahiro Yamada wrote:
>>
>> Per-CPU initialization of GIC is necessary even when
>> CONFIG_ARMV8_MULTIENTRY is undefined.
>
>
>> diff --git a/arch/arm/cpu/armv8/start.S b/arch/arm/cpu/armv8/start.S
>
>
>> @@ -208,6 +
On Fri, Apr 15, 2016 at 11:37:40AM -0600, Stephen Warren wrote:
> On 04/15/2016 11:11 AM, Tom Rini wrote:
> >On Fri, Apr 15, 2016 at 10:56:40AM -0600, Stephen Warren wrote:
> >>On 04/15/2016 10:30 AM, Tom Rini wrote:
> >>>On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
> Am 15.0
On 04/15/2016 11:11 AM, Tom Rini wrote:
On Fri, Apr 15, 2016 at 10:56:40AM -0600, Stephen Warren wrote:
On 04/15/2016 10:30 AM, Tom Rini wrote:
On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
Fix following warnings for all mips ba
On Fri, Apr 15, 2016 at 10:56:40AM -0600, Stephen Warren wrote:
> On 04/15/2016 10:30 AM, Tom Rini wrote:
> >On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
> >>Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> >>>Fix following warnings for all mips based boards:
> >>> mips: +
On 04/15/2016 10:30 AM, Tom Rini wrote:
On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
Fix following warnings for all mips based boards:
mips: + pic32mzdask
+Warning (unit_address_vs_reg): Node /memory has a reg or ranges
Hi Simon,
On 15/04/2016 17:23, Simon Glass wrote:
Hi Angelo,
On 15 April 2016 at 08:42, Angelo Dureghello wrote:
Hi Simon,
On 15/04/2016 16:14, Simon Glass wrote:
Hi Angelo,
On 27 December 2015 at 21:22, Simon Glass wrote:
On 20 December 2015 at 08:54, Angelo Dureghello wrote:
To u
On Fri, Apr 15, 2016 at 05:23:54PM +0200, Andreas Färber wrote:
> Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> > Fix following warnings for all mips based boards:
> > mips: + pic32mzdask
> > +Warning (unit_address_vs_reg): Node /memory has a reg or ranges property,
> > but no unit name
On 04/15/2016 05:41 AM, Masahiro Yamada wrote:
Per-CPU initialization of GIC is necessary even when
CONFIG_ARMV8_MULTIENTRY is undefined.
diff --git a/arch/arm/cpu/armv8/start.S b/arch/arm/cpu/armv8/start.S
@@ -208,6 +208,8 @@ WEAK(lowlevel_init)
*/
ldr x0, =GICD_BASE
Hi Tom,
Unfortunately I'm still unable to apply many of the patches in my
queue due to build errors. But in the meantime, here are the ones that
are OK.
The following changes since commit ff6552e8cc13c9b2283002144e297d63b30ac400:
R
xpress: Update include (2016-04-13 15:45:50 -0400)
are avail
On 19 March 2016 at 18:33, Tom Rini wrote:
>
> On Sat, Mar 19, 2016 at 06:25:48PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On 15 March 2016 at 21:32, Simon Glass wrote:
> > >
> > > On 15 March 2016 at 11:20, Tom Rini wrote:
> > > > good enough.
> > > > - Make include like other arches d
On 15 April 2016 at 08:12, Simon Glass wrote:
> On 12 April 2016 at 13:11, Tom Rini wrote:
>> In rollback_space_kernel we were not initializing the reserved fields
>> which should be for safety sake, and doing memset here means we don't
>> need to set the version field specifically either.
>>
>>
On 6 April 2016 at 17:16, Simon Glass wrote:
> On 6 April 2016 at 12:49, Stephen Warren wrote:
>> From: Stephen Warren
>>
>> This function parses the reg property based on an index found in the
>> reg-names property. This is required for bindings that are written
>> using reg-names rather than h
Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> Fix following warnings for all mips based boards:
> mips: + pic32mzdask
> +Warning (unit_address_vs_reg): Node /memory has a reg or ranges property,
> but no unit name
> +Warning (unit_address_vs_reg): Node /cpus/cpu@0 has a unit name, but n
Hi Angelo,
On 15 April 2016 at 08:42, Angelo Dureghello wrote:
> Hi Simon,
>
>
> On 15/04/2016 16:14, Simon Glass wrote:
>>
>> Hi Angelo,
>>
>> On 27 December 2015 at 21:22, Simon Glass wrote:
>>>
>>> On 20 December 2015 at 08:54, Angelo Dureghello wrote:
To use serial uclass and DM,
Add missing USB gadget options, so that microzed platfrom is uniform to
other zed platforms. This fixes build with zynq_microzed_defconfig.
Signed-off-by: Sam Protsenko
---
configs/zynq_microzed_defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/configs/zynq_microzed_defconfig b/
Hi Simon,
On 15/04/2016 16:14, Simon Glass wrote:
Hi Angelo,
On 27 December 2015 at 21:22, Simon Glass wrote:
On 20 December 2015 at 08:54, Angelo Dureghello wrote:
To use serial uclass and DM, CONFIG_SYS_MALLOC_F must be used.
So CONFIG_SYS_GENERIC_GLOBAL_DATA has been undefined and
call t
During Kconfig migrating process we missed to check some gadget options
for SPL_BUILD. Do it now to properly disable gadget in SPL build for
those platforms that disabled it before migrating options to Kconfig.
Signed-off-by: Sam Protsenko
---
include/configs/am43xx_evm.h | 1 +
in
Hi Heiko,
On 15/04/2016 12:59, Heiko Schocher wrote:
fix the following build error for m68k boards:
Building current source for 48 boards (2 threads, 1 job per thread)
m68k: + M54455EVB_i66
+arch/m68k/cpu/mcf5445x/start.o: In function `_start':
+arch/m68k/cpu/mcf5445x/start.S:668:(.tex
On 04/15/2016 12:41 PM, Heiko Schocher wrote:
> Fix following DTC warnings for all socfpga boards:
> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
> no unit name
> Warning (unit_address_vs_reg): Node /soc/clkmgr@ffd04000/clocks/main_pll has
> a reg or ranges proper
Hi Angelo,
On 27 December 2015 at 21:22, Simon Glass wrote:
> On 20 December 2015 at 08:54, Angelo Dureghello wrote:
>> To use serial uclass and DM, CONFIG_SYS_MALLOC_F must be used.
>> So CONFIG_SYS_GENERIC_GLOBAL_DATA has been undefined and
>> call to board_init_f_mem() is added for all cpu's.
Hi Mugunthan,
On 15 March 2016 at 07:59, Tom Rini wrote:
>
> On Tue, Mar 15, 2016 at 05:44:10PM +0530, Mugunthan V N wrote:
>
> > devm_zalloc() is already defined in dm/device.h header, so
> > devm_zalloc can be removed from linux_compact.h beader file.
> >
> > Signed-off-by: Mugunthan V N
>
> R
On 12 April 2016 at 13:11, Tom Rini wrote:
> In rollback_space_kernel we were not initializing the reserved fields
> which should be for safety sake, and doing memset here means we don't
> need to set the version field specifically either.
>
> Reported-by: Coverity (CID: 143917)
> Cc: Simon Glass
On 12 April 2016 at 07:21, Stefan Roese wrote:
> This patch prepares the designware I2C driver for the DM conversion.
> This is mainly done by removing struct i2c_adapter from the functions
> that shall be used by the DM driver version as well.
>
> Signed-off-by: Stefan Roese
> Cc: Simon Glass
>
On 04/15/2016 04:28 PM, Heiko Schocher wrote:
Fix following warnings for all vf6 based boards:
Warning (unit_address_vs_reg): Node
/soc/ifc@153/board-control@3,0/mdio-mux-emi1 has a reg or ranges property,
but no unit name
Warning (unit_address_vs_reg): Node /soc/aips-bus@4000 has a un
On 04/15/2016 03:00 PM, Alexey Brodkin wrote:
> Hi Marek,
>
> On Mon, 2016-04-11 at 20:48 +0200, Marek Vasut wrote:
>> On 04/11/2016 08:13 PM, Alexey Brodkin wrote:
>>>
>>> Hi Marek,
>>>
>>> On Mon, 2016-04-11 at 19:54 +0200, Marek Vasut wrote:
On 04/11/2016 07:48 PM, Alexey Brodkin wrot
Hi Marek,
On Mon, 2016-04-11 at 20:48 +0200, Marek Vasut wrote:
> On 04/11/2016 08:13 PM, Alexey Brodkin wrote:
> >
> > Hi Marek,
> >
> > On Mon, 2016-04-11 at 19:54 +0200, Marek Vasut wrote:
> > >
> > > On 04/11/2016 07:48 PM, Alexey Brodkin wrote:
> > > >
> > > >
> > > > Hi Alex,
> > > >
>
Add the ability to pass the phy-handle node offset
to the phy driver. This allows the phy driver
to access the DT subnode's data and parse accordingly.
Signed-off-by: Dan Murphy
Tested-by: Michal Simek
---
v6 - No changes - https://patchwork.ozlabs.org/patch/608769/
drivers/net/zynq_gem.c |
Move the phy_interface_is_rgmii to the phy.h
file for all phy's to be able to use the API.
This now aligns with the Linux kernel based on
commit e463d88c36d42211aa72ed76d32fb8bf37820ef1
Signed-off-by: Dan Murphy
Reviewed-by: Mugunthan V N
Reviewed-by: Michal Simek
---
v6 - No changes - https:
Not all devices use the same internal delay or fifo depth.
Add the ability to set the internal delay for rx or tx and the
fifo depth via the devicetree. If the value is not set in the
devicetree then set the delay to the default.
If devicetree is not used then use the default defines within the
d
The code assumed that if the interface is not RGMII configured
then it must be SGMII configured. This device has the ability
to support most of the MII interfaces. Therefore add the
helper for SGMII and only configure the device if the interface is
configured for SGMII.
Signed-off-by: Dan Murphy
Add the device tree bindings and the accompanying documentation
for the TI DP83867 Giga bit ethernet phy driver.
The original document was from:
[commit 2a10154abcb75ad0d7b6bfea6210ac743ec60897 from the Linux kernel]
Signed-off-by: Dan Murphy
Reviewed-by: Mugunthan V N
---
v6 - No Changes
Add the ability to read the phy-handle node of the
cpsw slave. Upon reading this handle the phy-id
can be stored based on the reg node in the DT.
The phy-handle also needs to be stored and passed
to the phy to access any phy data that is available.
Signed-off-by: Dan Murphy
---
v6 - Fix build
Add a helper to phy.h to identify whether the
phy is configured for SGMII all variables.
Signed-off-by: Dan Murphy
Reviewed-by: Mugunthan V N
Reviewed-by: Michal Simek
---
v6 - No changes - https://patchwork.ozlabs.org/patch/608766/
include/phy.h | 11 +++
1 file changed, 11 insertio
The initial version missed to set up the pin number 17.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/uniphier/pinctrl-uniphier-ld20.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pinctrl/uniphier/pinctrl-uniphier-ld20.c
b/drivers/pinctrl/uniphier/pinctr
In data venerdì 15 aprile 2016 12:53:36, Marek Vasut ha scritto:
> On 04/14/2016 03:20 PM, Diego wrote:
> > On 18.02.2016, Schrempf Frieder wrote:
> >> At the moment I have two sticks with the same chip around for which
> >> setting USB_MAX_XFER_BLK from 65535 to 32767 fixed the file transfer.
> >>
Per-CPU initialization of GIC is necessary even when
CONFIG_ARMV8_MULTIENTRY is undefined.
Signed-off-by: Masahiro Yamada
---
arch/arm/cpu/armv8/start.S | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/cpu/armv8/start.S b/arch/arm/cpu/armv8/start.S
index dceedd7..124a274 100644
--
Hello All,
I am using U-Boot 2013.04. I have tried enabling the USB support at u-boot. Now
i get the following log on successful detection of a USB device.
U-Boot > usb start
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: USB EHCI 1.00
scanning
Fi all DTC warnings for TI boards.
Signed-off-by: Heiko Schocher
---
This warnings pop up with the DTC compiler:
$ /tmp/dtc/dtc -v
Version: DTC 1.4.1-gbeef80b8
This fixes the compile warnings for:
https://travis-ci.org/hsdenx/u-boot/jobs/123238798
see:
https://travis-ci.org/hsdenx/u-boot/jobs/
Am 12.04.2016 um 05:09 schrieb Wills Wang:
>
> These series of patch based on top of mips/next, it fix some defects on
> the previous patch series "add support for atheros ath79 based SOCs".
>
>
> Wills Wang (4):
> ath79: spi: Remove the explicit pinctrl setting
> ar933x: serial: Remove th
Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> Fix following warnings for all mips based boards:
> mips: + pic32mzdask
> +Warning (unit_address_vs_reg): Node /memory has a reg or ranges property,
> but no unit name
> +Warning (unit_address_vs_reg): Node /cpus/cpu@0 has a unit name, but
On 04/15/2016 04:29 PM, Heiko Schocher wrote:
> Fix following warnings for all mips based boards:
> mips: + pic32mzdask
> +Warning (unit_address_vs_reg): Node /memory has a reg or ranges property,
> but no unit name
> +Warning (unit_address_vs_reg): Node /cpus/cpu@0 has a unit name, but n
On Monday 11 April 2016 05:48 PM, Dan Murphy wrote:
> Not all devices use the same internal delay or fifo depth.
> Add the ability to set the internal delay for rx or tx and the
> fifo depth via the devicetree. If the value is not set in the
> devicetree then set the delay to the default.
>
> If
On Monday 11 April 2016 05:48 PM, Dan Murphy wrote:
> Add the ability to read the phy-handle node of the
> cpsw slave. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
>
> The phy-handle also needs to be stored and passed
> to the phy to access any phy data tha
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Adding support for AM43xx secure devices require the addition
> of some SOC specific config options like the amount of memory
> used by public ROM and the address of the entry point of u-boot
> or SPL, as seen by
Fix following warnings for all mips based boards:
mips: + pic32mzdask
+Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
no unit name
+Warning (unit_address_vs_reg): Node /cpus/cpu@0 has a unit name, but no reg
property
Signed-off-by: Heiko Schocher
---
This
fix the following build error for m68k boards:
Building current source for 48 boards (2 threads, 1 job per thread)
m68k: + M54455EVB_i66
+arch/m68k/cpu/mcf5445x/start.o: In function `_start':
+arch/m68k/cpu/mcf5445x/start.S:668:(.text+0x45a): relocation truncated to fit:
R_68K_PC16 agains
Fix following warnings for all vf6 based boards:
Warning (unit_address_vs_reg): Node
/soc/ifc@153/board-control@3,0/mdio-mux-emi1 has a reg or ranges property,
but no unit name
Warning (unit_address_vs_reg): Node /soc/aips-bus@4000 has a unit name, but
no reg property
Warning (unit_addr
Fix following DTC warnings for all x86 boards.
There was a warning like:
Warning (unit_address_vs_reg): Node /microcode/update@0 has a unit name, but no
reg property
Warning (unit_address_vs_reg): Node /microcode/update@1 has a unit name, but no
reg property
I replaced "udpate@" with "update_".
On 04/14/2016 03:20 PM, Diego wrote:
> On 18.02.2016, Schrempf Frieder wrote:
>> At the moment I have two sticks with the same chip around for which
>> setting USB_MAX_XFER_BLK from 65535 to 32767 fixed the file transfer.
>> Also one of our customers tested a few non-working sticks with this
>> cha
On Monday 11 April 2016 05:48 PM, Dan Murphy wrote:
> Add the ability to read the phy-handle node of the
> cpsw slave. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
>
> The phy-handle also needs to be stored and passed
> to the phy to access any phy data tha
Fix following DTC warnings for all socfpga boards:
Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
no unit name
Warning (unit_address_vs_reg): Node /soc/clkmgr@ffd04000/clocks/main_pll has a
reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds CONFIG_OF_BOARD_SETUP to the config header files
> for dra7xx_evm and am57xx_evm.
>
> Signed-off-by: Daniel Allred
> Signed-off-by: Madan Srinivas
Reviewed-by: Lokesh Vutla
Thanks and regards,
Lokesh
___
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds new defconfig files for DRA7xx and AM57xx secure devices.
> These are the same as the non-secure parts, but with the addition
> of the CONFIG_TI_SECURE_DEVICE option set to 'y'.
>
> Signed-off-by: Daniel Allred
> Signed-off-by: Mada
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds an fdt.c file in that defines the ft_cpu_setup() function,
> which should be called from a board-specific ft_board_setup()).
> This ft_cpu_setup() will currently do nothing for non-secure (GP)
> devices but contains pertinent up
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds the board specific ft_board_setup() functions that
> are called when CONFIG_OF_BOARD_SETUP is defined. These functions
> will currently just call the ft_cpu_setup() function.
>
> Signed-off-by: Daniel Allred
> Signed-off-by: Madan S
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Update the CPU string output so that the device
> type is now included as part of the CPU string that
> is printed as the SPL or u-boot comes up. This update
> adds a suffix of the form "-GP" or "-HS" for production
> devices, so that gene
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Updates the SPL build so that when CONFIG_TI_SECURE_DEVICE
> is in use (which it should be when building for secure parts),
> the TI secure development package is used to create a valid
> secure boot image. The u-boot SPL build processes i
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Adds new defconfig files for AM43xx secure devices.
> These are the same as the non-secure parts, except for
> CONFIG_TI_SECURE_DEVICE option set to 'y'
> CONFIG_ISW_ENTRY_ADDR updated for secure imag
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Updated the CONFIG_SPL_TEXT_BASE to support secure parts (moving
> the start address past secure reserved memory and the size of the
> security certificate that precedes the boot image on secure devices).
> Updated the related CONFIG_SPL_M
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Adds code to detect AM43xx HS EVMS - the string in the
> I2C EEPROM for HS EVMs differs from GP EVMs. Adds code to
> for evm detection, regardless of whether the evm is for
> GP or HS parts, and updates board ini
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Updates configs/am43xx_evm.h to use CONFIG options from
> SOC specific Kconfig file for various calculations.
>
> On AM43x devices, the address of SPL entry point depends on
> the device type, i.e. whether it i
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Modifies the config.mk to build secure images when building
> the SPL for secure devices.
>
> Depending on the boot media, different images are needed
> for secure devices. The build generates u-boot*_HS_* files
> as appropriate for the d
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds a centralized config_secure.mk in omap-common for
> OMAP-style TI secure devices to use for boot image generation
>
> Depending on the boot media, different images are needed for
> secure devices. These commands generates u-boot*_HS_
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Defines CONFIG_TI_SECURE_DEVICE which needs to be turned on
> when building images for secure devices. This flag is used
> to invoke the secure image creation tools for creating a
> boot image that can be used on
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Adds a new Kconfig file for AM33xx class devices. We
> need a common place to define CONFIG parameters
> for these SOCs, especially for adding support
> for secure devices.
>
> a) Adds a definition for ISW_ENTRY
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> From: Madan Srinivas
>
> Adding support for AM43xx secure devices require the addition
> of some SOC specific config options like the amount of memory
> used by public ROM and the address of the entry point of u-boot
> or SPL, as seen by
On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
> Adds doc/README.ti-secure file to explain in generic terms
> how boot images need to be created for secure devices from
> Texas Instruments.
>
> Specific details for creating secure boot images for the
> AM43xx, DRA7xx and AM57xx secure d
Hi Ying,
The commit message should be more clear about what is wrong.
Like when using protocols to support 10G on MAC9 and MAC10, these
MACs should not be identified as 1G interface, otherwise, one MAC will be
Listed as two Ethernet ports, for ex. MAC9 will be listed as FM1@TGEC1
And FM1@DTSEC9.
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of
> ying.zh...@freescale.com
> Sent: Friday, April 15, 2016 2:19 PM
> To: u-boot@lists.denx.de
> Cc: york...@freescale.com; Ying Zhang
> Subject: [U-Boot] [PATCH 2/2] board/t4240rdb: some ethernet ports
>
> -Original Message-
> From: Shengzhou Liu
> Sent: Friday, April 15, 2016 3:45 PM
> To: 'ying.zh...@freescale.com' ; u-
> b...@lists.denx.de
> Cc: york...@freescale.com; Ying Zhang
> Subject: RE: [U-Boot] [PATCH 2/2] board/t4240rdb: some ethernet ports
> shouldn't be detected
>
>
> > -
Dear ying.zh...@freescale.com,
In message <1460701149-36278-2-git-send-email-ying.zh...@freescale.com> you
wrote:
> From: Ying Zhang
>
> FM1_DTSEC9 & FM1_DTSEC10 should not be detected.
Can you please explain (and add the explanation to the commit message)
what this means?
Are this ports dete
Hi,
On 15-04-16 02:46, Siarhei Siamashka wrote:
Hello Hans,
On Thu, 14 Apr 2016 18:58:04 +0200
Hans de Goede wrote:
We are running with the caches disabled when mctl_mem_matches gets called,
but the cpu's write buffer is still there and can still get in the way,
This does not make much sen
From: Ying Zhang
FM1_DTSEC9 & FM1_DTSEC10 should not be detected.
Signed-off-by: Ying Zhang
---
drivers/net/fm/t4240.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/fm/t4240.c b/drivers/net/fm/t4240.c
index ae5aca4..70887fa 100644
--- a/drivers/net/fm/t4240.c
From: Ying Zhang
There are 12 ethernet port on T4240RDB, but there need to set 16
MAC addressed for ethernets.
There need to disable non-existent ethernet ports in U-boot
Signed-off-by: Ying Zhang
---
board/freescale/t4rdb/eth.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/board/f
89 matches
Mail list logo
