19 Feb, 2019

1 commit

  • This commit converts the brxre1 board to DM,
    for this we have todo following things:

    - add a devicetree-file for this board
    - drop all obsolete settings from board header-file
    - use dm_i2c_xxx calls for read/write to the resetcontroller
    - request gpios before operate them

    Serues-cc: trini@konsulko.com
    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     

09 Feb, 2019

1 commit


20 Jul, 2018

11 commits

  • Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • - add a devicetree for each variant (mmc, spi, nand)
    - drop unneeded code from board and bur/common
    - drop unneeded stuff from config header files
    - minor adaptions to be compliant with driver model (requesting gpio,..)
    - harmonize the commandset over all brppt1 targets

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • With this commit we do:

    - set the bootdelay in all brppt1 defconfigs to 0, this makes
    development easier, since we can break into serial console.

    - move CONFIG_BOOTCOMMAND from header file to defconfig

    - introduce b_mode variable for selecting the final boot-target.
    This b_mode represents the boot-switch, which can found on most b&r
    targets. On the brppt1 this boot-switch is derived from some gpio and
    the bootcounter within the RTC block, making it so possible to force
    a boot-target (as example for repair-case).

    - refactor the environment for booting new flexible way
    primary we want to get some bootscr.img within the mass-storage,
    this script then loads everything needed for the boot.
    For legacy reason we implement the t30lgcy#x boot targets, booting the
    already delivered linux-images.

    - make space for the cfgscr within mtdparts on brppt1_nand

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • On other OS, not one provided by B&R, it is not guaranteed that there
    are factory-settings within a devicetree. So we must not treat the
    absence of them as error.
    Further we've the fact that on different version of the device-tree
    files there are different namings of the factory-settings, we consider
    this with searching for an alternative name.

    changing things as following:

    - don't treat as error if the bootloader version cannot written into
    devicetree.

    - since the naming of the factory-settings are different in different
    versions of the provided device-tree we search for the alternate name
    "/fset"

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • The falcon mode was never used on this board, there is also no plan to
    use it. So drop this dead code.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • If a board-code calls the pmicsetup(u32 mpupll) with a mpupll value
    != 0 it wants to force some frequency with the value provided by mpupll.
    Setting up 1 GHz is wrong here.

    Nobody did take notice about that yet, since every board calls this
    function with zero.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • This interface names may vary over different products, to consider this
    fact we replace the interface label "IF1" and "IF2" on the summary
    screen with some more generic wording "MAC1" and "MAC2".

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • On this linux target long time ago the OS is using DRM driver for
    handling video output, the pre initialization of u-boot and the display
    summary screen is obsolete. With this patch we drop the LCD-support from
    thisd board.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • Since we're going to drop LCD-support on brppt1 boards, we have to make
    this stuff here optional and remove the #error path.

    We also move out the ft_board_setup(...) from this #ifdef because
    there's no relationship with the LCD-code and on the other hand this is
    still needed in future even with LCD-support off.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • The linux systems running on the brppt1 targets are using modern DRM
    drivers since long time ago. Further we are going to drop the LCD
    support completely on this board, so the simple-framebuffer setup
    becomes obsolete.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • This patch drops the lcd-screen setup, the summary screen and getting
    mac-addresses based on a previous loaded device-tree for linux targets.
    Selecting those linux target is simple, since we have only the brppt1.

    In detail we do:
    - drop the common lcd-setup code which relys on a fdt_blob
    - drop the common dtb loading mechanism
    - drop the now obsolete CONFIG_USE_FDT from board header and whitelist.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     

07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

09 Apr, 2018

1 commit

  • In order that we can use eth_env_* even when CONFIG_NET isn't set, move
    these functions to environment code from net code.

    This fixes failures such as:

    board/ti/am335x/built-in.o: In function `board_late_init':
    board/ti/am335x/board.c:752: undefined reference to `eth_env_set_enetaddr'
    u-boot/board/ti/am335x/board.c:766: undefined reference to `eth_env_set_enetaddr'

    which caters for use cases such as:

    commit f411b5cca48f ("board: am335x: Always set eth/eth1addr environment
    variable")

    when Ethernet is required in Linux, but not U-Boot.

    Signed-off-by: Alex Kiernan

    Alex Kiernan
     

11 Jan, 2018

2 commits


16 Aug, 2017

4 commits


12 Jul, 2017

1 commit

  • As part of preparation for nand DM conversion the new API has been
    introduced to remove direct access to nand_info array. So, use it here
    instead of accessing to nand_info array directly.

    Signed-off-by: Grygorii Strashko
    Reviewed-by: Hannes Schmelzer
    Reviewed-by: Simon Glass

    Grygorii Strashko
     

16 Jun, 2017

1 commit

  • since commit

    'd5abcf94c7123167725fc22ace342f0d455093c1' -
    ti: boot: Register the MMC controllers in SPL in the same way as in u-boot

    MMC boot on brxre1 board is broken, with this commit we make our board
    working again.

    Signed-off-by: Hannes Schmelzer
    Reviewed-by: Tom Rini
    Reviewed-by: Jean-Jacques Hiblot

    Hannes Schmelzer
     

15 May, 2017

1 commit


06 May, 2017

1 commit


20 Mar, 2017

1 commit

  • To keep a consistent MMC device mapping in SPL and in u-boot, let's
    register the MMC controllers the same way in u-boot and in the SPL.
    In terms of boot time, it doesn't hurt to register more controllers than
    needed because the MMC device is initialized only prior being accessed for
    the first time.
    Having the same device mapping in SPL and u-boot allows us to use the
    environment in SPL whatever the MMC boot device.

    Signed-off-by: Jean-Jacques Hiblot

    Jean-Jacques Hiblot
     

25 Jun, 2016

2 commits


04 Jun, 2016

1 commit

  • nand_info[] is now an array of pointers, with the actual mtd_info
    instance embedded in struct nand_chip.

    This is in preparation for syncing the NAND code with Linux 4.6,
    which makes the same change to struct nand_chip. It's in a separate
    commit due to the large amount of changes required to accommodate the
    change to nand_info[].

    Signed-off-by: Scott Wood

    Scott Wood
     

25 Feb, 2016

1 commit


13 Nov, 2015

1 commit

  • Since we don't have for sure a valid IP-setup during
    board_late_init(...) because it maybe allready stored in environment or
    not, we cannot form a proper vxWorks bootline at this place.

    So we move to the way, forming the bootline just before
    executing/launching vxWorks. To do this we use the bootvx command
    instead go.

    We only have to form the "othbootargs" environment variable, the rest is
    done pretty good by the "bootvx" commannd.

    Signed-off-by: Hannes Schmelzer
    Reviewed-by: Bin Meng

    Hannes Petermaier
     

12 Sep, 2015

1 commit

  • To simplify and having a common default IP-setup on all B&R boards we
    introduce an environment variable "brdefaultip" which does following.

    Test if ${ipaddr} is empty, if yes it set's up some defaults:
    - ipaddr : 192.168.60.1
    - netmask : 255.255.255.0
    - gatewayip: 192.168.60.254
    - serverip : 192.168.60.254

    This environment is ran from CONFIG_PREBOOT.

    All other "tricks" are dropped.

    Signed-off-by: Hannes Schmelzer
    Reviewed-by: Tom Rini
    Acked-by: Joe Hershberger

    Hannes Petermaier
     

19 Jun, 2015

1 commit


28 May, 2015

1 commit


09 May, 2015

3 commits

  • usbupdate in real does allways load some script from usb-storage and execute
    it, on all B&R targets.

    So we do following 2 things:
    - rename it to what it really does
    - move it from boards to common environment

    Signed-off-by: Hannes Petermaier

    Hannes Petermaier
     
  • Since the used AM3352 SoC doesn't have GPU it isn't allways necessary to build
    in complete drm-stuff into linux kernel. In very small applications only we use
    the simple-framebuffer.

    So we have 2 use-cases:
    - device operating on drm-driver (let simplefb node disabled)
    - device operating on simplefb-driver (activate simplefb node and reserve mem)

    The decision is made by means of "simplefb" environment variable.

    simplefb = 0
    we don't enable the (maybe) existing simplefb node and all the rest around
    display is up to the linux-kernel. We just disable the backlight, beceause we
    do not want see the flicker during take over of drm-driver.

    simplefb = 1
    we enable the (maybe) existing simplefb node and reserve framebuffers size
    in memory.

    Signed-off-by: Hannes Petermaier

    Hannes Petermaier
     
  • We take use of the new LCD_ROTATION feature.
    The information about how the display is rotated is taken from B&R specific
    (/factory-settings/rotation) information in the devicetree.

    The information there is stored as string (cw, ud, ccw, none) since starting
    support of this devices and cannot be changed, so we have to convert it into

    none = 0
    cw = 1
    ud = 2
    ccw = 3

    Signed-off-by: Hannes Petermaier

    Hannes Petermaier
     

23 Apr, 2015

3 commits