1. 01 11月, 2005 1 次提交
    • J
      [PATCH] Creative Audigy 2 cardbus: Add IO window wakeup magic · d83c671f
      James Courtier-Dutton 提交于
      This adds the magic IO wakeup code for the CardBus version of the
      Creative Labs Audigy 2 to the snd-emu10k1 driver.
      
      Without the magic IO enable sequence, reading from the IO region of the
      card will fail spectacularly, and the machine will hang.
      
      My next task will be getting the driver to actually play sound without
      distortion.
      Signed-off-by: NJames Courtier-Dutton <James@superbug.co.uk>
      
      [ This is a work-in-progress, but since it avoids a total lockup
        if the emu10k module is loaded on a machine with the cardbus
        card inserted, we're better off with it than without it, even
        if sound quality is bad right now ]
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d83c671f
  2. 07 10月, 2005 2 次提交
  3. 12 9月, 2005 5 次提交
    • C
      [ALSA] set owner field in struct pci_driver · 3bcd4649
      Clemens Ladisch 提交于
      AD1889 driver,ALS4000 driver,ATIIXP driver,ATIIXP-modem driver
      AZT3328 driver,BT87x driver,CMIPCI driver,CS4281 driver
      ENS1370/1+ driver,ES1938 driver,ES1968 driver,FM801 driver
      Intel8x0 driver,Intel8x0-modem driver,Maestro3 driver,RME32 driver
      RME96 driver,SonicVibes driver,VIA82xx driver,VIA82xx-modem driver
      ALI5451 driver,au88x0 driver,CS46xx driver,EMU10K1/EMU10K2 driver
      HDA Intel driver,ICE1712 driver,ICE1724 driver,KORG1212 driver
      MIXART driver,NM256 driver,RME HDSP driver,RME9652 driver
      Trident driver,Digigram VX222 driver,YMFPCI driver
      Set the module owner field in each driver's struct pci_driver to get
      the driver symlink in the sysfs device directory.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      3bcd4649
    • J
      [ALSA] snd-emu10k1: ALSA bug#1297: Fix a error recognising the SB Live Platinum. · afe0f1f6
      James Courtier-Dutton 提交于
      EMU10K1/EMU10K2 driver
      The card does not have an AC97 chip.
      .subsystem = 0x80611102
      Signed-off-by: NJames Courtier-Dutton <James@superbug.co.uk>
      afe0f1f6
    • T
      [ALSA] Replace with kzalloc() - pci stuff · e560d8d8
      Takashi Iwai 提交于
      AD1889 driver,ATIIXP driver,ATIIXP-modem driver,AZT3328 driver
      BT87x driver,CMIPCI driver,CS4281 driver,ENS1370/1+ driver
      ES1938 driver,ES1968 driver,FM801 driver,Intel8x0 driver
      Intel8x0-modem driver,Maestro3 driver,SonicVibes driver,VIA82xx driver
      VIA82xx-modem driver,AC97 Codec,AK4531 codec,au88x0 driver
      CA0106 driver,CS46xx driver,EMU10K1/EMU10K2 driver,HDA Codec driver
      HDA generic driver,HDA Intel driver,ICE1712 driver,ICE1724 driver
      KORG1212 driver,MIXART driver,NM256 driver,Trident driver,YMFPCI driver
      Replace kcalloc(1,..) with kzalloc().
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      e560d8d8
    • C
      [ALSA] sparse address space annotations · 4d23359b
      Clemens Ladisch 提交于
      ALSA Core,RawMidi Midlevel,ALSA<-OSS emulation,ALSA sequencer
      RME32 driver,RME96 driver,EMU10K1/EMU10K2 driver,NM256 driver
      Add sparse annotations where we do strange this with __iomem/__user
      pointers.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      4d23359b
    • J
      [ALSA] snd-ca0106, snd-emu10k1: Add symlink in the sys tree. · 025cd2f6
      James Courtier-Dutton 提交于
      CA0106 driver,EMU10K1/EMU10K2 driver
      A thread appeared on the LKML. This patch implements the fix.
      
      Question:
      in sysfs, /sys/bus/*/drivers lists the driver names, with their exported .name (eg. '.name = 'EMU10K1_Audigy'' in the module code, from now on 'driver name'). In /sys/modules, the kernel modules are listed with their module name, eg. snd_emu10k1. However, it seems to me that in sysfs, there is no way in particular to tell, which module has which .name. That is, that snd_emu10k1 is EMU10K1_Audigy and vice versa.
      
      I wonder whether it wouldn't be possible to add a symlink to the particular module from the driver, and/or from the module to the driver, so the list of devices handled by the module and the module name would be accessible. This way, I would know which driver name corresponds to which module name and vice versa.
      
      Answer:
      For PCI drivers, just add the line:
      	.owner = THIS_MODULE,
      
      to their struct pci_driver definition and you will get the symlink
      created for you.
      Signed-off-by: NJames Courtier-Dutton <James@superbug.co.uk>
      025cd2f6
  4. 30 8月, 2005 6 次提交
  5. 28 7月, 2005 8 次提交
  6. 22 6月, 2005 2 次提交
  7. 29 5月, 2005 16 次提交