1. 06 12月, 2008 8 次提交
  2. 05 12月, 2008 1 次提交
    • S
      sparc,sparc64: unify kernel/ · a88b5ba8
      Sam Ravnborg 提交于
      o Move all files from sparc64/kernel/ to sparc/kernel
        - rename as appropriate
      o Update sparc/Makefile to the changes
      o Update sparc/kernel/Makefile to include the sparc64 files
      
      NOTE: This commit changes link order on sparc64!
      
      Link order had to change for either of sparc32 and sparc64.
      And assuming sparc64 see more testing than sparc32 change link
      order on sparc64 where issues will be caught faster.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a88b5ba8
  3. 12 9月, 2008 1 次提交
  4. 11 9月, 2008 1 次提交
  5. 25 8月, 2008 1 次提交
    • D
      sparc: Add mutex for set property calls. · 2481d766
      David S. Miller 提交于
      On some platforms, the I2C controller is shared between the OS and
      OBP.  OBP uses this I2C controller to access the EEPROM, and thus is
      programmed when the kernel calls prom_setprop().
      
      Wrap such calls with the new of_set_property_mutex.
      
      Relevant I2C bus drivers can grab this mutex around top-level I2C
      operations to provide the proper protection.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2481d766
  6. 08 8月, 2008 1 次提交
  7. 24 4月, 2008 1 次提交
  8. 18 2月, 2008 1 次提交
  9. 05 10月, 2007 1 次提交
  10. 17 9月, 2007 1 次提交
  11. 08 8月, 2007 1 次提交
  12. 21 7月, 2007 1 次提交
    • D
      [SPARC]: Fix serial console device detection. · c73fcc84
      David S. Miller 提交于
      The current scheme works on static interpretation of text names, which
      is wrong.
      
      The output-device setting, for example, must be resolved via an alias
      or similar to a full path name to the console device.
      
      Paths also contain an optional set of 'options', which starts with a
      colon at the end of the path.  The option area is used to specify
      which of two serial ports ('a' or 'b') the path refers to when a
      device node drives multiple ports.  'a' is assumed if the option
      specification is missing.
      
      This was caught by the UltraSPARC-T1 simulator.  The 'output-device'
      property was set to 'ttya' and we didn't pick upon the fact that this
      is an OBP alias set to '/virtual-devices/console'.  Instead we saw it
      as the first serial console device, instead of the hypervisor console.
      
      The infrastructure is now there to take advantage of this to resolve
      the console correctly even in multi-head situations in fbcon too.
      
      Thanks to Greg Onufer for the bug report.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c73fcc84
  13. 20 7月, 2007 6 次提交
  14. 16 7月, 2007 1 次提交
    • D
      [SPARC64]: Initial LDOM cpu hotplug support. · 4f0234f4
      David S. Miller 提交于
      Only adding cpus is supports at the moment, removal
      will come next.
      
      When new cpus are configured, the machine description is
      updated.  When we get the configure request we pass in a
      cpu mask of to-be-added cpus to the mdesc CPU node parser
      so it only fetches information for those cpus.  That code
      also proceeds to update the SMT/multi-core scheduling bitmaps.
      
      cpu_up() does all the work and we return the status back
      over the DS channel.
      
      CPUs via dr-cpu need to be booted straight out of the
      hypervisor, and this requires:
      
      1) A new trampoline mechanism.  CPUs are booted straight
         out of the hypervisor with MMU disabled and running in
         physical addresses with no mappings installed in the TLB.
      
         The new hvtramp.S code sets up the critical cpu state,
         installs the locked TLB mappings for the kernel, and
         turns the MMU on.  It then proceeds to follow the logic
         of the existing trampoline.S SMP cpu bringup code.
      
      2) All calls into OBP have to be disallowed when domaining
         is enabled.  Since cpus boot straight into the kernel from
         the hypervisor, OBP has no state about that cpu and therefore
         cannot handle being invoked on that cpu.
      
         Luckily it's only a handful of interfaces which can be called
         after the OBP device tree is obtained.  For example, rebooting,
         halting, powering-off, and setting options node variables.
      
      CPU removal support will require some infrastructure changes
      here.  Namely we'll have to process the requests via a true
      kernel thread instead of in a workqueue.  workqueues run on
      a per-cpu thread, but when unconfiguring we might need to
      force the thread to execute on another cpu if the current cpu
      is the one being removed.  Removal of a cpu also causes the kernel
      to destroy that cpu's workqueue running thread.
      
      Another issue on removal is that we may have interrupts still
      pointing to the cpu-to-be-removed.  So new code will be needed
      to walk the active INO list and retarget those cpus as-needed.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4f0234f4
  15. 08 6月, 2007 1 次提交
    • D
      [SPARC64]: Fix SBUS IRQ regression caused by PCI-E driver. · ec4d18f2
      David S. Miller 提交于
      We used to access the 64-bit IRQ IMAP and ICLR registers of bus
      controllers 4-bytes in and as a 32-bit register word, since only the
      low 32-bits were relevant.  This seemed like a good idea at the time.
      
      But the PCI-E controller requires full 8-byte 64-bit access to
      these registers, so we switched over to accessing them fully.
      
      SBUS was not adjusted properly, which broke interrupts completely.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ec4d18f2
  16. 05 6月, 2007 3 次提交
  17. 29 5月, 2007 1 次提交
  18. 12 5月, 2007 1 次提交
  19. 10 5月, 2007 1 次提交
  20. 07 5月, 2007 2 次提交
  21. 26 4月, 2007 4 次提交
  22. 31 10月, 2006 1 次提交
    • D
      [SPARC64]: Fix Tomatillo/Schizo IRQ handling. · 9001f285
      David S. Miller 提交于
      The code in schizo_irq_trans_init() should set irq_data->sync_reg
      to the location of the SYNC register if this is Tomatillo, and set
      it to zero otherwise.  But that is not what it is doing.
      
      As a result, non-Tomatillo systems were trying to access a
      non-existent register resulting in bus errors at the first
      PCI interrupt.
      
      Thanks to Roland Stigge for the bug report.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9001f285
新手
引导
客服 返回
顶部