1. 18 8月, 2010 1 次提交
  2. 09 2月, 2010 1 次提交
  3. 25 6月, 2009 1 次提交
  4. 12 1月, 2009 1 次提交
  5. 01 2月, 2008 1 次提交
    • T
      [ALSA] Remove sound/driver.h · 9004acc7
      Takashi Iwai 提交于
      This header file exists only for some hacks to adapt alsa-driver
      tree.  It's useless for building in the kernel.  Let's move a few
      lines in it to sound/core.h and remove it.
      With this patch, sound/driver.h isn't removed but has just a single
      compile warning to include it.  This should be really killed in
      future.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      9004acc7
  6. 16 10月, 2007 1 次提交
  7. 22 10月, 2006 1 次提交
  8. 23 9月, 2006 1 次提交
  9. 13 7月, 2006 1 次提交
  10. 23 6月, 2006 1 次提交
  11. 28 4月, 2006 1 次提交
  12. 03 1月, 2006 2 次提交
  13. 11 11月, 2005 1 次提交
  14. 04 11月, 2005 1 次提交
  15. 12 9月, 2005 1 次提交
    • 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
  16. 30 8月, 2005 1 次提交
    • C
      [ALSA] sound - fix .iface field of mixer control elements · 67ed4161
      Clemens Ladisch 提交于
      Documentation,CS46xx driver,EMU10K1/EMU10K2 driver,AD1848 driver
      SB16/AWE driver,CMIPCI driver,ENS1370/1+ driver,RME32 driver
      RME96 driver,ICE1712 driver,ICE1724 driver,KORG1212 driver
      RME HDSP driver,RME9652 driver
      This patch changes .iface to SNDRV_CTL_ELEM_IFACE_MIXER whre _PCM or
      _HWDEP was used in controls that are not associated with a specific PCM
      (sub)stream or hwdep device, and changes some controls that got
      inconsitent .iface values due to copy+paste errors.  Furthermore, it
      makes sure that all control that do use _PCM or _HWDEP use the correct
      number in the .device field.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      67ed4161
  17. 28 7月, 2005 2 次提交
  18. 29 5月, 2005 1 次提交
    • T
      [ALSA] Replace pci_module_init() with pci_register_driver() · 01d25d46
      Takashi Iwai 提交于
      Documentation,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,CA0106 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
      Replace the obsolete pci_module_init() with pci_register_driver().
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      01d25d46
  19. 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