1. 14 7月, 2008 5 次提交
  2. 09 7月, 2008 1 次提交
    • G
      ibm_newemac: Parameterize EMAC Multicast Match Handling · 05781ccd
      Grant Erickson 提交于
      Various instances of the EMAC core have varying: 1) number of address
      match slots, 2) width of the registers for handling address match slots,
      3) number of registers for handling address match slots and 4) base
      offset for those registers.
      
      As the driver stands today, it assumes that all EMACs have 4 IAHT and
      GAHT 32-bit registers, starting at offset 0x30 from the register base,
      with only 16-bits of each used for a total of 64 match slots.
      
      The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
      core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
      from the register base, with ALL 32-bits of each used for a total of
      256 match slots.
      
      This adds a new compatible device tree entry "emac4sync" and a new,
      related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
      and inlines which supply the appropriate parameterized value based on
      the presence or absence of the EMAC4SYNC feature.
      
      The code has further been reworked where appropriate to use those macros
      and inlines.
      
      In addition, the register size passed to ioremap is now taken from the
      device tree:
      
      	c4 for EMAC4SYNC cores
      	74 for EMAC4 cores
      	70 for EMAC cores
      
      rather than sizeof (emac_regs).
      
      Finally, the device trees have been updated with the appropriate compatible
      entries and resource sizes.
      
      This has been tested on an AMCC Haleakala board such that: 1) inbound
      ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
      and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
      'haleakala.local' to those same systems in the '.local' domain via MDNS
      now work.
      Signed-off-by: NGrant Erickson <gerickson@nuovations.com>
      Acked-by: NJeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      05781ccd
  3. 28 6月, 2008 1 次提交
  4. 11 6月, 2008 4 次提交
  5. 10 6月, 2008 5 次提交
  6. 09 6月, 2008 2 次提交
  7. 03 6月, 2008 5 次提交
  8. 31 5月, 2008 1 次提交
  9. 29 5月, 2008 3 次提交
  10. 20 5月, 2008 1 次提交
  11. 13 5月, 2008 3 次提交
  12. 07 5月, 2008 1 次提交
  13. 02 5月, 2008 1 次提交
  14. 30 4月, 2008 1 次提交
  15. 29 4月, 2008 3 次提交
  16. 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
  17. 25 4月, 2008 1 次提交
  18. 17 4月, 2008 1 次提交