13 Aug, 2013

1 commit


24 Jul, 2013

1 commit


04 Feb, 2013

1 commit

  • CONFIG_ARM_DCC_MULTI should be also removed in the patch
    "serial: Remove CONFIG_SERIAL_MULTI from serial drivers"
    (sha1: a3827250606895ec2dd4b8d867342b7cabf3692f)
    Because the driver defines serial_* functions
    which cause conflict with serial.c (multiple definition of serial_*)

    Removing CONFIG_SERIAL_MULTI function also require to define
    default_serial_console for cases where another serial driver
    is not available in the system.

    Signed-off-by: Michal Simek
    Acked-by: Marek Vasut

    Michal Simek
     

01 Dec, 2012

1 commit

  • This patch builds upon the recently introduced CBMEM console
    feature of coreboot.

    CBMEM console uses a memry area allocated by coreboot to store
    the console output. The memory area has a certain structure,
    which allows to determine where the buffer is, the buffer size
    and the location of the pointer in the buffer. This allows
    different phases of the firmware (rom based coreboot, ram based
    coreboot, u-boot after relocation with this change) to keep
    adding text to the same buffer.

    Note that this patch introduces a new console driver and adds the
    driver to the list of drivers to be used for console output, i.e.
    it engages only after u-boot relocates. Usiong CBMEM console for
    capturing the pre-relocation console output will be done under a
    separate change.

    >From Linux, run the cbmem.py utility (which is a part of the coreboot
    package) to see the output, e.g.:

    vvvvvvvvvvvvvvvvv
    SCSI: AHCI 0001.0300 32 slots 6 ports ? Gbps 0xf impl SATA mode
    flags: 64bit ilck stag led pmp pio
    ...
    Magic signature found
    Kernel command line: "cros_secure quiet loglevel=1 console=tty2...
    ^^^^^^^^^^^^^^^^^

    Note that the entire u-boot output fits into the buffer only if
    the coreboot log level is reduced from the most verbose. Ether
    the buffer size will have to be increased, or the coreboot
    verbosity permanently reduced.

    Signed-off-by: Vadim Bendebury
    Signed-off-by: Simon Glass

    Vadim Bendebury
     

23 Jun, 2011

1 commit

  • The 'trab' board configuration is broken, and there is nobody who is
    interested and willing to fix it. Drop it.

    This includes support for VFD displays which have always been used by
    this board only.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

29 Nov, 2010

1 commit


19 Jul, 2009

1 commit


18 Jul, 2009

1 commit

  • So far the console API uses the following naming convention:

    ======Extract======
    typedef struct device_t;

    int device_register (device_t * dev);
    int devices_init (void);
    int device_deregister(char *devname);
    struct list_head* device_get_list(void);
    device_t* device_get_by_name(char* name);
    device_t* device_clone(device_t *dev);
    =======

    which is too generic and confusing.

    Instead of using device_XX and device_t we change this
    into stdio_XX and stdio_dev

    This will also allow to add later a generic device mechanism in order
    to have support for multiple devices and driver instances.

    Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD

    Edited commit message.

    Signed-off-by: Wolfgang Denk

    Jean-Christophe PLAGNIOL-VILLARD