Eric Lee / smarc-fsl-linux-kernel

10 Jan, 2012

3 commits

08 Nov, 2011

1 commit

  • e0d65113a   Merge git://git.infradead.org/mtd-2.6 ... Browse Code »

    * git://git.infradead.org/mtd-2.6: (226 commits)
    mtd: tests: annotate as DANGEROUS in Kconfig
    mtd: tests: don't use mtd0 as a default
    mtd: clean up usage of MTD_DOCPROBE_ADDRESS
    jffs2: add compr=lzo and compr=zlib options
    jffs2: implement mount option parsing and compression overriding
    mtd: nand: initialize ops.mode
    mtd: provide an alias for the redboot module name
    mtd: m25p80: don't probe device which has status of 'disabled'
    mtd: nand_h1900 never worked
    mtd: Add DiskOnChip G3 support
    mtd: m25p80: add EON flash EN25Q32B into spi flash id table
    mtd: mark block device queue as non-rotational
    mtd: r852: make r852_pm_ops static
    mtd: m25p80: add support for at25df321a spi data flash
    mtd: mxc_nand: preset_v1_v2: unlock all NAND flash blocks
    mtd: nand: switch `check_pattern()' to standard `memcmp()'
    mtd: nand: invalidate cache on unaligned reads
    mtd: nand: do not scan bad blocks with NAND_BBT_NO_OOB set
    mtd: nand: wait to set BBT version
    mtd: nand: scrub BBT on ECC errors
    ...

    Fix up trivial conflicts:
    - arch/arm/mach-at91/board-usb-a9260.c
    Merged into board-usb-a926x.c
    - drivers/mtd/maps/lantiq-flash.c
    add_mtd_partitions -> mtd_device_register vs changed to use
    mtd_device_parse_register.

    Linus Torvalds
     

01 Nov, 2011

1 commit

16 Oct, 2011

1 commit

  • d5de1907d   mtd: provide an alias for the redboot module name ... Browse Code »
    1

    parse_mtd_partitions takes a list of partition types; if the driver
    isn't loaded, it attempts to load it, and then it grabs the partition
    parser. For redboot, the module name is "redboot.ko", while the parser
    name is "RedBoot". Since modprobe is case-sensitive, attempting to
    modprobe "RedBoot" will never work. I suspect the embedded systems that
    make use of redboot just always manually loaded redboot prior to loading
    their specific nand chip drivers (or statically compiled it in).

    Signed-off-by: Andres Salomon
    Signed-off-by: Artem Bityutskiy
    Cc: stable@kernel.org

    Andres Salomon
     

11 Sep, 2011

1 commit

  • c79753301   mtd: abstract last MTD partition parser argument ... Browse Code »
    43

    Encapsulate last MTD partition parser argument into a separate
    structure. Currently it holds only 'origin' field for RedBoot parser,
    but will be extended in future to contain at least device_node for OF
    devices.

    Amended commentary to make kerneldoc happy

    Signed-off-by: Dmitry Eremin-Solenikov
    Signed-off-by: Artem Bityutskiy

    Dmitry Eremin-Solenikov
     

09 Aug, 2010

1 commit

11 Jul, 2008

1 commit

07 Jun, 2008

1 commit

05 Jun, 2008

1 commit

  • 59018b6d2   MTD/JFFS2: remove CVS keywords ... Browse Code »

    Once upon a time, the MTD repository was using CVS.

    This patch therefore removes all usages of the no longer updated CVS
    keywords from the MTD code.

    This also includes code that printed them to the user.

    Signed-off-by: Adrian Bunk
    Signed-off-by: David Woodhouse

    Adrian Bunk
     

29 Oct, 2007

1 commit

10 Feb, 2007

2 commits

09 Feb, 2007

1 commit

08 Dec, 2006

1 commit

  • f33665d93   [MTD] Support combined RedBoot FIS directory and configuration area ... Browse Code »

    RedBoot supports storing the FIS directory and the RedBoot
    configuration area in the same block of flash memory. This is
    not the most common RedBoot configuration, but it is used on
    commercially available boards supported by the kernel.

    A recent patch to mtd/redboot.c (http://lkml.org/lkml/2006/3/20/410)
    which corrected the skipping of deleted table entries has exposed the
    latent problem of the kernel redboot parser running off the end of the
    FIS directory and interpreting the RedBoot configuration information
    as table entries.

    This patch terminates the table parsing when the first truly empty
    entry is found (table entry deletion only clears the first byte of the
    name, so two cleared bytes in a row indicates the end of the table),
    thereby supporting the combined redboot FIS directory and RedBoot
    configuration information flash layout scenario.

    Signed-off-by: Rod Whitby
    Signed-off-by: David Woodhouse

    Rod Whitby
     

01 Dec, 2006

1 commit

29 Nov, 2006

1 commit

17 May, 2006

1 commit

  • b020bb7d3   [MTD] Fix build warnings in RedBoot MTD partition parser. ... Browse Code »

    Fix build warnings from drivers/mtd/redboot.c due to
    use of `unsigned long` in `struct fis_image_desc` for
    fields being passed to swab32s() which expects __u32 *

    Change the entries to uint32_t to make them compatible
    with the swab32s() function

    Signed-off-by: Ben Dooks
    Signed-off-by: David Woodhouse

    Ben Dooks
     

01 Apr, 2006

1 commit

  • 84e699e6e   [PATCH] mtd/redboot: Handle holes in fis table ... Browse Code »

    Redboot simply sets the first character of a fis entry to 0xff on "fis
    delete". The kernel redboot parser stops parsing on such an entry, and
    without this patch any entries after a deleted image would not be detected.

    Signed-off-by: Peter Korsgaard
    Cc: Thomas Gleixner
    Acked-by: David Woodhouse
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Peter Korsgaard
     

03 Mar, 2006

1 commit

01 Mar, 2006

1 commit

  • 9cff3372b   [PATCH] drivers/mtd/redboot.c: recognise a foreign byte sex partition table ... Browse Code »

    The RedBoot boot loader writes flash partition tables containing native
    byte sex 32 bit values. When booting an opposite byte sex kernel (e.g. an
    LE kernel from BE RedBoot) the current MTD driver fails to handle the
    partition table and therefore is unable to generate the correct partition
    map for the flash.

    So far as I am aware this problem is ARM specific, because only ARM
    supports software change of the CPU (memory system) byte sex, however the
    partition table parsing is in generic MTD code. The patch below has been
    tested on NSLU2 (an IXP4XX based system) with a patch,
    10-ixp4xx-copy-from.patch (submitted to linux-arm-kernel - it's ARM
    specific) required to make the maps/ixp4xx.c driver work with an LE kernel.

    Builds of the patched system are in the 'unstable' release of OpenSlug and
    UcSlugC available from www.nslu2-linux.org. These builds are BE, the
    archives at www.nslu2-linux.org and www.handhelds.org (see
    monotone.vanille.de) can be built LE (currently DISTRO targets
    nslu-ltu.conf for LE thumb uclibc (32 bit kernel) and nslu2-lau.conf,
    nslu2-lag.conf for LE arm uclibc/glibc) and this patch has been tested
    extensively will both BE and LE systems on the NSLU2 (including swapping
    between BE and LE by reflashing from both RedBoot and Linux).

    The patch recognises that the FIS directory (the partition table) is
    byte-reversed by examining the partition table size, which is known to be
    one erase block (this is an assumption made elsewhere in redboot.c). If
    the size matches the erase block after byte swapping the value then
    byte-reversal is assumed, if not no further action is taken. The patched
    code is fail safe; should redboot.c be changed to support a partition table
    with a modified size field the test will fail and the partition table will
    be assumed to have the host byte sex.

    If byte-reversal is detected the patch byte swaps the remainder of the 32
    bit fields in the copy of the table; this copy is then used to set up the
    MTD partition map.

    Signed-off-by: John Bowler
    Cc: David Woodhouse
    Cc: Thomas Gleixner
    Cc: Martin Michlmayr
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    John Bowler
     

07 Nov, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds