York,
Thanks a lot for your answer and precisions.
On 23/03/16 16:56, york sun wrote:
> Valentin,
>
> Your understand is correct. Please see my answers below to your questions.
>
> On 03/23/2016 12:46 AM, Valentin Longchamp wrote:
>> Hello,
>>
>> We are
Hello,
We are currently designing a board based on the T1040 CPU from Freescale/NXP. I
am preparing its u-boot support and bring-up tools (JTAG) as well as
contributing to the hardware design. We base our work (both HW and SW) on the
1040RDB dev board as our reference design. We want to use a
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
drivers/spi/kirkwood_spi.c | 39 ---
1 file changed, 20 insertions(+), 19 deletions(-)
diff --git a/drivers/spi/kirkwood_spi.c b/drivers/spi/kirkwood_spi.c
index e7b0982..a95ce78 100644
-
On 25/11/2015 04:52, Stefan Roese wrote:
> Hi Valentine,
>
> On 24.11.2015 17:02, Valentin Longchamp wrote:
>
>
>
>>>>> Does your board use driver model from SPI and SPI flash? If not I
>>>>> think that should be the first step.
>>>&g
On 24/11/2015 02:49, Simon Glass wrote:
> Hi Valentine,
>
> On 23 November 2015 at 02:19, Valentin Longchamp
> <valentin.longch...@keymile.com> wrote:
>> Hi Simon,
>>
>> On 20/11/2015 18:19, Simon Glass wrote:
>>> Hi,
>>>
>>> On 20
Hi Simon,
On 20/11/2015 18:19, Simon Glass wrote:
> Hi,
>
> On 20 November 2015 at 03:13, Valentin Longchamp
> <valentin.longch...@keymile.com> wrote:
>> On 19/11/2015 17:57, Jagan Teki wrote:
>>> On 13 November 2015 at 18:55, Valentin Longchamp
>>&
Hi York,
On 21/11/2015 07:33, York Sun wrote:
> Valentin,
>
> Can you refresh my memory why you needed this
> commitac337168ad81a18e768e5e3cfff8d229adeb2b25 (patch
> http://patchwork.ozlabs.org/patch/455439)?
> Today I bisect an issue back to this commit.
In the patch description, there is a
On 19/11/2015 17:57, Jagan Teki wrote:
> On 13 November 2015 at 18:55, Valentin Longchamp
> <valentin.longch...@keymile.com> wrote:
>> The release command is the pendant of the probe command. This command
>> allows to call spi_flash_free from the command line. This may
header in $headers
> do
> echo "processing $header in $common"
> hbase=`basename $header`
> git mv $common/$hbase $common/include/board-common
> sed -i -e "s/\"..\/common\/$hbase\"/<board-common\/$hbase>/g"
> $vendor/*/
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2:
- Removed support for kmvect1_p1a: not relevant anymore
board/keymile/km82xx/km82xx.c | 2 +-
board/keymile/km83xx/km83xx.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/k
switch enhancements.
Signed-off-by: Bagavathiannan Palanisamy <bagavathiannan.palanis...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
board/keymile/km82xx/km82xx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
For consistency with all the other km83xx plaforms, this should also be
defined for km8309. The same settings as for km8321 are taken.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
include/configs/km/km8309-common.h | 6 ++
1 file chan
This board uses the same CPU (8309) as VECT1. The memory however is
different since it has NAND Flash, the NOR Flash partitioning is
different and of course the FPGAs as well.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
Signed-off-by: Christoph Dietrich <christ
;
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
include/configs/km/km-powerpc.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/configs/km/km-powerpc.h b/include/configs/km/km-powerpc.h
index eb85a74..8121e5c 100644
---
ll support kmvect1.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
include/configs/km/km8309-common.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/configs/km/km8309-common.h
b/include/configs/km/km8309-common
.
This is now changed to ODT_WR_ONLY_CURRENT which is the equivalent of
ODT_WR_ACS.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2:
- Rewritten commit message to get rid of internal git commit reference
include/configs/km8360.h | 4 ++--
1 file changed, 2 inse
From: Holger Brunck <holger.bru...@keymile.com>
We use CONFIG_OF_LIBFDT and CONFIG_OF_BOARD_SETUP on all our powerpc
targets, so there is no need to check these defines within our C code.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <
From: Christoph Dietrich <christoph.dietr...@keymile.com>
This board is similar to TUXX1, but it has differend FPGAs.
Signed-off-by: Christoph Dietrich <christoph.dietr...@keymile.com>
Signed-off-by: Andreas Huber <andreas.hu...@keymile.com>
Signed-off-by: Valentin Longcham
From: Holger Brunck <holger.bru...@keymile.com>
commit 0a4f88b98 removed the usage of our setports function, but the
function itself were not removed. So toss it it's dead code.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <
From: Holger Brunck <holger.bru...@keymile.com>
We use the same settings for open firmware defines on all our powerpc
targets, so move them from the CPU specific headers to the common
powerpc header.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valent
t as a few
measurements done in the lasts have shown. Since all the hardware
qualification tests have been performed with half strength, the nominal
strength settings are removed in favor of the default reset half
strength settings.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com&g
Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
board/keymile/km82xx/km82xx.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/board/keymile/km82xx/km82xx.c b/bo
m>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes in v2: None
board/keymile/common/common.c | 5 -
board/keymile/common/common.h | 2 ++
board/keymile/km82xx/km82xx.c | 9 +
3 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/bo
The hardcoded value are bad, since the address could change between
different boards.
Furthermore, the relevant #defines are set only if #undefined here, so
that they can be changed by some boards if required.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
Changes
for mgcoge3ne
km/powerpc: increase space for kernel imange and FDT blob
km/powerpc: move open firmware defines to km-powerpc.h
km/powerpc: remove unneeded defines
km/powerpc82xx: remove unused function
Valentin Longchamp (7):
powerpc/km8321: define CONFIG_SYS_DDRCDR
powerpc/km8309
On 16/11/2015 14:34, Tom Rini wrote:
> On Mon, Nov 16, 2015 at 01:26:53PM +0100, Holger Brunck wrote:
>> Hi Valentin,
>>
>> On 13/11/15 15:59, Valentin Longchamp wrote:
>>> The impedance settings have been changed with commit
>>> 2ea8ae99595ca11dd228726e
by mpc83xx's cpu_init_f function at early CPU initialization.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/km8321-common.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/configs/km/km8321-common.h
b/include/configs/km/km8321-co
;
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/km-powerpc.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/configs/km/km-powerpc.h b/include/configs/km/km-powerpc.h
index eb85a74..8121e5c 100644
--- a/include/configs/km/
for the km_kirkwood boards that must support .esw where
the DTB sometimes is appended (for backwards compatibility) and sometimes
is passed correctly (as we do now for all newer boards).
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/keymile-common
From: Tobias Müller <tobias.muel...@keymile.com>
Search for the kernel and DTBs in a folder named PRODUCTNAME (found in the IVM)
at the TFTP server instead of the u-boot boardname.
Signed-off-by: Tobias Müller <tobias.muel...@keymile.com>
Signed-off-by: Valentin Longchamp <
b file is not a fallback to boardname.dtb is used.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Tobias Müller <tobias.muel...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/scripts/develop-common.txt |
From: Holger Brunck <holger.bru...@keymile.com>
To prevent u-boot to stop accidently e.g. due to line noise on the
serial line, we now use the option CONFIG_AUTOBOOT_KEYED. We choose the
key for this.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valent
m>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/common/common.c | 5 -
board/keymile/common/common.h | 2 ++
board/keymile/km82xx/km82xx.c | 9 +
3 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/board/keymile/common/common
if someone press
km/scripts: load fdt_bid_kwkey.dtb when working with tftp
Tobias Müller (1):
km/scripts: search for kernel/DTBs at serverip:/PRODUCTNAME via TFTP
in develop mode
Valentin Longchamp (1):
km: update the boot script to check for a DTB
board/keymile/scripts/develop-common.txt
From: Holger Brunck <holger.bru...@keymile.com>
commit 0a4f88b98 removed the usage of our setports function, but the
function itself were not removed. So toss it it's dead code.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <
Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km82xx/km82xx.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/board/keymile/km82xx/km82xx.c b/board/keymile/km82xx/km82
e hardware
qualification tests have been performed with half strength, the nominal
strength settings are removed in favor of the default reset half
strength settings.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/km8321-common.h | 4 ++--
1 file chang
For consistency with all the other km83xx plaforms, this should also be
defined for km8309. The same settings as for km8321 are taken.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/km8309-common.h | 6 ++
1 file changed, 6 insertions(+)
From: Holger Brunck <holger.bru...@keymile.com>
We use CONFIG_OF_LIBFDT and CONFIG_OF_BOARD_SETUP on all our powerpc
targets, so there is no need to check these defines within our C code.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <
to ODT_RD_ONLY_CURRENT, which is uncorrect and causes faulty
RAM accesses at low temperatures.
This is now changed to ODT_WR_ONLY_CURRENT which is the equivalent of
ODT_WR_ACS.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km8360.h | 4 ++--
1 file changed, 2 inse
ll support kmvect1.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/configs/km/km8309-common.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/configs/km/km8309-common.h
b/include/configs/km/km8309-common.h
index d7f6cb1
From: Holger Brunck <holger.bru...@keymile.com>
We use the same settings for open firmware defines on all our powerpc
targets, so move them from the CPU specific headers to the common
powerpc header.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valent
From: Christoph Dietrich <christoph.dietr...@keymile.com>
This board is similar to TUXX1, but it has differend FPGAs.
Signed-off-by: Christoph Dietrich <christoph.dietr...@keymile.com>
Signed-off-by: Andreas Huber <andreas.hu...@keymile.com>
Signed-off-by: Valentin Longcham
This board uses the same CPU (8309) as VECT1. The memory however is
different since it has NAND Flash, the NOR Flash partitioning is
different and of course the FPGAs as well.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
Signed-off-by: Christoph Dietrich <christ
switch enhancements.
Signed-off-by: Bagavathiannan Palanisamy <bagavathiannan.palanis...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km82xx/km82xx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/keymile
The hardcoded value are bad, since the address could change between
different boards.
Furthermore, the relevant #defines are set only if #undefined here, so
that they can be changed by some boards if required.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
i
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km82xx/km82xx.c | 2 +-
board/keymile/km83xx/km83xx.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/keymile/km82xx/km82xx.c b/board/keymile/km82xx/km82xx.c
index 9e285ec..c
/powerpc: remove unneeded defines
km/powerpc82xx: remove unused function
Valentin Longchamp (8):
powerpc/km8321: define CONFIG_SYS_DDRCDR
powerpc/km8321: set the DDRCDR impedance settings back to half
strength
powerpc/km8309: define CONFIG_SYS_DDRCDR
powerpc/km8360: fix the ODT
leases. To be able to deal with these old
versions we add temporary a further target kmvect1_p1a.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km83xx/MAINTAINERS | 1 +
board/keymile/km83
, so it is here sent again.
[1] http://patchwork.ozlabs.org/patch/399411/
Holger Brunck (1):
arm/mgcoge3un: check dip_switch at startup
Tobias Müller (1):
arm/km: Fix LED configuration for 88E1118R PHY (PIGGY3)
Valentin Longchamp (2):
arm/km_kirkwood: remove KM_ENV_BUS and use
There was a small typo for KM_COGE5UN that resulted in the dip switch
not to behave as expected.
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km_arm/km_arm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/keymile/km_arm/km
KM_ENV_BUS was used for nothing else than an direct assignment to
CONFIG_I2C_ENV_EEPROM_BUS. To avoid this, directly use
CONFIG_I2C_ENV_EEPROM_BUS instead.
Patchwork: http://patchwork.ozlabs.org/patch/399411/
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
include/c
c_init to decide wether we wait for
the ne to start or not. If the dip_switch is set we don't wait and
continue immediately.
Signed-off-by: Holger Brunck <holger.bru...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.com>
---
board/keymile/km_arm/km_arm.c | 11 +
From: Tobias Müller <tobias.muel...@keymile.com>
Configure PHY LED register for Marvell 88E1118R PHY used on PIGGY3 to
match with printed descriptions on PCB
Signed-off-by: Tobias Müller <tobias.muel...@keymile.com>
Signed-off-by: Valentin Longchamp <valentin.longch...@keymile.c
the same behavior as env_relocate_spec.
Since the static env_flash variable will be NULL after every function
call, it is thus removed and its functionality is replaced by a
systematic call to spi_flash_probe at the start of both
env_relocate_spec and saveenv.
Signed-off-by: Valentin Longchamp
This is necessary to make sure that all the pins used for SPI access,
especially the CS, are configured back to the NAND Flash interface.
Otherwise, if either newenv or update are called, u-boot cannot access
the NAND Flash anymore.
Signed-off-by: Valentin Longchamp <valentin.lon
ers.u-boot/169723
Changes in v3:
- Rebased on v2015.10
- Rebased on v2015.10
Changes in v2:
- Rebased on v2014.10
Valentin Longchamp (3):
cmd_sf: add 'release' command
env_sf: generalize call to spi_flash_free after accesses
km_arm: call 'sf release' in the newenv and update scripts
commo
The release command is the pendant of the probe command. This command
allows to call spi_flash_free from the command line. This may be
necessary for some boards where sf probe does change the state of the
hardware (like with some pin multiplexing changes for instance).
Signed-off-by: Valentin
by this patch:
http://patchwork.ozlabs.org/patch/448849/
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
arch/powerpc/cpu/mpc512x/Makefile | 3 ---
arch/powerpc/cpu/mpc512x/cache.c | 17 --
arch/powerpc/cpu/mpc5xxx/Makefile | 1 -
arch/powerpc/cpu/mpc5xxx/cache.c
This is not used anymore since the procedure was split into a simple
read function and a later alaysis.
The ivm_read_eeprom name is now used for the previous
ivm_simple_read_eeprom function.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes in v3: None
Changes in v2
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
Valentin Longchamp (6):
KM/IVM: split the IVM reading and parsing in 2 parts
kirkwood/km_arm: read the IVM eeprom earlier
85xx/kmp204x: read the IVM eeprom earlier
83xx/km83xx: read the IVM eeprom earlier
82xx/km82xx: read the IVM eeprom earlier
KM/IVM: remove ivm_read_eeprom(void)
board
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
the HW read to happen twice, the buffer passed to
ivm_read_eeprom() has to be reused by ivm_analyze_eeprom (and thus
allocated before calling ivm_read_eeprom()).
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes in v3:
- Fix typo that prevented patch 1/6 from compiling
the HW read to happen twice, the buffer passed to
ivm_read_eeprom() has to be reused by ivm_analyze_eeprom (and thus
allocated before calling ivm_read_eeprom()).
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes in v2:
- Include the first patch, which was forgotten
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes
This is not used anymore since the procedure was split into a simple
read function and a later alaysis.
The ivm_read_eeprom name is now used for the previous
ivm_simple_read_eeprom function.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
Changes in v2: None
board
Hello Tom and Holger,
On 01/06/2015 09:19 AM, Brunck, Holger wrote:
On 01/05/2015 07:47 PM, Tom Rini wrote:
On Tue, Dec 23, 2014 at 02:08:57PM +0100, Valentin Longchamp wrote:
This is not used anymore since the procedure was split into a simple
read function and a later alaysis
and MAC addresses can be read prior to
ethernet initialization. The analysis of the rest of the IVM content
still happens at a later second stage.
Changes in v2:
- Include the first patch, which was forgotten in the first submission
Valentin Longchamp (6):
KM/IVM: split the IVM reading and parsing
On 12/18/2014 03:03 PM, Jagan Teki wrote:
On 3 November 2014 at 19:31, Valentin Longchamp
valentin.longch...@keymile.com wrote:
Some board require spi_flash_free to be called after all the accesses,
in order, for instance, to restore the pin multiplexing configuration in
the case where
and MAC addresses can be read prior to
ethernet initialization. The analysis of the rest of the IVM content
still happens at a later second stage.
Valentin Longchamp (5):
kirkwood/km_arm: read the IVM eeprom earlier
85xx/kmp204x: read the IVM eeprom earlier
83xx/km83xx: read the IVM eeprom
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
board
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
board
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
board
This is not used anymore since the procedure was split into a simple
read function and a later alaysis.
The ivm_read_eeprom name is now used for the previous
ivm_simple_read_eeprom function.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
board/keymile/common/common.h
This allows to define the ethaddr env variable according to the the IVM
content by reading the IVM in misc_init_r.
Later, when HUSH is available the content read earlier is analyzed to
populate some non env variables.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
board
Hi Tom,
On 11/10/2014 10:29 PM, Tom Rini wrote:
Hey all,
I've pushed v2015.01-rc1 out to the repository and tarballs should exist
soon.
The merge window is now closed. Per both the min-summit and the follow
up emails, I'm going to try and get into the every 2 week RC tagging
groove.
The release command is the pendant of the probe command. This command
allows to call spi_flash_free from the command line. This may be
necessary for some boards where sf probe does change the state of the
hardware (like with some pin multiplexing changes for instance).
Signed-off-by: Valentin
] but it
was rejected without any feedback. So I send this rebased v2 so that it
finally gets reviewed and merged.
[1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/169723
Changes in v2:
- Rebased on v2014.10
Valentin Longchamp (3):
env_sf: generalize call to spi_flash_free after accesses
cmd_sf
the same behavior as env_relocate_spec.
Since the static env_flash variable will be NULL after every function
call, it is thus removed and its functionality is replaced by a
systematic call to spi_flash_probe at the start of both
env_relocate_spec and saveenv.
Signed-off-by: Valentin Longchamp
This is necessary to make sure that all the pins used for SPI access,
especially the CS, are configured back to the NAND Flash interface.
Otherwise, if either newenv or update are called, u-boot cannot access
the NAND Flash anymore.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
On 10/23/2014 05:13 PM, York Sun wrote:
On 10/23/2014 08:02 AM, Valentin Longchamp wrote:
Hi York,
On 10/01/2014 05:41 PM, York Sun wrote:
On 10/01/2014 08:39 AM, Valentin Longchamp wrote:
Hi York,
On 09/30/2014 05:48 PM, York Sun wrote:
Valentin,
We are seeing the image size of kmcoge4
as
well to be on line with the other powerpc boards and to eventually
configure in some additional features (and binary size) to u-boot.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
include/configs/km/kmp204x-common.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
Hi York,
On 10/01/2014 05:41 PM, York Sun wrote:
On 10/01/2014 08:39 AM, Valentin Longchamp wrote:
Hi York,
On 09/30/2014 05:48 PM, York Sun wrote:
Valentin,
We are seeing the image size of kmcoge4 and kmlion1 are on the edge.
Attempts to
add new features cause overflow. Would you
i2c_init_all should disappear and is currently only called
from the early board initialisation sequences, it is not suited for
other usage.
This reverts commit 01a0c64762e902971b34587a8a61b59e9ea51374.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
common/cmd_eeprom.c | 9
KM_ENV_BUS was used for nothing else than an direct assignment to
CONFIG_I2C_ENV_EEPROM_BUS. To avoid this, directly use
CONFIG_I2C_ENV_EEPROM_BUS instead.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
include/configs/km/km_arm.h | 2 +-
include/configs/km_kirkwood.h
.
But perhaps there's a better way to fix that.
I think that the proposal that Holger made to actually define
CONFIG_I2C_ENV_EEPROM_BUS for your boards is what I would try first.
Valentin
Matthias
On 10/14/2014 11:16 AM, Valentin Longchamp wrote:
Since i2c_init_all always sets the bus back
Hello Jagannadha,
On 01/21/2014 11:03 AM, Valentin Longchamp wrote:
On 09/17/2013 08:46 AM, Valentin Longchamp wrote:
Some board require spi_flash_free to be called after all the accesses,
in order, for instance, to restore the pin multiplexing configuration in
the case where the SPI pins
Since on powerpc phys_size_t can be unsigned long long, this printout
line can result in a not nice compile warning.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
common/board_r.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/board_r.c b
This converts all the Keymile powerpc boards to the generic board
initialization.
This includes the 3 Keymile powerpc subsystems: km82xx, km83xx,
and kmp204x.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
include/configs/km/km83xx-common.h | 3 +++
include/configs/km
() call to 0 prior to the function
call to avoid unknown content to end up in gd-flags.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
arch/powerpc/cpu/mpc83xx/start.S | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/cpu/mpc83xx/start.S b/arch/powerpc/cpu
This implies that all the km_kirkwood boards and their variants now are
using the generic board init sequence.
Signed-off-by: Valentin Longchamp valentin.longch...@keymile.com
---
include/configs/km/km_arm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/configs/km/km_arm.h b
Hi York,
On 09/30/2014 05:48 PM, York Sun wrote:
Valentin,
We are seeing the image size of kmcoge4 and kmlion1 are on the edge. Attempts
to
add new features cause overflow. Would you consider to increase the image size
for km boards. You may have noticed several patches doing this for
Hi Simon,
I'm very glad you answered this, I was busy with other stuff these last weeks
but I had planed to pick this issue again this week.
On 09/28/2014 06:27 AM, Simon Glass wrote:
Hi,
On 26 August 2014 09:17, Valentin Longchamp
valentin.longch...@keymile.com wrote:
Hello,
Here
Hello,
Here is the outcome of my debug session today:
On 08/25/2014 05:42 PM, Valentin Longchamp wrote:
Hello,
I am currently porting all the Keymile boards to CONFIG_SYS_GENERIC_BOARD.
On u-boot 2014.10-rc1 I have all of them working quite well (at least booting
and showing no obvious
1 - 100 of 499 matches
Mail list logo
