1. 16 10月, 2007 1 次提交
    • T
      [ALSA] opti9xx: adjust OPL3 FM resource value · 1ea73412
      Takashi Iwai 提交于
      The OPTi ISA-PnP chips advertise their OPL4 base at 0x380 (to 0x3f0) through
      pnp and put their on-chip OPL3 at +8. The driver assumes the provided
      value is the ALBase (OPL3 address) though and checks for an OPL4 at -8,
      which means that simply adding 8 to the pnp provides value works to fix
      detection of both OPL3 and OPL4.
      Problem spotted on 931 and 933 by Krzysztof Helt and confirmed on 924 and
      925 (together all OPTi ISA-PnP chips) by me.
      Signed-off-by; Rene Herman <rene.herman@gmail.com>
      Acked-by: NKrzysztof Helt <krzysztof.h1@wp.pl>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@suse.cz>
      1ea73412
  2. 20 7月, 2007 1 次提交
    • T
      [ALSA] Fix unfreed pnp driver in opti9xx ISA driver · 101f6f4b
      Takashi Iwai 提交于
      - Added the missing pnp_unregister_card_driver() in the case ISA PnP
        isn't found, which caused an error at kobject_add with -EEXIST
         Jun 11 09:07:31 rain kernel: kobject_add failed for opti9xx with -EEXIST, don't try to register things with the same name in the same directory.
         Jun 11 09:07:31 rain kernel:  [<c01c18fa>] kobject_shadow_add+0x12a/0x1c0
         Jun 11 09:07:31 rain kernel:  [<c01c1a81>] kobject_register+0x21/0x50
         Jun 11 09:07:31 rain kernel:  [<c01f09a2>] bus_add_driver+0x72/0x1b0
         Jun 11 09:07:31 rain kernel:  [<c01d3dff>] pnp_register_card_driver+0x4f/0xc0
         Jun 11 09:07:31 rain kernel:  [<c89bc00a>] alsa_card_opti9xx_init+0xa/0x25 [snd_opti92x_ad1848]
         Jun 11 09:07:31 rain kernel:  [<c0136947>] sys_init_module+0x157/0x1610
         Jun 11 09:07:31 rain kernel:  [<c01029b4>] syscall_call+0x7/0xb
      - Fixed the probe behavior when no PnP is set up.  Now it behaves
        like the former version.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@suse.cz>
      101f6f4b
  3. 11 5月, 2007 3 次提交
  4. 22 10月, 2006 1 次提交
  5. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  6. 03 7月, 2006 1 次提交
  7. 12 4月, 2006 1 次提交
  8. 22 3月, 2006 1 次提交
  9. 01 2月, 2006 1 次提交
  10. 03 1月, 2006 4 次提交
  11. 04 11月, 2005 1 次提交
  12. 12 9月, 2005 3 次提交
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4