Skip to content
  1. Dec 09, 2013
  2. Dec 02, 2013
  3. Nov 13, 2013
  4. Nov 11, 2013
  5. Nov 05, 2013
  6. Nov 04, 2013
  7. Nov 01, 2013
  8. Oct 31, 2013
    • Arnaud Ebalard's avatar
      ARM: mvebu: Add Netgear ReadyNAS 104 board · 45e8815f
      Arnaud Ebalard authored
      
      
      Main hardware parts of the (Armada 370 based) NETGEAR ReadyNAS 104 are
      supported by mainline kernel (USB 3.0 rear ports, USB 2.0 front port,
      Gigabit controller and PHYs, serial port, LEDs, buttons, SATA ports,
      G762 fan controller) and referenced in provided .dts file. Some additonal
      work remains for:
      
       - Intersil ISL12057 I2C RTC and Alarm chip: working driver but needs
         to be splitted for submission of RTC part first;
       - Front LCD (Winstar 1602G): driver needs to be written
       - Armada NAND controller (to access onboard 128MB of NAND): support
         being pushed by @free-electrons people
       - 4 front SATA LEDs controlled via GPIO brought by NXP PCA9554:
         driver is available upstream. Not referenced/tested yet.
      
      but the device is usable w/o those.
      
      Signed-off-by: default avatarArnaud Ebalard <arno@natisbad.org>
      Acked-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      45e8815f
    • Hiroshi Doyu's avatar
      ARM: tegra: fix Tegra114 IOMMU register address · 4cca9593
      Hiroshi Doyu authored
      
      
      The IOMMU node's reg property contains completely bogus values! Somehow,
      this had no practical effect, despite the fact the IOMMU driver appears
      to be writing to those registers. I suppose that since no HW modules is
      actually at that address, the writes simply had no effect.
      
      Note that I'm not CCing stable here, even though the problem exists as
      far back as v3.9, simply because this patch doesn't fix any observed
      issue, and I don't want to run the risk of suddenly writing to some
      registers and causing a regression.
      
      Signed-off-by: default avatarHiroshi Doyu <hdoyu@nvidia.com>
      [swarren, wrote commit description]
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      4cca9593
    • Thomas Petazzoni's avatar
      ARM: kirkwood: add support for OpenBlocks A7 platform · f24b56cb
      Thomas Petazzoni authored
      
      
      The OpenBlocks A7 board is designed and sold by PlatHome, and based on
      a Kirkwood 6283 Marvell SoC. It is quite similar to the OpenBlocks A6
      already supported in the kernel, with the following main differences:
      
       - The A6 uses a RTC on I2C, while the A7 uses the internal SoC RTC.
      
       - The A6 has one Ethernet port, while the A7 has two Ethernet ports
      
       - The A6 has only one USB port, while the A7 integrates a USB hub,
         which provides two front-side USB port, and an internal USB port as
         well.
      
       - The A6 has 512 MB of RAM, while the A7 has 1 GB of RAM.
      
       - Slightly different GPIOs for some functions.
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Acked-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Acked-by: default avatarGregory CLEMENT <gregory.clement@free-electrons.com>
      Signed-off-by: default avatarJason Cooper <jason@lakedaemon.net>
      f24b56cb
  9. Oct 30, 2013
  10. Oct 29, 2013