1. 04 Oct, 2006 1 commit
  2. 21 Jul, 2006 1 commit
    • David S. Miller's avatar
      [SPARC64]: Fix more of_device layer IRQ bugs, and correct PROMREG_MAX. · 46ba6d7d
      David S. Miller authored
      Sabre and Psycho PCI controllers can have partial interrupt-map
      properties, meaning that on-board devices don't match up to any
      entries.  Instead, they are fully specified from the beginning and
      we should pass them directly to the IRQ translator as-is.
      Also, fill in the necessary translator slots for the "graphics"
      and "expansion UPA" interrupts on Sabre, Psycho, and SYSIO SBUS.
      Increase PROMREG_MAX to 24, as seen on SUNW,ffb devices.
      Finally, prevent accidentally writing past the end of the of_device
      struct resource[] and irqs[] arrays.  Spit out a log message when
      we ignore some entries because there are too many of them.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  3. 13 Jul, 2006 2 commits
    • David S. Miller's avatar
      [SPARC]: Fix OF register translations under sub-PCI busses. · a83f9823
      David S. Miller authored
      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
              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: default avatarDavid S. Miller <davem@davemloft.net>
    • Andrew Morton's avatar
      [SPARC64]: of_device_register() error checking fix · 6cc8b6f5
      Andrew Morton authored
      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: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  4. 30 Jun, 2006 1 commit
  5. 29 Jun, 2006 3 commits
  6. 26 Jun, 2006 1 commit
  7. 24 Jun, 2006 1 commit
  8. 22 Mar, 2006 1 commit
  9. 13 Jan, 2006 1 commit
  10. 30 Oct, 2005 1 commit
  11. 05 Oct, 2005 1 commit
  12. 22 Sep, 2005 1 commit
    • Benjamin Herrenschmidt's avatar
      [PATCH] ppc64: SMU driver update & i2c support · 0365ba7f
      Benjamin Herrenschmidt authored
      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: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Jean Delvare <khali@linux-fr.org>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  13. 29 Aug, 2005 1 commit
  14. 06 Jul, 2005 1 commit
  15. 20 Jun, 2005 1 commit
  16. 16 Apr, 2005 2 commits
    • Pavel Machek's avatar
      [PATCH] u32 vs. pm_message_t in ppc and radeon · b1c42851
      Pavel Machek authored
      This fixes pm_message_t vs.  u32 confusion in ppc and aty (I *hope* that's
      basically radeon code...).  I was not able to test most of these, but I'm
      not really changing anything, so it should be okay.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!