menuconfig SOUND tristate "Sound card support" depends on HAS_IOMEM help If you have a sound card in your computer, i.e. if it can say more than an occasional beep, say Y. Be sure to have all the information about your sound card and its configuration down (I/O port, interrupt and DMA channel), because you will be asked for it. You want to read the Sound-HOWTO, available from . General information about the modular sound system is contained in the files . The file contains some slightly outdated but still useful information as well. Newer sound driver documentation is found in . If you have a PnP sound card and you want to configure it at boot time using the ISA PnP tools (read ), then you need to compile the sound card support as a module and load that module after the PnP configuration is finished. To do this, choose M here and read ; the module will be called soundcore. if SOUND config SOUND_OSS_CORE bool default n config SOUND_OSS_CORE_PRECLAIM bool "Preclaim OSS device numbers" depends on SOUND_OSS_CORE default y help With this option enabled, the kernel will claim all OSS device numbers if any OSS support (native or emulation) is enabled whether the respective module is loaded or not and try to load the appropriate module using sound-slot/service-* and char-major-* module aliases when one of the device numbers is opened. With this option disabled, kernel will only claim actually in-use device numbers and opening a missing device will generate only the standard char-major-* aliases. The only visible difference is use of additional module aliases and whether OSS sound devices appear multiple times in /proc/devices. sound-slot/service-* module aliases are scheduled to be removed (ie. PRECLAIM won't be available) and this option is to make the transition easier. This option can be overridden during boot using the kernel parameter soundcore.preclaim_oss. Disabling this allows alternative OSS implementations. If unsure, say Y. source "sound/oss/dmasound/Kconfig" if !M68K && !UML menuconfig SND tristate "Advanced Linux Sound Architecture" help Say 'Y' or 'M' to enable ALSA (Advanced Linux Sound Architecture), the new base sound system. For more information, see if SND source "sound/core/Kconfig" source "sound/drivers/Kconfig" source "sound/isa/Kconfig" source "sound/pci/Kconfig" source "sound/hda/Kconfig" source "sound/ppc/Kconfig" source "sound/aoa/Kconfig" source "sound/arm/Kconfig" source "sound/atmel/Kconfig" source "sound/spi/Kconfig" source "sound/mips/Kconfig" source "sound/sh/Kconfig" # the following will depend on the order of config. # here assuming USB is defined before ALSA source "sound/usb/Kconfig" source "sound/firewire/Kconfig" # the following will depend on the order of config. # here assuming PCMCIA is defined before ALSA source "sound/pcmcia/Kconfig" source "sound/sparc/Kconfig" source "sound/parisc/Kconfig" source "sound/soc/Kconfig" endif # SND menuconfig SOUND_PRIME tristate "Open Sound System (DEPRECATED)" select SOUND_OSS_CORE help Say 'Y' or 'M' to enable Open Sound System drivers. if SOUND_PRIME source "sound/oss/Kconfig" endif # SOUND_PRIME endif # !M68K endif # SOUND # AC97_BUS is used from both sound and ucb1400 config AC97_BUS tristate help This is used to avoid config and link hard dependencies between the sound subsystem and other function drivers completely unrelated to sound although they're sharing the AC97 bus. Concerned drivers should "select" this. ='1'>ssdiff
authorDavid S. Miller <davem@davemloft.net>2017-02-07 13:07:56 -0500
committerDavid S. Miller <davem@davemloft.net>2017-02-07 13:07:56 -0500
commit29ba6e7400a317725bdfb86a725d1824447dbcd7 (patch)
treeb009850c5a2e7c633a94eeacb71a25f91b4b64f0 /net
parentb08d46b01e995dd7b653b22d35bd1d958d6ee9b4 (diff)
parent51ce8bd4d17a761e1a90a34a1b5c9b762cce7553 (diff)
Merge branch 'replace-dst_confirm'
Julian Anastasov says: ==================== net: dst_confirm replacement This patchset addresses the problem of neighbour confirmation where received replies from one nexthop can cause confirmation of different nexthop when using the same dst. Thanks to YueHaibing <yuehaibing@huawei.com> for tracking the dst->pending_confirm problem. Sockets can obtain cached output route. Such routes can be to known nexthop (rt_gateway=IP) or to be used simultaneously for different nexthop IPs by different subnet prefixes (nh->nh_scope = RT_SCOPE_HOST, rt_gateway=0). At first look, there are more problems: - dst_confirm() sets flag on dst and not on dst->path, as result, indication is lost when XFRM is used - DNAT can change the nexthop, so the really used nexthop is not confirmed So, the following solution is to avoid using dst->pending_confirm. The current dst_confirm() usage is as follows: Protocols confirming dst on received packets: - TCP (1 dst per socket) - SCTP (1 dst per transport) - CXGB* Protocols supporting sendmsg with MSG_CONFIRM [ | MSG_PROBE ] to confirm neighbour: - UDP IPv4/IPv6 - ICMPv4 PING - RAW IPv4/IPv6 - L2TP/IPv6 MSG_CONFIRM for other purposes (fix not needed): - CAN Sending without locking the socket: - UDP (when no cork) - RAW (when hdrincl=1) Redirects from old to new GW: - rt6_do_redirect The patchset includes the following changes: 1. sock: add sk_dst_pending_confirm flag - used only by TCP with patch 4 to remember the received indication in sk->sk_dst_pending_confirm 2. net: add dst_pending_confirm flag to skbuff - skb->dst_pending_confirm will be used by all protocols in following patches, via skb_{set,get}_dst_pending_confirm 3. sctp: add dst_pending_confirm flag - SCTP uses per-transport dsts and can not use sk->sk_dst_pending_confirm like TCP 4. tcp: replace dst_confirm with sk_dst_confirm 5. net: add confirm_neigh method to dst_ops - IPv4 and IPv6 provision for slow neigh lookups for MSG_PROBE users. I decided to use neigh lookup only for this case because on MSG_PROBE the skb may pass MTU checks but it does not reach the neigh confirmation code. This patch will be used from patch 6. - xfrm_confirm_neigh: we use the last tunnel address, if present. When there are only transports, the original dest address is used. 6. net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP - dst_confirm conversion for UDP, RAW, ICMP and L2TP/IPv6 - these protocols use MSG_CONFIRM propagated by ip*_append_data to skb->dst_pending_confirm. sk->sk_dst_pending_confirm is not used because some sending paths do not lock the socket. For MSG_PROBE we use the slow lookup (dst_confirm_neigh). - there are also 2 cases that need the slow lookup: __ip6_rt_update_pmtu and rt6_do_redirect. I hope &ipv6_hdr(skb)->saddr is the correct nexthop address to use here. 7. net: pending_confirm is not used anymore - I failed to understand the CXGB* code, I see dst_confirm() calls but I'm not sure dst_neigh_output() was called. For now I just removed the dst->pending_confirm flag and left all dst_confirm() calls there. Any better idea? - Now may be old function neigh_output() should be restored instead of dst_neigh_output? ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
-rw-r--r--net/core/dst.c1
-rw-r--r--net/core/sock.c2
-rw-r--r--net/ipv4/ip_output.c11
-rw-r--r--net/ipv4/ping.c3
-rw-r--r--net/ipv4/raw.c6
-rw-r--r--net/ipv4/route.c19
-rw-r--r--net/ipv4/tcp_input.c12
-rw-r--r--net/ipv4/tcp_metrics.c7
-rw-r--r--net/ipv4/tcp_output.c2
-rw-r--r--net/ipv4/udp.c3
-rw-r--r--net/ipv6/ip6_output.c7
-rw-r--r--net/ipv6/raw.c6
-rw-r--r--net/ipv6/route.c43
-rw-r--r--net/ipv6/udp.c3
-rw-r--r--net/l2tp/l2tp_ip6.c3
-rw-r--r--net/sctp/associola.c3
-rw-r--r--net/sctp/output.c10
-rw-r--r--net/sctp/outqueue.c2
-rw-r--r--net/sctp/sm_make_chunk.c6
-rw-r--r--net/sctp/sm_sideeffect.c2
-rw-r--r--net/sctp/socket.c4
-rw-r--r--net/sctp/transport.c16
-rw-r--r--net/xfrm/xfrm_policy.c19
23 files changed, 143 insertions, 47 deletions
diff --git a/net/core/dst.c b/net/core/dst.c