1. 31 5月, 2008 1 次提交
  2. 28 4月, 2008 1 次提交
    • Y
      fbdev: powerpc: driver for Freescale 8610 and 5121 DIU · 9b53a9e2
      York Sun 提交于
      The following features are supported:
      plane 0 works as a regular frame buffer, can be accessed by /dev/fb0
      plane 1 has two AOIs (area of interest), can be accessed by /dev/fb1 and /dev/fb2
      plane 2 has two AOIs, can be accessed by /dev/fb3 and /dev/fb4
      Special ioctls support AOIs
      
      All /dev/fb* can be used as regular frame buffer devices, except hardware
      change can only be made through /dev/fb0.  Changing pixel clock has no effect
      on other fbs.
      
      Limitation of usage of AOIs:
      AOIs on the same plane can not be horizonally overlapped
      AOIs have horizonal order, i.e. AOI0 should be always on top of AOI1
      AOIs can not beyond phisical display area. Application should check AOI geometry
      before changing physical resolution on /dev/fb0
      
      required command line parameters to preallocate memory for frame buffer diufb.
      
      optional command line parameters to set modes and monitor
      video=fslfb:[resolution][,bpp][,monitor]
      Syntax:
      
      Resolution
      xres x yres-bpp@refresh_rate, the -bpp and @refresh_rate are optional
      eg, 1024x768, 1280x1024, 1280x1024-32, 1280x1024@60, 1280x1024-32@60, 1280x480-32@60
      
      Bpp
      bpp=32, bpp=24, or bpp=16
      
      Monitor
      monitor=0, monitor=1, monitor=2
      0 is DVI
      1 is Single link LVDS
      2 is Double link LVDS
      
      Note: switching monitor is a board feather, not DIU feather. MPC8610HPCD has three
      monitor ports to swtich to. MPC5121ADS doesn't have additional monitor port. So switching
      monirot port for MPC5121ADS has no effect.
      
      If compiled as a module, it takes pamameters mode, bpp, monitor with the same syntax above.
      Signed-off-by: NYork Sun <yorksun@freescale.com>
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9b53a9e2
  3. 25 4月, 2008 1 次提交
  4. 17 4月, 2008 2 次提交
  5. 15 4月, 2008 1 次提交
  6. 26 3月, 2008 1 次提交
    • D
      [POWERPC] Start removing linux,network-index in favour of aliases · ecc6cd73
      David Gibson 提交于
      This patch alters the bootwrapper for a number of machines (roubhly
      all 4xx based cuboot or treeboot platforms) to use aliases instead of
      the linux,network-index hack to work out which MAC address to attach
      to which ethernet device node.
      
      The now obsolete linux,network-index properties are removed from the
      corresponding device trees.  This won't break backwards compatiblity,
      because in cases where this fixup code is relevant, the device tree is
      part of the kernel image.
      
      The references to linux,network-index are removed from
      booting-without-of.txt.  Not only is it now deprecated, but as a hack
      applicable only when the device tree blob and fixup code were in the
      same image, this property never belonged in booting-without-of.txt
      which describes the interface between the kernel and firmware or
      bootloaders which produce a device tree.  By the time the device tree
      reaches the kernel, all the MAC addresses must be fully filled in.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NJosh Boyer <jwboyer@linux.vnet.ibm.com>
      ecc6cd73
  7. 07 2月, 2008 2 次提交
  8. 28 1月, 2008 4 次提交
  9. 24 1月, 2008 5 次提交
  10. 17 1月, 2008 2 次提交
  11. 09 1月, 2008 1 次提交
    • S
      [POWERPC] Xilinx: Update booting-without-of. · ab99eee8
      Stephen Neuendorffer 提交于
      This now better describes what the UBoot device tree generator
      actually does.  In particular:
      
      1) Nodes have a label derived from the device name, and a node name
      derived from a generic version of the device type, e.g. 'ethernet',
      'serial', etc.
      
      2) Usage of compound nodes (representing more than one device in the
      same IP) which actually works.  This requires having a valid
      compatible node, and all the other things that a bus normally has.
      I've chosen 'xlnx,compound' as the bus name to describe these compound
      nodes.
      
      In addition, I've clarified some of the language relating to how mhs
      nodes should be represent in the device tree.
      Signed-off-by: NStephen Neuendorffer <stephen.neuendorffer@xilinx.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      ab99eee8
  12. 14 12月, 2007 1 次提交
    • T
      [POWERPC] qe: add function qe_clock_source() · 174b0da2
      Timur Tabi 提交于
      Add function qe_clock_source() which takes a string containing the name of a
      QE clock source (as is typically found in device trees) and returns the
      matching enum qe_clock value.
      
      Update booting-without-of.txt to indicate that the UCC properties rx-clock
      and tx-clock are deprecated and replaced with rx-clock-name and tx-clock-name,
      which use strings instead of numbers to indicate QE clock sources.
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      174b0da2
  13. 12 12月, 2007 1 次提交
    • K
      [POWERPC] FSL: enet device tree cleanups · e77b28eb
      Kumar Gala 提交于
      * Removed address fields in ethernet nodes
      * Removed #address-cells, #size-cells from gianfar nodes
      * Added cell-index to gianfar and ucc ethernet nodes
      * Added enet[0..3] labels
      * Renamed compatible node for gianfar mdio to "fsl,gianfar-mdio"
      * Removed device_type = "mdio"
      
      The matching for gianfar mdio still supports the old "mdio"/"gianfar" combo
      but it is now considered deprecated.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      e77b28eb
  14. 06 12月, 2007 1 次提交
  15. 20 11月, 2007 1 次提交
  16. 08 11月, 2007 1 次提交
    • B
      [POWERPC] Fix cache line vs. block size confusion · 20474abd
      Benjamin Herrenschmidt 提交于
      We had an historical confusion in the kernel between cache line
      and cache block size. The former is an implementation detail of
      the L1 cache which can be useful for performance optimisations,
      the later is the actual size on which the cache control
      instructions operate, which can be different.
      
      For some reason, we had a weird hack reading the right property
      on powermac and the wrong one on any other 64 bits (32 bits is
      unaffected as it only uses the cputable for cache block size
      infos at this stage).
      
      This fixes the booting-without-of.txt documentation to mention
      the right properties, and fixes the 64 bits initialization code
      to look for the block size first, with a fallback to the line
      size if the property is missing.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      20474abd
  17. 01 11月, 2007 1 次提交
  18. 11 10月, 2007 1 次提交
    • D
      Device tree aware EMAC driver · 1d3bb996
      David Gibson 提交于
      Based on BenH's earlier work, this is a new version of the EMAC driver
      for the built-in ethernet found on PowerPC 4xx embedded CPUs.  The
      same ASIC is also found in the Axon bridge chip.  This new version is
      designed to work in the arch/powerpc tree, using the device tree to
      probe the device, rather than the old and ugly arch/ppc OCP layer.
      
      This driver is designed to sit alongside the old driver (that lies in
      drivers/net/ibm_emac and this one in drivers/net/ibm_newemac).  The
      old driver is left in place to support arch/ppc until arch/ppc itself
      reaches its final demise (not too long now, with luck).
      
      This driver still has a number of things that could do with cleaning
      up, but I think they can be fixed up after merging.  Specifically:
      	- Should be adjusted to properly use the dma mapping API.
      Axon needs this.
      	- Probe logic needs reworking, in conjuction with the general
      probing code for of_platform devices.  The dependencies here between
      EMAC, MAL, ZMII etc. make this complicated.  At present, it usually
      works, because we initialize and register the sub-drivers before the
      EMAC driver itself, and (being in driver code) runs after the devices
      themselves have been instantiated from the device tree.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      1d3bb996
  19. 08 10月, 2007 1 次提交
  20. 05 10月, 2007 2 次提交
    • S
      [POWERPC] cpm: Describe multi-user ram in its own device node. · 15f8c604
      Scott Wood 提交于
      The way the current CPM binding describes available multi-user (a.k.a.
      dual-ported) RAM doesn't work well when there are multiple free regions,
      and it doesn't work at all if the region doesn't begin at the start of
      the muram area (as the hardware needs to be programmed with offsets into
      this area).  The latter situation can happen with SMC UARTs on CPM2, as its
      parameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn't
      support moving it.
      
      It is now described with a muram node, similar to QE.  The current CPM
      binding is sufficiently recent (i.e. never appeared in an official release)
      that compatibility with existing device trees is not an issue.
      
      The code supporting the new binding is shared between cpm1 and cpm2, rather
      than remain separated.  QE should be able to use this code as well, once
      minor fixes are made to its device trees.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      15f8c604
    • S
      [POWERPC] Document local bus nodes in the device tree, and update cuboot-pq2. · 96fca1de
      Scott Wood 提交于
      The localbus node is used to describe devices that are connected via a chip
      select or similar mechanism.  The advantages over placing the devices under
      the root node are that it can be probed without probing other random things
      under the root, and that the description of which chip select a given device
      uses can be used to set up mappings if the firmware failed to do so in a
      useful manner.
      
      cuboot-pq2 is updated to match the binding; previously, it called itself
      chipselect rather than localbus, and used phandle linkage between the
      actual bus node and the control node (the current agreement is to simply use
      the fully-qualified address of the control registers, and ignore the overlap
      with the IMMR node).
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      96fca1de
  21. 04 10月, 2007 1 次提交
    • S
      [POWERPC] Introduce new CPM device bindings. · e631ae3b
      Scott Wood 提交于
      This introduces a new device binding for the CPM and other devices on
      these boards.  Some of the changes include:
      
      1. Proper namespace scoping for Freescale compatibles and properties.
      
      2. Use compatible rather than things like device_type and model
      to determine which particular variant of a device is present.
      
      3. Give the drivers the relevant CPM command word directly, rather than
      requiring it to have a lookup table based on device-id, SCC v. SMC, and
      CPM version.
      
      4. Specify the CPCR and the usable DPRAM region in the CPM's reg property.
      
      Boards that do not require the legacy bindings should select
      CONFIG_PPC_CPM_NEW_BINDING to enable the of_platform CPM devices. Once
      all existing boards are converted and tested, the config option can
      become default y to prevent new boards from using the old model.  Once
      arch/ppc is gone, the config option can be removed altogether.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Acked-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      e631ae3b
  22. 13 9月, 2007 1 次提交
  23. 19 7月, 2007 1 次提交
  24. 03 7月, 2007 2 次提交
  25. 28 6月, 2007 1 次提交
    • D
      [POWERPC] In booting-without-of.txt, clarify that properties must precede subnodes · eff2ebd2
      David Gibson 提交于
      A strict reading of the flattened device tree format defined in
      booting-without-of.txt does in fact require that all the tags defining
      properties for a node go before any definitions of subnodes, however
      it's not particularly emphasised.  Although allowing intermingled
      properties and subnodes would not be ambiguous in meaning, the kernel
      parser does currently require that properties precede subnodes.
      Furthermore, keeping this constraint makes life easier for various
      device tree scanning tools.
      
      Therefore, re-emphasise in booting-without-of.txt that this is a
      strict requirement of the flattened device tree format.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      eff2ebd2
  26. 07 6月, 2007 2 次提交
  27. 09 5月, 2007 1 次提交
新手
引导
客服 返回
顶部