Re: [U-Boot] [PATCH 2/2] Enable test/py for sandbox in Travis CI

2016-02-09 Thread Meier, Roger
Thanks Stephen

> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Dienstag, 9. Februar 2016 02:24
> To: Tom Rini <tr...@konsulko.com>
> Cc: Simon Glass <s...@chromium.org>; u-boot@lists.denx.de; Meier, Roger
> <r.me...@siemens.com>; Daniel Schwierzeck
> <daniel.schwierz...@gmail.com>; Heiko Schocher <h...@denx.de>; Stephen
> Warren <swar...@nvidia.com>
> Subject: [PATCH 2/2] Enable test/py for sandbox in Travis CI
> 
> From: Stephen Warren <swar...@nvidia.com>
> 
> This provides runtime test coverage in Travis, in addition to the existing
> build coverage.
> 
> Signed-off-by: Stephen Warren <swar...@nvidia.com>
> ---
>  .travis.yml | 8 
>  1 file changed, 8 insertions(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index 8caaeb34553e..18bf2ed4fcdb 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -16,6 +16,8 @@ addons:
>  - bc
>  - build-essential
>  - libsdl1.2-dev
> +- python
> +- python-virtualenv
> 
>  cache:
>   - apt
> @@ -38,6 +40,9 @@ install:
>   - echo -e "\n\n[toolchain-alias]\n${BUILDMAN_ALIAS} i386\n" >>
> ~/.buildman
>   - echo -e "${BUILDMAN_ALIAS_ARM} armv5te\n" >> ~/.buildman
>   - cat ~/.buildman
> + - virtualenv /tmp/venv
> + - . /tmp/venv/bin/activate
> + - pip install pytest
> 
>  env:
>global:
> @@ -177,5 +182,8 @@ matrix:
>  # some statistics about the code base
>  - env:
>  - TEST_CMD="sloccount ."
> +# test/py
> +- env:
> +- TEST_CMD="./test/py/test.py --bd sandbox --build"
> 
>  # TODO make it perfect ;-r
> --
> 2.7.0

Reviewed-by: Roger Meier <r.me...@siemens.com>


Best Regards
Roger

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] .travis.yml: rework according to new travis-ci infra

2016-02-04 Thread Meier, Roger
Hi Warren

> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Mittwoch, 3. Februar 2016 17:58
> To: Roger Meier <ro...@bufferoverflow.ch>
> Cc: Tom Rini <tr...@konsulko.com>; Tom Rini <tr...@ti.com>; u-
> b...@lists.denx.de; Andreas Färber <afaer...@suse.de>; Meier, Roger
> <r.me...@siemens.com>; Daniel Schwierzeck <daniel.schwierz...@gmail.com>
> Subject: Re: [U-Boot] .travis.yml: rework according to new travis-ci infra
> 
> On 02/01/2016 06:57 PM, Tom Rini wrote:
> > On Mon, Jan 25, 2016 at 08:22:41PM +0100, Roger Meier wrote:
> >
> >> - install using addons.apt
> >> - remove MAKEALL
> >> - split mpc85xx boards
> >> - remove TEST_CONFIG_CMD, just info
> >> - fetch mips toolchain via buildman
> >> - remove --list-error-boards param
> >> - conditional script
> >> - use TOOLCHAIN instead of INSTALL_TOOLCHAIN
> >> - add aarch64
> >> - enable notifications via email
> >>
> >> Signed-off-by: Roger Meier <r.me...@siemens.com>
> >> Cc: Wolfgang Denk <w...@denx.de>
> >> Cc: Heiko Schocher <h...@denx.de>
> >> Cc: Tom Rini <tr...@ti.com>
> >> Cc: Daniel Schwierzeck <daniel.schwierz...@gmail.com>
> >> Cc: Andreas Färber <afaer...@suse.de>
> >> Tested-by: Daniel Schwierzeck <daniel.schwierz...@gmail.com>
> >> Acked-by: Heiko Schocher <h...@denx.de>
> >
> > Applied to u-boot/master, thanks!
> 
> I wanted to add something to this file, so I set up my own travis-ci.org
> account and made it run against my own github U-Boot repo "fork" to test
> my change. However, most of the builds failed before I even modified
> .travis.yml. For example:
> 
> > $ if [[ "${TOOLCHAIN}" == *arm* ]]; then sh eldk-eglibc-i686-arm-toolchain-
> gmae-5.4.sh -y ; fi
> > Enter target directory for SDK (default: /opt/eldk-5.4/armv5te): /opt/eldk-
> 5.4/armv5te
> > You are about to install the SDK to "/opt/eldk-5.4/armv5te". Proceed[Y/n]?Y
> > Sorry, you are not allowed to execute as root.

Things like this should work, but there are some limitations.
Ok, you added sudo:true within your branch.

It's unclear to me why it does not work on your build...
Here it works:
https://travis-ci.org/u-boot/u-boot/jobs/106517001
> 
> Do I need to perform some manual configuration of my
> repo/branch/profile/... before this .travis.yml will work correctly
> (container vs VM I wonder?), or perhaps obtain some kind of
> authorization from the Travis CI admins? If so, if that could all be
> documented in a comment at the top of .travis.yml that would be
> extremely helpful. Bonus points if it can be handled simply be adding
> extra configuration options into .travis.yml so that it "just works"
> without manual steps.
No, there is nothing to do beside of setting up the hook.
I'm unsure about replication of documentation within .travis.yml

Regards
Roger

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] i2c, avr32: fix compiler warning "input is not relaxable"

2015-11-17 Thread Meier, Roger
Thanks Heiko!

> -Original Message-
> From: Heiko Schocher [mailto:h...@denx.de]
> Sent: Dienstag, 17. November 2015 12:23
> To: U-Boot Mailing List <u-boot@lists.denx.de>
> Cc: Heiko Schocher <h...@denx.de>; Andreas Bießmann
> <andreas.de...@googlemail.com>; Meier, Roger <r.me...@siemens.com>;
> Simon Glass <s...@chromium.org>
> Subject: [PATCH] i2c, avr32: fix compiler warning "input is not relaxable"
> 
> compiling U-Boot for avr32 boards shows since
> commit 3d1957f0ea01 "dm: i2c: Add support for multiplexed I2C buses"
> this warning:
> 
> Building current source for 4 boards (4 threads, 8 jobs per thread)
>  avr32:  +   atstk1002
> +(atstk1002) drivers/i2c/built-in.o: warning: input is not relaxable
>  avr32:  +   grasshopper
> +(grasshopper) drivers/i2c/built-in.o: warning: input is not relaxable
>  avr32:  +   atngw100
> +(atngw100) drivers/i2c/built-in.o: warning: input is not relaxable
>  avr32:  +   atngw100mkii
> +(atngw100mkii) drivers/i2c/built-in.o: warning: input is not relaxable
> 040 /4  0:00:16  : atngw100mkii
> 
> Fix it.
> 
> Signed-off-by: Heiko Schocher <h...@denx.de>
> 
> ---
> 
>  drivers/i2c/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/Makefile b/drivers/i2c/Makefile
> index 32198bd..811ad9b 100644
> --- a/drivers/i2c/Makefile
> +++ b/drivers/i2c/Makefile
> @@ -40,4 +40,4 @@ obj-$(CONFIG_SYS_I2C_UNIPHIER) += i2c-uniphier.o
>  obj-$(CONFIG_SYS_I2C_UNIPHIER_F) += i2c-uniphier-f.o
>  obj-$(CONFIG_SYS_I2C_ZYNQ) += zynq_i2c.o
> 
> -obj-y += muxes/
> +obj-$(CONFIG_I2C_MUX) += muxes/
> --
> 2.1.0

Reviewed-by: Roger Meier <r.me...@siemens.com>

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] siemens,am33x: adjust mtd partition

2015-07-01 Thread Meier, Roger
Thanks Sam!

 -Original Message-
 From: Samuel Egli [mailto:samuel.e...@siemens.com]
 Sent: Mittwoch, 1. Juli 2015 11:05
 To: u-boot@lists.denx.de
 Cc: tr...@konsulko.com; Egli, Samuel; Heiko Schocher; Meier, Roger
 Subject: [PATCH] siemens,am33x: adjust mtd partition
 
 Use one mtd partition for rootfs and configuration by
 means of ubi volumes and get rid of configuration partition.
 We can use partition layout for both 256MB and 512MB flash.
 
 Signed-off-by: Samuel Egli samuel.e...@siemens.com
 Cc: Heiko Schocher h...@denx.de
 Cc: Roger Meier r.me...@siemens.com

Reviewed-by: Roger Meier r.me...@siemens.com

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] travis.yml: add more targets to build on travis

2015-03-17 Thread Meier, Roger
 -Original Message-
 From: Heiko Schocher [mailto:h...@denx.de]
 Sent: Dienstag, 17. März 2015 08:22
 To: u-boot@lists.denx.de
 Cc: Heiko Schocher; Tom Rini; Meier, Roger; Angelo Dureghello; Alison Wang
 Subject: [PATCH] travis.yml: add more targets to build on travis
 
 - add more targets for building with buildman:
   - avr32
   - m68k
 
 and while at it, sort the list alphabetical
 
 Signed-off-by: Heiko Schocher h...@denx.de
Reviewed-by: Roger Meier r.me...@siemens.com

Thanks Heiko for pushing this forward!
-roger

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] travis.yml: some adaptions

2015-03-05 Thread Meier, Roger
Thanks Heiko!

This is a great step towards *build everything* on public servers.

 -Original Message-
 From: Heiko Schocher [mailto:h...@denx.de]
 Sent: Donnerstag, 5. März 2015 09:02
 To: u-boot@lists.denx.de
 Cc: Heiko Schocher; Prafulla Wadaskar; Tom Rini; Meier, Roger; Luka Perkov
 Subject: [PATCH] travis.yml: some adaptions
 
 - adapt to build with eldk-5.4
 - add more targets for building with buildman:
   - freescale -x arm,m68k,aarch64
   - arm1136
   - arm1176
   - arm720t
   - arm920t
   - davinci
   - kirkwood
 
 Signed-off-by: Heiko Schocher h...@denx.de

Reviewed-by: Roger Meier r.me...@siemens.com


regards
-roger
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v2] .travis.yml: build u-boot on travis-ci

2014-11-18 Thread Meier, Roger
Hello,

 Hi,
 
 Am 14.11.2014 um 14:58 schrieb Roger Meier:
  ---
  Changes for v2:
- use latest device tree compiler (suggested by Daniel Schwierzeck)
- add sandbox (suggested by Daniel Schwierzeck)
- seperate echo and execution of TEST_CMD
- remove BUILD_NCPUS( part of script)
- introduce ${TEST_CONFIG_CMD}
- add libsdl-dev package which is required by sandbox
- use buildman (suggested by Tom Rini)
- generate ~/.buildman
- split ppc into several jobs
- install gcc-arm-linux-gnueabihf
- use --inline-suppr option for cppcheck
 
  Signed-off-by: Roger Meier r.me...@siemens.com
  Cc: Wolfgang Denk w...@denx.de
  Cc: Tom Rini tr...@ti.com
  Cc: Daniel Schwierzeck daniel.schwierz...@gmail.com
  ---
 
 The Sob was probably meant to go before the first ---?
Yes, however patchworks detected the patch properly.
http://patchwork.ozlabs.org/patch/410846/

What I forgot to mention, here is the build result:
https://travis-ci.org/u-boot/u-boot/builds/41050962

Best!
-roger

PS:
I've also contacted GitHub about the orphan u-boot account and I got it.
So we can have a mirror on GitHub and use travis-ci as a build system.
Here is this patch: https://github.com/u-boot/u-boot/tree/travis2
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] .travis.yml: build u-boot on travis-ci

2014-11-05 Thread Meier, Roger
And here is the result:
https://travis-ci.org/siemens/u-boot/builds/40058028


 -Original Message-
 From: Roger Meier [mailto:r.me...@siemens.com]
 Sent: Mittwoch, 5. November 2014 14:39
 To: u-boot@lists.denx.de
 Cc: Roger Meier; Meier, Roger
 Subject: [PATCH] .travis.yml: build u-boot on travis-ci
 
 Signed-off-by: Roger Meier r.me...@siemens.com
 ---
  .travis.yml |   86
 +++
  1 file changed, 86 insertions(+)
  create mode 100644 .travis.yml
 
 diff --git a/.travis.yml b/.travis.yml
 new file mode 100644
 index 000..027aff2
 --- /dev/null
 +++ b/.travis.yml
 @@ -0,0 +1,86 @@
 +# Copyright Roger Meier r.me...@siemens.com
 +# SPDX-License-Identifier:   GPL-2.0+
 +
 +# build U-Boot on Travis CI - https://travis-ci.org/
 +
 +language: c
 +
 +cache:
 + - apt
 +
 +install:
 + - sudo apt-get install -qq cppcheck sloccount sparse bc device-tree-compiler
 gcc-arm-linux-gnueabi
 +
 +env:
 +  global:
 +- BUILD_DIR=build
 +- DOWNLOAD_URL=
 +- INSTALL_CMD=
 +- CROSS_COMPILE=
 +- HOSTCC  = cc
 +- HOSTCXX = c++
 +
 +before_script:
 + - if [[ $DOWNLOAD_URL !=  ]]; then wget $DOWNLOAD_URL ; fi
 + - if [[ $INSTALL_CMD !=  ]]; then $INSTALL_CMD ; fi
 +
 +script:
 + - export BUILD_NCPUS=`grep processor /proc/cpuinfo | wc -l`
 + - echo BUILD on $BUILD_NCPUS cpu's
 + - echo $TEST_CMD  $TEST_CMD
 +
 +matrix:
 +  include:
 +# arm and powerpc have too many boards for th 50min time limit
 +# so we need to build by vendor
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v atmel
 +  CROSS_COMPILE=arm-linux-gnueabi-
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v denx
 +  CROSS_COMPILE=arm-linux-gnueabi-
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v freescale
 +  CROSS_COMPILE=arm-linux-gnueabi-
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v siemens
 +  CROSS_COMPILE=arm-linux-gnueabi-
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v ti
 +  CROSS_COMPILE=arm-linux-gnueabi-
 +- env:
 +- TEST_CMD=./MAKEALL -a x86
 +- HOSTCC  = gcc
 +- HOSTCXX  = g++
 +- env:
 +- TEST_CMD=./MAKEALL -a x86
 +- HOSTCC  = clang
 +- HOSTCXX  = clang++
 +- env:
 +- TEST_CMD=./MAKEALL -a powerpc -v freescale
 +  CROSS_COMPILE=/opt/eldk-5.4/powerpc/sysroots/i686-eldk-
 linux/usr/bin/powerpc-linux/powerpc-
 +  DOWNLOAD_URL=ftp://ftp.denx.de/pub/eldk/5.4/targets/powerpc/eldk-
 eglibc-i686-powerpc-toolchain-gmae-5.4.sh
 +  INSTALL_CMD=sh eldk-eglibc-i686-powerpc-toolchain-gmae-5.4.sh -y
 +- env:
 +- TEST_CMD=./MAKEALL -a mips
 +  CROSS_COMPILE=/opt/eldk-5.4/mips/sysroots/i686-eldk-
 linux/usr/bin/mips32-linux/mips-linux-
 +  DOWNLOAD_URL=ftp://ftp.denx.de/pub/eldk/5.4/targets/mips/eldk-
 eglibc-i686-mips-toolchain-gmae-5.4.sh
 +  INSTALL_CMD=sh eldk-eglibc-i686-mips-toolchain-gmae-5.4.sh -y
 +- env:
 +- TEST_CMD=./MAKEALL -a arm -v denx -v siemens
 +  CROSS_COMPILE=/opt/eldk-5.4/armv7a-hf/sysroots/i686-eldk-
 linux/usr/bin/armv7ahf-vfp-neon-linux-gnueabi/arm-linux-gnueabi-
 +  DOWNLOAD_URL=ftp://ftp.denx.de/pub/eldk/5.4/targets/armv7a-
 hf/eldk-eglibc-i686-arm-toolchain-gmae-5.4.sh
 +  INSTALL_CMD=sh eldk-eglibc-i686-arm-toolchain-gmae-5.4.sh -y
 +- env:
 +- TEST_CMD=cppcheck --force --quiet .
 +- env:
 +- TEST_CMD=grep -r TODO *
 +- env:
 +- TEST_CMD=grep -r FIXME *
 +- env:
 +- TEST_CMD=grep -r HACK *
 +- env:
 +- TEST_CMD=sloccount .
 +
 +notifications:
 +  email: false
 --
 1.7.10.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] .travis.yml: build u-boot on travis-ci

2014-11-05 Thread Meier, Roger
 On Wed, Nov 05, 2014 at 03:10:11PM +, Meier, Roger wrote:
 
  And here is the result:
  https://travis-ci.org/siemens/u-boot/builds/40058028
 
 Interesting.  I just saw something else about travis-ci elsewhere.  My
 first thought is can you update it to use buildman instead of MAKEALL?
 And a few more comments about what/why and I don't see a downside to
 including at least a sample config and we can explore wider usage of
 travis-ci (the 50min thing worries me a bit but maybe we can find some
 other ways to break it down).  Thanks!
Yes, I know buildman is the new MAKEALL.
It is already on my list, I will try to get it up and running during the
next few days and will include some more comments with a further version. 

A big challenge is to add all toolchains and create small configurations
to stay within time limit. That's why I created some vendor configs.
Parallel execution is another key element, I guess buildman is already
taking care on this.

Would be great, if somebody can have a look at the broken builds we have
with this .travis.yml file.

Best!
-roger

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v10 0/4] mtd: nand: omap: optimize and clean-up of OMAP NAND driver

2013-11-19 Thread Meier, Roger
 -Original Message-
 From: Pekon Gupta [mailto:pe...@ti.com]
[...]
 
 Pekon Gupta (4):
   mtd: nand: omap: make am33xx/elm.c as common driver for all OMAPx and
 AM platforms
   mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform
   mtd: nand: omap: add CONFIG_NAND_OMAP_ECCSCHEME for selection of
 ecc-scheme
   am335x: fix GPMC config for NAND and NOR SPL boot
 
  arch/arm/cpu/armv7/am33xx/Makefile |   1 -
  arch/arm/cpu/armv7/am33xx/mem.c|  52 ++--
  arch/arm/include/asm/arch-am33xx/mem.h |   5 -
  .../include/asm/{arch-am33xx/elm.h = omap_elm.h}  |   0
  arch/arm/include/asm/omap_gpmc.h   |  16 +
  board/ti/am335x/board.c|  14 +-
  doc/README.nand|  53 
  doc/README.omap3   |   3 +-
  drivers/mtd/nand/Makefile  |   1 +
  .../am33xx/elm.c = drivers/mtd/nand/omap_elm.c|   6 +-
  drivers/mtd/nand/omap_gpmc.c   | 323 +---
 -
  include/configs/am335x_evm.h   |   5 +-
  include/configs/am335x_igep0033.h  |   2 +
  include/configs/am3517_crane.h |   1 +
  include/configs/am3517_evm.h   |   1 +
  include/configs/devkit8000.h   |   1 +
  include/configs/mcx.h  |   2 +-
  include/configs/omap3_beagle.h |   1 +
  include/configs/omap3_evm.h|   1 +
  include/configs/omap3_evm_quick_nand.h |   1 +
  include/configs/omap3_igep00x0.h   |   1 +
  include/configs/omap3_overo.h  |   1 +
  include/configs/siemens-am33x-common.h |   2 +
  include/configs/tam3517-common.h   |   2 +-
  include/configs/tricorder.h|   2 +-
  25 files changed, 321 insertions(+), 176 deletions(-)
  rename arch/arm/include/asm/{arch-am33xx/elm.h = omap_elm.h} (100%)
  rename arch/arm/cpu/armv7/am33xx/elm.c = drivers/mtd/nand/omap_elm.c (97%)
 
 --
 1.8.1

Reviewed-by: Roger Meier r.me...@siemens.com

Thanks!
-roger
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] SPDX License IDs - moving forward

2013-10-23 Thread Meier, Roger
Hi Wolfgang!

 -Original Message-
 From: Wolfgang Denk [mailto:w...@denx.de]
 Sent: Donnerstag, 10. Oktober 2013 12:49
 To: u-boot@lists.denx.de
 Cc: Meier, Roger
 Subject: SPDX License IDs - moving forward

 Hallo,

 while working on converting more files to SPDX license IDs and
 discussing the whole approach with the SPDX team, a few ideas crossed
 my mind.  It would be very helpful if I gould get some feedback on
 these:


 I wonder if we should not take the idea even a step further.  So far
 we only focus on the license terms of the source code.  However,
 U-Boot is very flexible to configure, and as is it is not trvial to
 tell if a specific piece of code actually gets linked into the final
 product.  I wonder if we should turn the comment as we have it now
 into actual code, i. e. into a preprocessor macro that compiles the
 license ID into the generated object file (probably into a separate
 section so you can decide whether or not you want to include this
 ieven into the final binary image).  We could easily make the linker
 combine identical tags into a single entry, to the total memory
 overhead would be minimal.

 This would allow to easily find out which components have actually
 been built into the final product, so which licenses apply tho that.
 You don't have to bother about license terms for code that you don't
 actually use in your product, right?
Getting a report with files + licenses as build output would by awesome!
Part of binary and a license command would a very nice supplement.



 And there is another topic that's on my mind.  License terms for the
 source code are one thing, but there are is additional information
 that may be relevant when releasing a product, for example (known)
 patents or other intellectual property rights that may apply.  For
 example, despite the fact that all code to implement FAT/VFAT file
 system support is licensed under GPL-2.0+ in U-Boot, we know that
 Microsoft holds patents on parts of that technology, which may become
 an issue if you include FAT/VFAT support in your product.

 Should we also add similar tags to list known patents etc.?  for
 example, the FAT code could be augmented like that:

 SPDX-Patent-Notice: US5,579,517 US5,758,352 US5,745,902 US6,286,013 EP0618550

 [Of course I'm not sure if SPDX would cover such an entry; I'm just
 interested in feedback for the general idea.]
I really like this idea, had it also within my ideabox.

A perfect way to simplify this topic as well and I think it fits to the
idea of Software Package Data Exchange. If SPDX people agree on patent
info as part of further SPDX the tag name fits perfectly otherwise
just use License-Notice as a tag?


 Again, I tent to make this a preprocessor macro, so you can easily
 determine which (known) patents may apply to your final product.


 What do you think?  Does this make sense to you?
Yes!

The other thing within my ideabox is a SPDX-Copyright-Text tag.
What about that?

-roger


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v2] Merge and reformat boards.cfg and MAINTAINERS

2013-09-16 Thread Meier, Roger
Hi Albert

 Could you send thoses two fixes as as a proper, standalone git patch
 rather than a reply to another patch, so that they can be properly
 attributed to you?

I received this message from mailing list robot:
Message rejected. No base64 encoded MIME text parts allowed.
... I will try the setup another mail client soon.

So I did a resend here: http://patchwork.ozlabs.org/patch/274695/

Regards
Roger

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH] at91: add defines for reset type

2013-09-10 Thread Meier, Roger
Signed-off-by: Roger Meier r.me...@siemens.com
---
 arch/arm/include/asm/arch-at91/at91_rstc.h |7 +++
 1 file changed, 7 insertions(+)

diff --git a/arch/arm/include/asm/arch-at91/at91_rstc.h 
b/arch/arm/include/asm/arch-at91/at91_rstc.h
index 423cf51..a942342 100644
--- a/arch/arm/include/asm/arch-at91/at91_rstc.h
+++ b/arch/arm/include/asm/arch-at91/at91_rstc.h
@@ -38,4 +38,11 @@ typedef struct at91_rstc {
 
 #define AT91_RSTC_SR_NRSTL 0x0001
 
+#define AT91_RSTC_RSTTYP   (7  8)/* Reset Type */
+#define AT91_RSTC_RSTTYP_GENERAL   (0  8)
+#define AT91_RSTC_RSTTYP_WAKEUP(1  8)
+#define AT91_RSTC_RSTTYP_WATCHDOG  (2  8)
+#define AT91_RSTC_RSTTYP_SOFTWARE  (3  8)
+#define AT91_RSTC_RSTTYP_USER  (4  8)
+
 #endif
-- 
1.7.10.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot