1. 05 12月, 2008 1 次提交
    • S
      sparc: prepare kernel/ for unification · d670bd4f
      Sam Ravnborg 提交于
      o sparc32 files with identical names to sparc64 renamed to <name>_32.S
      o introduced a few Kconfig helpers to simplify Makefile logic
      o refactored Makefile to prepare for unification
        - use obj-$(CONFIG_SPARC32) for sparc32 specific files
        - use <name>_$(BITS) for files where sparc64 has a _64 variant
        - sparc64 directly include a few files where sparc32 builds them,
          refer to these files directly (no BITS)
        - sneaked in -Werror as used by sparc64
      o modified sparc/Makefile to use the new names for head/init_task
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d670bd4f
  2. 13 11月, 2008 1 次提交
  3. 11 9月, 2008 1 次提交
  4. 03 9月, 2008 1 次提交
  5. 30 8月, 2008 1 次提交
  6. 29 8月, 2008 3 次提交
  7. 26 8月, 2008 1 次提交
  8. 25 8月, 2008 1 次提交
  9. 09 2月, 2008 1 次提交
  10. 18 10月, 2007 1 次提交
  11. 14 10月, 2007 1 次提交
  12. 21 7月, 2007 1 次提交
  13. 20 7月, 2007 3 次提交
  14. 26 4月, 2007 1 次提交
  15. 03 3月, 2007 2 次提交
  16. 10 12月, 2006 1 次提交
  17. 27 10月, 2006 1 次提交
  18. 04 10月, 2006 1 次提交
  19. 22 7月, 2006 1 次提交
  20. 13 7月, 2006 2 次提交
    • D
      [SPARC]: Fix OF register translations under sub-PCI busses. · a83f9823
      David S. Miller 提交于
      There is an implicit assumption in the code that ranges will translate
      to something that can fit in 2 32-bit cells, or a 64-bit value.  For
      certain kinds of things below PCI this isn't necessarily true.
      
      Here is what the relevant OF device hierarchy looks like for one of
      the serial controllers on an Ultra5:
      
          Node 0xf005f1e0
              ranges:      00000000.00000000.00000000.000001fe.01000000.00000000.01000000
                           01000000.00000000.00000000.000001fe.02000000.00000000.01000000
                           02000000.00000000.00000000.000001ff.00000000.00000001.00000000
                           03000000.00000000.00000000.000001ff.00000000.00000001.00000000
              device_type:  'pci'
              model:  'SUNW,sabre'
      
              Node 0xf005f9d4
                  device_type:  'pci'
                  model:  'SUNW,simba'
      
                 Node 0xf0060d24
                      ranges:  00000010.00000000 82010810.00000000.f0000000 01000000
      			 00000014.00000000 82010814.00000000.f1000000 00800000
                      name:  'ebus'
      
                      Node 0xf0062dac
                          reg:  00000014.003083f8.00000008 --> 0x1ff.f13083f8
                          device_type:  'serial'
                          name:  'su'
      
      So the correct translation here is:
      
      1) Match "su" register to second ranges entry of 'ebus', which translates
         into a PCI triplet "82010814.00000000.f1000000" of size 00800000, which
         gives us "82010814.00000000.f13083f8".
      
      2) Pass-through "SUNW,simba" since it lacks ranges property
      
      3) Match "82010814.00000000.f13083f8" to third ranges property of PCI
         controller node 'SUNW,sabre', and we arrive at the final physical
         MMIO address of "0x1fff13083f8".
      
      Due to the 2-cell assumption, we couldn't translate to a PCI 3-cell
      value, and we couldn't perform a pass-thru on it either.
      
      It was easiest to just stop splitting the ranges application operation
      between two methods, ->map and ->translate, and just let ->map do all
      the work.  That way it would work purely on 32-bit cell arrays instead
      of having to "return" some value like a u64.
      
      It's still not %100 correct because the out-of-range check is still
      done using the 64 least significant bits of the range and address.
      But it does work for all the cases I've thrown at it so far.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a83f9823
    • A
      [SPARC64]: of_device_register() error checking fix · 6cc8b6f5
      Andrew Morton 提交于
      device_create_file() can fail.  This causes the sparc64 compile to
      fail when my fanatical __must_check patch is applied, due to -Werror.
      
      [ Added necessary identical fix for sparc32. -DaveM]
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6cc8b6f5
  21. 30 6月, 2006 3 次提交
  22. 26 6月, 2006 1 次提交
  23. 24 6月, 2006 2 次提交
  24. 23 3月, 2006 1 次提交
  25. 14 1月, 2006 1 次提交
  26. 31 10月, 2005 1 次提交
  27. 06 10月, 2005 1 次提交
  28. 23 9月, 2005 1 次提交
    • B
      [PATCH] ppc64: SMU driver update & i2c support · 0365ba7f
      Benjamin Herrenschmidt 提交于
      The SMU is the "system controller" chip used by Apple recent G5 machines
      including the iMac G5.  It drives things like fans, i2c busses, real time
      clock, etc...
      
      The current kernel contains a very crude driver that doesn't do much more
      than reading the real time clock synchronously.  This is a completely
      rewritten driver that provides interrupt based command queuing, a userland
      interface, and an i2c/smbus driver for accessing the devices hanging off
      the SMU i2c busses like temperature sensors.  This driver is a basic block
      for upcoming work on thermal control for those machines, among others.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Jean Delvare <khali@linux-fr.org>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0365ba7f
  29. 30 8月, 2005 1 次提交
  30. 07 7月, 2005 1 次提交
  31. 21 6月, 2005 1 次提交