From nobody Mon Apr 22 19:04:04 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VNZRf1gZDz5Hh4h for ; Mon, 22 Apr 2024 19:04:14 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VNZRd3nZgz4dWy; Mon, 22 Apr 2024 19:04:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id D62FE8D4A241; Mon, 22 Apr 2024 19:04:05 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 8914E2D029D8; Mon, 22 Apr 2024 19:04:05 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id sLnL0RIebwJd; Mon, 22 Apr 2024 19:04:04 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id A12F22D029D2; Mon, 22 Apr 2024 19:04:04 +0000 (UTC) Date: Mon, 22 Apr 2024 19:04:04 +0000 (UTC) From: "Bjoern A. Zeeb" To: Mark Johnston cc: freebsd-arch@freebsd.org Subject: Re: requiring reserved NFS client ports by default In-Reply-To: Message-ID: <11p334q0-914s-4oq3-3q49-9rp000662730@yvfgf.mnoonqbm.arg> References: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zabbadoz.net]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4VNZRd3nZgz4dWy On Tue, 16 Apr 2024, Mark Johnston wrote: > It's common practice for NFS clients to bind to reserved ports (i.e., <= > 1023) since some NFS servers require this as a weak security measure > against attackers with network access to a server but without local > privileges. FreeBSD's NFS server does not require clients to use > privileged ports by default, but this can be changed by setting > nfs_reserved_port_only=YES in rc.conf. > > I would like to propose flipping the default for nfs_reserved_port_only. > This raises the bar a bit for a malicious agent able to execute > unprivileged code on a machine with network access to an unauthenticated > NFS server running FreeBSD. This behaviour would match the defaults on > Linux (the per-export "secure" attribute) and OpenBSD. > > The downside is increased pressure on the limited range of reserved port Does it still? Is it not per 4-tuple these days? > numbers. However, the server will complain on the console if a request > arrives on an unreserved port, so diagnosis should be easy, and most > clients sport an option to not use a reserved port number (noresvport on > FreeBSD), so one can configure client mounts to use them only where > needed. And, the option is easy to disable on the server should that be > necessary. My aim here is to provide a safer out-of-the-box behaviour. > > Any comments, objections, feedback? Yes, please do it! -- Bjoern A. Zeeb r15:7 From nobody Mon Apr 22 20:26:19 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VNcGS0gDqz5Hq86 for ; Mon, 22 Apr 2024 20:26:24 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VNcGR64mjz4wCv for ; Mon, 22 Apr 2024 20:26:23 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x72f.google.com with SMTP id af79cd13be357-7906782388aso139075685a.2 for ; Mon, 22 Apr 2024 13:26:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713817583; x=1714422383; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=cyVBxFjjnpl/octgw9az96krVuWVniw1OEcEMcR82BA=; b=VlVdwDLNXsV6UVi/YYtGZVFx8jDFRcQjf4mAF01UjAVUeLsU2FgWh9Fll5mSQZTnSX VwACBxI6plKpk0sutwr+nHtZIT28tlJQdtEs6E0O813zppXwBO1mQkzg5uLdt4ldiD+4 NHumxEApkrIZjDIiUAphfoXSfDZBivX+EPDw4yg47aLsB7e0o0GrggTphPoXYhgMIOHX Q4w56QCYI4t+H3SxCALHPhITlJ4gDPOtvUEVIB26avEYyNlupMZQtisAMH5PXnJ4lm5z o9vZv6cmyvGWVXUDTXzt3X1QROu63XD9n3CBKjBMfH50vVEgEDmp0ARMDWd60RLBQNet 2nag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713817583; x=1714422383; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=cyVBxFjjnpl/octgw9az96krVuWVniw1OEcEMcR82BA=; b=aevSYXYYE1YSaqgqn/xouARXOUhVxGhe2jI2qfZGHfMPNaeE87K8C/obbv5k5/wT2H jAgnXH8+Hyj+rI4d6UgNi6Wn6y3fMWDEm2MBea8MEx97b1VBBRHzRsvous1xiluFDesO JR4VZ6CrozJGVTS0O+WS2EJIcDmapGTDXwcz0n/ZRYiszzraXKH8toBxotEbJzG5dHCg qivytVTqvlToW4cxWZUDMB3Qe+neSlm3dxXMrOD7T55/oM+5W6DsSIaPCoFqBH7jFfoE E/daZIzHM80fXBCBGux/QeJ5DD1e1bzCvBTNc4eew9ry6bMNvDRi77h9eEGvbE1zHHfp B2aA== X-Gm-Message-State: AOJu0YyWLy8/jxAObFrQr616oQ8Ed8P9VmZRSONy0z/00urDqW80XMXg I0rRVyK8UR6/Gy/wF4+GHWZirstYVYqmu2fC4zRPr6npX3oma+2bPmxg3w== X-Google-Smtp-Source: AGHT+IG0jzu4LikalrgF/KciUYuPti/eKI38UC03psn8dudcaKe22c+tbf7OKG0V9gjkwUqJWdOK2A== X-Received: by 2002:a05:620a:a:b0:78e:ef2c:6e with SMTP id j10-20020a05620a000a00b0078eef2c006emr13630331qki.32.1713817582561; Mon, 22 Apr 2024 13:26:22 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id w14-20020a05620a148e00b0078d6b42ca02sm4621038qkj.120.2024.04.22.13.26.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Apr 2024 13:26:22 -0700 (PDT) Date: Mon, 22 Apr 2024 16:26:19 -0400 From: Mark Johnston To: "Bjoern A. Zeeb" Cc: freebsd-arch@freebsd.org Subject: Re: requiring reserved NFS client ports by default Message-ID: References: <11p334q0-914s-4oq3-3q49-9rp000662730@yvfgf.mnoonqbm.arg> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11p334q0-914s-4oq3-3q49-9rp000662730@yvfgf.mnoonqbm.arg> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VNcGR64mjz4wCv On Mon, Apr 22, 2024 at 07:04:04PM +0000, Bjoern A. Zeeb wrote: > On Tue, 16 Apr 2024, Mark Johnston wrote: > > > It's common practice for NFS clients to bind to reserved ports (i.e., <= > > 1023) since some NFS servers require this as a weak security measure > > against attackers with network access to a server but without local > > privileges. FreeBSD's NFS server does not require clients to use > > privileged ports by default, but this can be changed by setting > > nfs_reserved_port_only=YES in rc.conf. > > > > I would like to propose flipping the default for nfs_reserved_port_only. > > This raises the bar a bit for a malicious agent able to execute > > unprivileged code on a machine with network access to an unauthenticated > > NFS server running FreeBSD. This behaviour would match the defaults on > > Linux (the per-export "secure" attribute) and OpenBSD. > > > > The downside is increased pressure on the limited range of reserved port > > Does it still? Is it not per 4-tuple these days? Well, I'd expect port N to be unusable for an NFS client if a service is listening on that port. And, if a client has many mounts from the same server, it might be difficult to find a spare port. > > numbers. However, the server will complain on the console if a request > > arrives on an unreserved port, so diagnosis should be easy, and most > > clients sport an option to not use a reserved port number (noresvport on > > FreeBSD), so one can configure client mounts to use them only where > > needed. And, the option is easy to disable on the server should that be > > necessary. My aim here is to provide a safer out-of-the-box behaviour. > > > > Any comments, objections, feedback? > > Yes, please do it! https://reviews.freebsd.org/D44906 From nobody Tue Apr 23 17:32:50 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VP8Mq4H7Tz5Hh1k for ; Tue, 23 Apr 2024 17:32:55 +0000 (UTC) (envelope-from christos@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VP8Mq3mnWz4Hdw for ; Tue, 23 Apr 2024 17:32:55 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713893575; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=f0tp/dS+tts8kpbZsdrqMtrIflAxk6N7YtK9TW4o+As=; b=s01ZZXsEb821qILj4NZUcncBWL/zknuTwtphFHKb4olyD++eQJbLIAb3hqzsQux3WX3mTd iYZXx4JWXgamIC72Iv0sPljhQWbo/buq0aezzPrLb9FEtaBFwGMQQRqz3o4myICd56/jSu IFhNZnKHyEdBMgWaZI7MAt0k2k4r/7ucYWrFHqTsrthqQZJY78uyZGS1GAqvaEPuHaRpvl ykdZAblm2lYkxNbAdLlw9JmpjFiWLvY9nDJTahrxUPMAoAv74G73Zb+7CsJ3Go/XEesoCc V4QqBuuCSBXKPZIOSV6SdgIfrZUf0kXsGjoiHlO4QcJUFhWnPaKwLSldVyYmEw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1713893575; a=rsa-sha256; cv=none; b=k5LvqigXtOEcy3LANjJgjlu8V18EQmH6VK67qh4cMUCoNg7CK6UQQy70De+W5wBdmDOfJO G3+T+6OR8Y4GM5CKxMW5L5yDXEUnvANGWgemll5CYyoJNSk79koyrv8qsalYsPv4QSDAiE CRDOU62DBVAJaVQ7N0uQpCtShcuqVuyoxCs5nbKsx/VK6Iy5cq1qN3e2b7dHcrsRLWIFl1 roXwLZFKqyDcStZctR8/tPhYstl3Oxtg3AvROEnXEQ7ZMn71Lh4/+ArKtQPL5lL+0vgFVm HdG5cVMPRgVQe7RtXkDHop1NloxvMj6ddPiBrWstmORFZxC1yYRfDsNWUwlarg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713893575; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=f0tp/dS+tts8kpbZsdrqMtrIflAxk6N7YtK9TW4o+As=; b=M6Z4ZpTw2iDBTvM2h3AB+4Z7pWL2IIQ6fOY/ufM1d7IO7f7KmwMeQfFO+RyffYvYcmgGhx wXHucylryB2HPY8rzSlXfMhiD7fQTtleV3wDXvlsbeQdcT7o9vNRRdAtB9Lv/FXXBYmPw9 CYLxd7AgvAaiYvylYGA64uaVN8etyX50Y5ZwxeUjQ4W7zDKz8yI8XBbGSKXVS/BUvlK2Fc i4EEIby1SqeX8F2DnqYPdErHYhrRE8NiQ24PhyEsF3QPKuCq8JYdiSMqeFcf2zQmi/RL4B JBqqC/pJ/QCkQFBQpv6uCNxODz75WaU6qn9gtErCFEd0nyRt36hTb6lyd15s3Q== Received: from margiolis.net (mail.margiolis.net [95.179.159.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) (Authenticated sender: christos/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VP8Mq1ZgczgsN for ; Tue, 23 Apr 2024 17:32:55 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=mail; bh=7ioCIc54LDYAWVo g6E23mVXZnEMm4fcxOS3yjazRPM4=; h=subject:to:from:date; d=margiolis.net; b=RU09A4ilncBLAaQOeLRCaqdgyN9Yvq41Z1/bwV3qFeqqAcr53Hj r3GfS13BZW+UtZtbddLGYT7k6ZLsX2l9XBpTDDrmIhXyc9x1PLaJKB1F0wvJFJ9kvIqfLR cTuik6ip2jzjQ8CQGD13dnZM4G4AS7a7/xpcsum4kC6PVjlE8M= Received: from tpad (ip-45-81-121-44.ask4internet.com [45.81.121.44]) by margiolis.net (OpenSMTPD) with ESMTPSA id b1eb95ec (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Tue, 23 Apr 2024 17:32:51 +0000 (UTC) Date: Tue, 23 Apr 2024 19:32:50 +0200 From: Christos Margiolis To: freebsd-arch@freebsd.org Subject: sound(4) purge candidates Message-ID: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I compiled the following list of PCI drivers that we could possibly purge. I've included the drivers that have either never been referenced in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. snd_als4000 never (only auto-loaded by snd_driver.ko) snd_atiixp never snd_cmi 2004 snd_cs4281 2020 (OpenBSD), 2004 (FreeBSD) snd_csa 2006 (as well as a single 2020 reference) snd_emu10k1 2006 snd_envy24 never snd_envy24ht 2018 (only reference) snd_es137x 2004 snd_fm801 never (only auto-loaded by snd_driver.ko) snd_neomagic 2004 snd_solo 2004 snd_spicds never snd_t4dwave 2004 snd_via8233 2005 snd_via82c686 2004 snd_vibes never (only auto-loaded by snd_driver.ko) Christos [1] https://dmesgd.nycbug.org From nobody Tue Apr 23 17:37:54 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VP8Tf1Y25z5HhnM for ; Tue, 23 Apr 2024 17:37:58 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VP8Td4s35z4JZs for ; Tue, 23 Apr 2024 17:37:57 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x133.google.com with SMTP id e9e14a558f8ab-36c1a6362a4so4083675ab.2 for ; Tue, 23 Apr 2024 10:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; t=1713893876; x=1714498676; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=xJzAWVTcmXPWfCp4grICV3XYW8IB5MrqNWbhDMacHro=; b=B9qTF2JWs1DQzYMw79YXVg3wyZ+a0UIsocSp8sEG7BPhijmij/DeJ5IuVY0vK/kdAK ChWp8wOBrvSu8pIlD4h7DjpPiY3SKUc0DA7ats4PZgybRRmdh9tbgE/xF9h1G8NMnCoO J6RgSd8KkyDebSgWMZrBh6l7jXa8AccRYKkGZ8TpPVrBwlzsGGv+/GfLv6ieaiL4w5vj qv+MMYSbVhoy/L/+Fmv/ugA+++iMktKCtD4xtVf3G4mzrWUPNker7+0gtSH/Unu9s1BZ pOnIK+JWJDmwjMBVxPPVicIAJ4SVdKmX5KGmVlODTJLDL8lRP9daDzZWMGrCd+Qq1qbh 3/Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713893876; x=1714498676; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=xJzAWVTcmXPWfCp4grICV3XYW8IB5MrqNWbhDMacHro=; b=sr2+lTpBE2EW568UsjtmIoxTVI6qvKdtwAnhezTnEllJkazwKadoSUQTFg3HE+YLDa /dAArTBf0KNTBpQbqaOHJoOAmOhVvd2IJM/xH0oXc45bFKNKLUnfaLVlpTFLg41ybQYt c0L9a3YOiJCQkbBVEk5BHCL35aP2U7QO4SIySqIuS38AYJB23kqwD6HqGD20KNFprP5V 07qgD62999umTnX9R0sAfMuHRWzxQNXwabwFsd/DMjVLCcRPxK6is99XD7IZpEt1ZHRY 5AYIavoNMcBDE+YBRzEeE+Sbbs2Ck/diMzy6kNUYjNiphvqDHOQ/sGOVQ8tgIkFuF4lD IsKQ== X-Gm-Message-State: AOJu0Yx37OYNLPyHz2sMLx8xn4g+3YGbmTq5P/ZSdDM6fM57z01NZ771 RVn8icLS21SXjwBA1snZOheGCQHVR8XpXL4ul2MGbja3nuRfrte4wY+ci42mt1D7re7KyxdjgTx 7 X-Google-Smtp-Source: AGHT+IHVg62wC1Ya01kNH4AkaoXH/tQY0rA3iy0ANZDVjbE2399hTUjoSCktHygGl3fYPML+sPIIEQ== X-Received: by 2002:a05:6e02:1a6a:b0:36a:686:bc99 with SMTP id w10-20020a056e021a6a00b0036a0686bc99mr251157ilv.4.1713893876131; Tue, 23 Apr 2024 10:37:56 -0700 (PDT) Received: from mutt-hbsd ([184.99.37.29]) by smtp.gmail.com with ESMTPSA id y3-20020a92d203000000b0036a3a6cb15asm2711184ily.30.2024.04.23.10.37.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Apr 2024 10:37:55 -0700 (PDT) Date: Tue, 23 Apr 2024 17:37:54 +0000 From: Shawn Webb To: Christos Margiolis Cc: freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates Message-ID: <6ip4sayqs5jw4nou4vvigivgeoejc42fw6j76wryfgwulihcpp@nlrk2wv5q7nq> X-Operating-System: FreeBSD mutt-hbsd 15.0-CURRENT-HBSD FreeBSD 15.0-CURRENT-HBSD X-PGP-Key: https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/blob/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gqv7mqvhsxwbveij" Content-Disposition: inline In-Reply-To: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VP8Td4s35z4JZs --gqv7mqvhsxwbveij Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 23, 2024 at 07:32:50PM +0200, Christos Margiolis wrote: > I compiled the following list of PCI drivers that we could possibly > purge. I've included the drivers that have either never been referenced > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. [snip] > [1] https://dmesgd.nycbug.org >=20 Another data point for hardware deployments is: https://bsd-hardware.info/ Might be worth taking a look at. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --gqv7mqvhsxwbveij Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmYn8esACgkQ/y5nonf4 4fqCSQ/6AqR0Ck2d9AFhpYCYa4yKCK1E1I5xle91o/n24fIkzH2EDFkSzz39Gy1Q WaqKbKWYqaFL4lWsi8w00GqIhqLsApr3VjfH7WOTyOq+8xpUewzQb+AG+q1EYYcY giZ0pTucoJwwLJsFQY9AWYnvAu0YstDHStLhAFYpNhYf2n83VFIVGWvgMsN6vCaa 2lIZ40jKGtf6gpmTunmaxKv3ei/Ki3kimoitdaQN8MXcyWMQSoGSRSkLEMSy0V/7 kyrjZZp1s4TkelPQqSnCXTU6OMPLNHd8rehsLqv0mtEa+itfyg1iZNhm7H0lckZC IUerRbp6hXP+MNCAMBcupKNqUv16Ym1631NhK1C989l8hE4jU5reetX2vrB5pzBG 5qOS50FjQ/RdHbK6WFoQmj24ydj4WNXHMiqJaTbXeGH0xFtfMBMdQvfyo5xCMb9O s6Hxd8tYaMV3usbctPh2+nynlAnKmBDYMxfzTsEflDmGeuH/dE717nJSl6rjXmCZ lQa8MzUwRkC73Hh5pgWDs4Eoi5Fjtf1ylJErlbI+QQmvgO5EnpUNOp2G5HUc/rt6 lmhXzND8XEFfXIkeW5hz5I0nOFjed469QPJeuGVVZrRly8/+XfET5/5f28JtWVTC iT4jOCZ6dkdmHg6ILSow9zpXC2KV1z7MffYyJdBz0o7kV+UAPMs= =zm18 -----END PGP SIGNATURE----- --gqv7mqvhsxwbveij-- From nobody Tue Apr 23 18:36:51 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VP9nm3BxWz5HpvD for ; Tue, 23 Apr 2024 18:37:00 +0000 (UTC) (envelope-from joel@vnode.se) Received: from oden.vnode.se (oden.vnode.se [IPv6:2001:19f0:6c01:6b7:5400:1ff:fe33:16b1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "oden.vnode.se", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VP9nl1sHFz4XVx; Tue, 23 Apr 2024 18:36:59 +0000 (UTC) (envelope-from joel@vnode.se) Authentication-Results: mx1.freebsd.org; none Received: from ymer.vnode.se (81-231-98-9-no600.tbcn.telia.com [81.231.98.9]) by oden.vnode.se (Postfix) with ESMTPSA id 9640C1F40C; Tue, 23 Apr 2024 20:36:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vnode.se; s=mail; t=1713897411; bh=iln3JdrFm/A8DwcWUS0ydIfOGyGw6n5/IWGuWEseSdU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=SLbTZVBIcYtL34NJ4f6T2Xd6eyBRv+IIZHvf3pVoy+crdD9Mz/nQG/TTxlxZUmmiH 6UZK553VUSoPSdSiK2yzAr060a1ZzLEKMUfOE1WQ51lGdEdSCLOXMYKKfpTCSN8TcB RMddI1exSwoEzaBHCf8vYmZG646R9kQ6Tl0yKS0E= Date: Tue, 23 Apr 2024 20:36:51 +0200 From: Joel Dahl To: Christos Margiolis Cc: freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates Message-ID: Mail-Followup-To: Christos Margiolis , freebsd-arch@freebsd.org References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:6c00::/38, country:US] X-Rspamd-Queue-Id: 4VP9nl1sHFz4XVx On Tue, Apr 23, 2024 at 07:32:50PM +0200, Christos Margiolis wrote: > I compiled the following list of PCI drivers that we could possibly > purge. I've included the drivers that have either never been referenced > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. FWIW, I still have my old snd_es137x, snd_fm801, snd_solo, snd_csa, and snd_cmi cards. I test them from time to time and they still work (about ~2 years ago at least). -- Joel From nobody Tue Apr 23 21:49:46 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VPG4G13hnz5J8XC for ; Tue, 23 Apr 2024 21:49:50 +0000 (UTC) (envelope-from christos@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VPG4F5CNHz4xft; Tue, 23 Apr 2024 21:49:49 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713908989; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XdFbkmPUv73iodr4B+UiiJcG92DeTnVDZq1aj8t+s+4=; b=Om9KeoRzVGg1XjrAhz87Muoq6ws2JUqi2wDer6IyFWW1JbcmHdY4cy8jUSNtpYT+vCsjMz KIbuH5e9Tpmxmh4tciI2nF+8zqoXbgNHO8Mu6ZGrwjza3qh6f8XHJYGeaSJSmb4dYwlTau tUcq/BixYzuwkLnGYw+yj2xOqhlyumD/c0bVAfektdc/iXeEuDmMT7iEtoj2U6qfXkkwdk QMwjA4EA618Ty/J1l7cKZgjmo8yFK/5ciz4aMxGlkW6OGEZcnCjO808vt/GkUmjf/3fZ53 Eq77CMI5L89eOpxBZ/flP+ntroONNyqjHxRVcvF+ojjH83otnCAgps9o+GqGVw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1713908989; a=rsa-sha256; cv=none; b=qb72vt9s0hizGiSJlUaqOxJ3w+G0ygOTYTOaS8eAGjURSbSLolYmKgC6qiiEb9w0/8NZNA SuvVA1SNPCgh5Ss6EUIwEIp5YS07bM+Eg/ZZXiO0PGLVPnwuNuDkDfYsFkkGsQLzfqNc5a M4jvXB4m7bqM08k7grcWteGcmXfcGk2Q2DwFhZlQpohZ4hDLs/mryLfkC/mzfQ8xM/8UDi OqcVLNCmsqIQZJLsni8EpzgwvUPbthdQtrOTc9lX6TyJxH7inmjh6cp757HewAgQbUtOPS /iQBMnVwuwkBOYaiooD2DwgCGe2KJIiAikDoIPRvaTz2k68Z26XeOnoejn273A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713908989; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=XdFbkmPUv73iodr4B+UiiJcG92DeTnVDZq1aj8t+s+4=; b=o/M2GjY/R8z5H20jgbr/bpvElW8zOmOFUB2xnTlmqu9TyUbmaag97vJ7O+103/U0bAA366 wAlbsahpn9BTHTib1W4+oJzn3udr9z8N8XsAeAkKGhl6zv6hEo5Tqurhl1E4dFl8+gAnv1 ObTlebAm5AvVrf91IRgUfw7U61XZnQSVWoxofQz64luuZjMyHxiGt7qumG1hyfgMAjHH9+ qwYQJi5XJ3/dQGauCOBaVOmMd64BAWMZ7uKSOl9SNddSFBZS271htrLv7AaSTvbxe9OjYf /rmUu3pIrp2K7BGI6f5WIAL2UZ2l6AjtCafriWzzf3UmZELkOjXgt9rTqoGfNw== Received: from margiolis.net (mail.margiolis.net [95.179.159.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) (Authenticated sender: christos/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VPG4F2Tg5z117n; Tue, 23 Apr 2024 21:49:49 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=mail; bh=zPO4/1t6ZSyOEO/ MZzfe9D3+GKu+uRDX2NhQndbTh3I=; h=in-reply-to:references:subject:cc:to: from:date; d=margiolis.net; b=cmWBws1zAGDdH7HZkyyyBwVFOChwLfLmZEuv93Hm nN0csiyqz5HcRmbgo4hNJbTScfPgNL0rVbzESZ6r3+YWfz4v2dJTHZ3xbf8xQietxrvWq3 NcEa/4rmBHMvu2EhNLDa0zMdPSdmqz4CC70PKMhKJD/xyrnbCDnbtwCgO7ujY= Received: from tpad (ip-45-81-121-44.ask4internet.com [45.81.121.44]) by margiolis.net (OpenSMTPD) with ESMTPSA id 121bac92 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Tue, 23 Apr 2024 21:49:47 +0000 (UTC) Date: Tue, 23 Apr 2024 23:49:46 +0200 From: Christos Margiolis To: Joel Dahl Cc: freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates Message-ID: References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Joel Dahl wrote: > On Tue, Apr 23, 2024 at 07:32:50PM +0200, Christos Margiolis wrote: > > I compiled the following list of PCI drivers that we could possibly > > purge. I've included the drivers that have either never been referenced > > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. > > FWIW, I still have my old snd_es137x, snd_fm801, snd_solo, snd_csa, and snd_cmi cards. I > test them from time to time and they still work (about ~2 years ago at least). Interesting. I would expect the drivers to work, as you said, but the rationale behind my email is more like, do we want to keep supporting these cards in the first place? Is there demand for them? Ed got rid of the ISA drivers a while ago as well, so I'm thinking whether we might want to start cleaning up our PCI drivers as well. Christos From nobody Wed Apr 24 07:05:42 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VPVPq0Pb1z5JyD4 for ; Wed, 24 Apr 2024 07:05:51 +0000 (UTC) (envelope-from joel@vnode.se) Received: from oden.vnode.se (oden.vnode.se [45.76.82.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "oden.vnode.se", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VPVPp5RDdz4hRq; Wed, 24 Apr 2024 07:05:50 +0000 (UTC) (envelope-from joel@vnode.se) Authentication-Results: mx1.freebsd.org; none Received: from ymer.vnode.se (81-231-98-9-no600.tbcn.telia.com [81.231.98.9]) by oden.vnode.se (Postfix) with ESMTPSA id 8BB4E1F417; Wed, 24 Apr 2024 09:05:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vnode.se; s=mail; t=1713942343; bh=h/Y2Wvm+UvmRHhprrtta+n0f3lpFeWcEYkCLYWYC3iI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=LfYtopaO44JsTXINkhJ1LNHNuZc/Q+1J2qn7oa8SdHLXVjOVk0wHdCazyJ0jqQqmj 3AQ8sqXziuFsLjrR8M/YpOxmJ2lZvoVJVW4zecdB052LZ3YYVZk+BESmIul/cZ0Q8u T+P/RVaRjia3FPK05y5kexq5hG1VJ2RupVOAOknc= Date: Wed, 24 Apr 2024 09:05:42 +0200 From: Joel Dahl To: Christos Margiolis Cc: freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates Message-ID: Mail-Followup-To: Christos Margiolis , freebsd-arch@freebsd.org References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:45.76.80.0/20, country:US] X-Rspamd-Queue-Id: 4VPVPp5RDdz4hRq On Tue, Apr 23, 2024 at 11:49:46PM +0200, Christos Margiolis wrote: > Joel Dahl wrote: > > On Tue, Apr 23, 2024 at 07:32:50PM +0200, Christos Margiolis wrote: > > > I compiled the following list of PCI drivers that we could possibly > > > purge. I've included the drivers that have either never been referenced > > > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. > > > > FWIW, I still have my old snd_es137x, snd_fm801, snd_solo, snd_csa, and snd_cmi cards. I > > test them from time to time and they still work (about ~2 years ago at least). > > Interesting. I would expect the drivers to work, as you said, but the > rationale behind my email is more like, do we want to keep supporting > these cards in the first place? Is there demand for them? Ed got rid of > the ISA drivers a while ago as well, so I'm thinking whether we might > want to start cleaning up our PCI drivers as well. Are these drivers preventing development in the sound area? Do they increase the maintenance burden? When I look at the code I don't see much git activity in any of the drivers for the past 10 years or so. But the drivers still do seem to work (at least for the cards I have). -- Joel From nobody Wed Apr 24 10:16:21 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VPZdw1sytz5H25n for ; Wed, 24 Apr 2024 10:16:36 +0000 (UTC) (envelope-from tomek@cedro.info) Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VPZdv6xYRz420F for ; Wed, 24 Apr 2024 10:16:35 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-617f8a59a24so56077347b3.1 for ; Wed, 24 Apr 2024 03:16:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1713953795; x=1714558595; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ksSpFmB6v+hKqM2ORrcvxWbskJdXLBFh+74lOoKodyc=; b=jV0SSG59wT+jbSkXt5uJ4q28xMwN70ahcg0jyz7rVSVuxgA19Dls04n4GVKqJa4zuM WtYMXZgk4SpFOGiEoepn2lHRlsNOsI+nYzeECSuc4D7lRqfRjeCawYJmVmLTIg4ur37A bw8s7YHVTKFYFj6uMq1x4pJblqycPhgSoSVkeK2k3vQEoGktB3mpAByquHk54qa+2GRj FuUIrhaNN2VYkrvL9EqSQ1lecDP6qKX6hMMKDfS8sTV4GAJuJosjUctSDi2wluraNsxy 12xLdWClzIt0Mk0aR73vkNK22s8FtOvnaOFX3BS0uzmN7Ge4QSsrShgOqlfXg9Bfmc3/ rKfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713953795; x=1714558595; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ksSpFmB6v+hKqM2ORrcvxWbskJdXLBFh+74lOoKodyc=; b=FDgqwNT1anDHhH/qeuV/szILFap5nYooMoLSm1xwioyLOfGfWXZLzOSktRRTqOX5AJ 48v8QSYcVvEVOAJLD98lUWWJj7+bcxh9SryaP8YMKpuO41vu6sJr2jjEjxwEMkA7MtXJ Aopdl5Q6u+Eph2wPeeW1tKl1P/g/ZnfaqLK3Q4hi2cbDTrTMIN35FtjfGCsFcDzwET3F sWrCLI6Xx+yKA6LUvvUz7beUluJvxgKfE+4oKcZEdl26NFE8tln/IIh2iqfVlRJFXIcX w6H67dXg59oriciEpNQDi3g397daxm8PkMdimJrt9l4CCvao83iTboeVVVTdkKODi2mc jbog== X-Gm-Message-State: AOJu0YzbiFWx+1ykSmJBAj/iLaUdwdWPuPRWppqG6s37Gd7fFbiGqsfe vGP/mTJV+jbgP9EHicZ+MvYqMgVMCaGYbvG/loXHRpP6zyCxWmP4i6Y3JNOXVg== X-Google-Smtp-Source: AGHT+IH5VC7kD52fWDlSAFOLk/nUZiHkDu9k++v2D4/nxnWqu6mnAa0cONvp2ppIkJaLOEGCDwqKGQ== X-Received: by 2002:a05:690c:62c3:b0:615:c96:1a8d with SMTP id hn3-20020a05690c62c300b006150c961a8dmr2364307ywb.8.1713953794892; Wed, 24 Apr 2024 03:16:34 -0700 (PDT) Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com. [209.85.219.169]) by smtp.gmail.com with ESMTPSA id x30-20020a81af5e000000b0061b1f325755sm2920401ywj.123.2024.04.24.03.16.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Apr 2024 03:16:34 -0700 (PDT) Received: by mail-yb1-f169.google.com with SMTP id 3f1490d57ef6-de46da8ced2so6600571276.0; Wed, 24 Apr 2024 03:16:34 -0700 (PDT) X-Received: by 2002:a25:ce12:0:b0:dca:e4fd:b6d5 with SMTP id x18-20020a25ce12000000b00dcae4fdb6d5mr2260324ybe.27.1713953793461; Wed, 24 Apr 2024 03:16:33 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> In-Reply-To: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> From: Tomek CEDRO Date: Wed, 24 Apr 2024 12:16:21 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: sound(4) purge candidates To: Christos Margiolis Cc: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VPZdv6xYRz420F On Tue, Apr 23, 2024 at 7:33=E2=80=AFPM Christos Margiolis wrote: > > I compiled the following list of PCI drivers that we could possibly > purge. I've included the drivers that have either never been referenced > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. > > snd_als4000 never (only auto-loaded by snd_driver.ko) > snd_atiixp never > snd_cmi 2004 > snd_cs4281 2020 (OpenBSD), 2004 (FreeBSD) > snd_csa 2006 (as well as a single 2020 reference) > snd_emu10k1 2006 > snd_envy24 never > snd_envy24ht 2018 (only reference) > snd_es137x 2004 > snd_fm801 never (only auto-loaded by snd_driver.ko) > snd_neomagic 2004 > snd_solo 2004 > snd_spicds never > snd_t4dwave 2004 > snd_via8233 2005 > snd_via82c686 2004 > snd_vibes never (only auto-loaded by snd_driver.ko) If these PCI drivers work fine then I would leave them as is. I have three SounBlaster Live/Audigy cards that works fine here on FreeBSD but not on Windoze anymore.. they enforce buying new hardware just because drivers are unsupported. We do not want that on BSD. If something works fine then don't touch it :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Thu Apr 25 01:49:25 2024 X-Original-To: arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VPzLZ12Njz5JZwS for ; Thu, 25 Apr 2024 01:49:42 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from fuchsia.eden.le-Fay.ORG (fuchsia.eden.le-fay.org [81.187.47.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4VPzLY1WRHz46JK for ; Thu, 25 Apr 2024 01:49:41 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=fuchsia header.b=G9Ees9jz; dmarc=none; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 81.187.47.195 as permitted sender) smtp.mailfrom=lexi@le-fay.org Received: from iris.eden.le-Fay.ORG (iris.eden.le-fay.org [IPv6:2001:8b0:aab5:106:3::6]) by fuchsia.eden.le-Fay.ORG (Postfix) with ESMTP id 3A8BF98E2 for ; Thu, 25 Apr 2024 01:49:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=fuchsia; t=1714009774; bh=NZVPKkOfH2quSPuz1HtM+CZRZbB6dqL66nVYQri5qF8=; h=Date:From:To:Subject; b=G9Ees9jz7louUM/P6XM7+sr2mC/Osqq4AJfzl7m/OZhZ55ykUvFWCf1aDmHgymDCO NM0n3fH0pLuatZywCnFHC5YDz0hxOL4eU/a/0u8jRI2XvYKqzcstN5IW962LDfVBSp 72F57c0s4Ca5pn+F0MgF2sfjriO8r1icZuSgjTN8= Received: from ilythia.eden.le-fay.org (ilythia.eden.le-fay.org [IPv6:2001:8b0:aab5:106:3::10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id 108CC2C0421 for ; Thu, 25 Apr 2024 02:49:34 +0100 (BST) Date: Thu, 25 Apr 2024 02:49:25 +0100 From: Lexi Winter To: arch@freebsd.org Subject: config(8) - remove 'device' Message-ID: List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AO6slL23QPhytN2w" Content-Disposition: inline X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.49 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=fuchsia]; R_SPF_ALLOW(-0.20)[+ip4:81.187.47.195:c]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB]; RCPT_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[le-fay.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DWL_DNSWL_NONE(0.00)[le-fay.org:dkim]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[arch@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[arch@freebsd.org]; DKIM_TRACE(0.00)[le-fay.org:+] X-Rspamd-Queue-Id: 4VPzLY1WRHz46JK --AO6slL23QPhytN2w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hello, as older BSD users may remember, 'device' when used in a kernel config used to have a fairly specific syntax, e.g.: device foo0 at pci? irq? ... etc ... nowdays of course this isn't a thing, you just write: device foo so, practically this is no different from writing: options FOO i propose to remove the 'device' syntax from config(8) and simply use 'options' to include various parts of kernel code in the kernel. i am prepared to create a patch to do this, but of course, i would prefer to find out if people would accept this before putting the effort in. the concrete benefit of this is that we don't have two different syntaxes in kernel configs that do exactly the same thing. --AO6slL23QPhytN2w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEuwt6MaPcv/+Mo+ftDHqbqZ41x5kFAmYptqIACgkQDHqbqZ41 x5lOkwv+KtBXoTh4HDRaczlsv4LW+z5rcjOfkfKweiqtGWptGrOplwzzSfg73Uwi cEyF0+wKf2+dgNhn7LNajT+X46dm1S2ZyIGpVAzBGm2LL+iwWBz+/6veLGSGdvRa AdtF7PvvzHZ3MNn5nFww4AHFzqCFyE9oyt4Oau61+N/BnCZarYWkK2ZXcsoRwhvn 2g5aQU7iPuJ0xKCiQCuvanjmGjPCg9LNQMQc38DddXN2vdrqXKJPBuTBL9ZMBTo+ f7YYTCHeuQiCkkpVc6Q5eMaeehRp2RbJ/UGUT99HFQecu6C58+y4pqOpiTguY+44 +QaIimo+bQFSJrOP8Nf6nPiESOAp16Wk9WpUoiz2wwZrH4qJnGrcEdjY6SiZlHgd WvjTp0LXV990MfEITMIwvr2m0t9KIH1L8VvJTE3g05/zwbJu4jPBkiDOLmnZpYES 7Jw3Avfn+lTLzqgqqlTzuwCIq9DlIMKmfl2I65nExhx3kp9k0Ruytnxyx7B+5Ehi MjtbgOmi =nCdT -----END PGP SIGNATURE----- --AO6slL23QPhytN2w-- From nobody Thu Apr 25 04:15:54 2024 X-Original-To: arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VQ7wD6Lclz5H2Z7 for ; Thu, 25 Apr 2024 08:15:56 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VQ7wD2phmz4kvW for ; Thu, 25 Apr 2024 08:15:56 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1714032955; x=1714637755; i=garyj@gmx.de; bh=HgLJgNvNWs4vv9zKsKKwUrdSRbCHM/OKt9RJ1bJNycQ=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:Message-ID:In-Reply-To: References:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=A+5XwsOOohI/57YnQXbmikCAK4alWcyD66b96MQMtMozRHX9lGCm1psAT0o8QE3A MNbiuAnfAxtlu1DKruhs7iXtua+nFM7frks+xfxkWrIFGHR2l6N87JM8Qy+a4l48e jlLzumcuYqNmjAF4ZBLu1TtMEllGrgvQx/ivw56T0VI9X+04itYTMqUBMo4JeFAC3 AJrHzSNeUQHlf4Apt/0/BqxeTV3ApfRU6uwEIzExb6urxEtNxbD22HM6CzkJsK04I ucz3cGmsdTQjKQqOcIAb8LsUiNRO7NsJcHPYJZMEB2NCbDNvH/ARMocRBUX/BMuX6 IPd8fLEnds063nIkQw== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([217.226.50.237]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M26vL-1rxzON3GWX-0044IG; Thu, 25 Apr 2024 10:15:54 +0200 Date: Thu, 25 Apr 2024 04:15:54 +0000 From: Gary Jennejohn To: Lexi Winter Cc: arch@freebsd.org Subject: Re: config(8) - remove 'device' Message-ID: <20240425061554.4d1965c8@ernst.home> In-Reply-To: References: Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:fgdIeaEKI2FRRUFTJ2ToybW5r5G7hCdDBkYVRfmuRJLd+tDwjtP 0TGdpMIwPRNLxo7Pz/5CaPNcQyYraUD5hkS/YkbcYS9nRvFt2oV8ro6nx+PDAHiFDCHRf7v nZvTv69s+atupAvKWtVdG8gcDci3o/lPTkM7fZHdp9iR4UbfURiSwY6GYRNIaNbaS/Cb/3W jvbGM6xL3TlD1JrArKh2g== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:K0sZQxeJvI4=;UVbUbhzp+gyTZl6o/bWWZtGWafN tYJThNZho400CewZmWDgFfenJOz39pYefRsPW2apuZFXTn4l1e/+1Brc3RpuCI94xoICedD3N FzBiIoOgU3BqpQwiSZvUr0EOu+ddTiZRb65dJ+QCFIVOK7qvrBL/wIP9EiIE+eSx49PDK0ZrO DLb8SLiutz16wyHG3tp9EgxJE53zYWizcEtc1rPrbq6KxsasLTIPO+5FsNzgbxsXdIlCcVRSy HmBxykuYWW5fAZI7Fy6Nk3RkNkbOvn/ZkNUWiptFMfG+5cvzdixWrkP2blHdMHD0HizoZjKxs NAS78mDNy6FStCodGds1tWNCTUnlUCWNjU2MxwAIMkJN7jOdUcsSyAHB93eO7hM4D+IyDbf5l WtZY6rXMHV/vJhtnT8biAkYw3JbtyULWSlmNn1qevTglyVsx6A4k9VlSliEF7C7+YY9c/Vmmx /+lW5TOPmtdeLJcg58DkwNGBzAeX8vajMK7Wcb1+it+SunZFydLpObsfWUwdy6w8kEczeKu/p i6gVDPD/mXp4OBSDwjCRvq9FnCY4Nh3vgcmK8vZzPzMFG+qx3GMR/gxBNqI0yWG9jE0OS8Kop uWNBq2A5jNvnx1e+YKBc8Bpy0pfinjZGmJVfumzjZqrsptZPvzQgA/nr4cbyrFmWkUqCOVVic budXsbI2XwiEsOFnNNQPi4u+WN4xc/mrxNb33MtvqDlDk8u6unn9N8l+Ua9tKB6rOYeaP20/t rxNC52Yxg5NmscJLAgfJhwEefFbcwNePugTin7CceMGWMe3W36b8fPwaeAM8X5QYuIeYizIw8 Y7s0UnVxT+6M3npxUsLjOb5emetQTMjdm0jySama3jqCc= X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Queue-Id: 4VQ7wD2phmz4kvW On Thu, 25 Apr 2024 02:49:25 +0100 Lexi Winter wrote: > hello, > > as older BSD users may remember, 'device' when used in a kernel config > used to have a fairly specific syntax, e.g.: > > device foo0 at pci? irq? ... etc ... > > nowdays of course this isn't a thing, you just write: > > device foo > > so, practically this is no different from writing: > > options FOO > > i propose to remove the 'device' syntax from config(8) and simply use > 'options' to include various parts of kernel code in the kernel. > > i am prepared to create a patch to do this, but of course, i would > prefer to find out if people would accept this before putting the effort > in. > > the concrete benefit of this is that we don't have two different > syntaxes in kernel configs that do exactly the same thing. I personally like having device, since this tells me that it's a driver and not an option which affects how the kernel is built, like SCHED_4BSD. For users who use e.g. GENERIC et al. this change wouldn't matter much. But for users using custom kernel configuration files, like I do, it would mean some unnecessary churn. However, I could live with that if the majority considers this change to be a good idea. =2D- Gary Jennejohn From nobody Thu Apr 25 08:43:59 2024 X-Original-To: arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VQ8Xm1Hzbz5H627 for ; Thu, 25 Apr 2024 08:44:08 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VQ8Xl1vBfz4ncB for ; Thu, 25 Apr 2024 08:44:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 43P8hxkk053048; Thu, 25 Apr 2024 11:44:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 43P8hxkk053048 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 43P8hxVQ053047; Thu, 25 Apr 2024 11:43:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 25 Apr 2024 11:43:59 +0300 From: Konstantin Belousov To: Lexi Winter Cc: arch@freebsd.org Subject: Re: config(8) - remove 'device' Message-ID: References: List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on tom.home X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4VQ8Xl1vBfz4ncB On Thu, Apr 25, 2024 at 02:49:25AM +0100, Lexi Winter wrote: > hello, > > as older BSD users may remember, 'device' when used in a kernel config > used to have a fairly specific syntax, e.g.: > > device foo0 at pci? irq? ... etc ... > > nowdays of course this isn't a thing, you just write: > > device foo > > so, practically this is no different from writing: > > options FOO There is a difference, and it is quite significant. As a hint, look at sys/conf/options* and it's second column. > > i propose to remove the 'device' syntax from config(8) and simply use > 'options' to include various parts of kernel code in the kernel. > > i am prepared to create a patch to do this, but of course, i would > prefer to find out if people would accept this before putting the effort > in. > > the concrete benefit of this is that we don't have two different > syntaxes in kernel configs that do exactly the same thing. From nobody Thu Apr 25 15:48:11 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VQKy70mHtz5J0k5 for ; Thu, 25 Apr 2024 15:48:15 +0000 (UTC) (envelope-from christos@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VQKy70BSRz4Fq0; Thu, 25 Apr 2024 15:48:15 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1714060095; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=APm0VQMF4vTTsHtPDWoWXXqVZvPYcHUAAWzk8j9INv8=; b=pSDsPk9VtezvKqMedqGcZdInPHGeajXB4392URlLsEatiyLnZe82lc3yJ9fLyT+1QLEV9P Ff2WQRnCX/uMU3CJ66Y7zuoMx+LHS5leg4/DbGdK4g/6Lsw9zhOddMr8wCGce8voQ2Myoo c518gT0dE2T5p2y5dHcPCnnF2stM14/Infd+srV7ety2BiS5keXD128zv9ZxLm8wsTNZAJ 6grt7NTdPxV+aWNA4s4KUkrfEgAWK+1uWul7cFkKdInDDtHff80IQe5ImaBzYU7YsUOmzQ JIAydUE3iBrlgE8Qzv/Z385WJqYlVQoX2Z2/FCfuLv1rVwH/R8Ms4N2k+DkxfQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1714060095; a=rsa-sha256; cv=none; b=NIyPFNaI6l/vBAJV2VJUkBzxUpxCC5KbDsnDgTDjU3EIC4y53nbkQG7kbVCGX3dBIZAdcx 9n70YLkWhxawzDcEPKdSLfGrUa1HkPt9+S6lGMkQmXBa/b/GQxwLa0DVs7VDcZvokCLSLt GLcm1jshMVaijvmlR7/YP/fSus1z3jRCh7vxL7bsJs5clLLTVyEonLzqH3pZdF+3OG9w5H 6t71UCyg/MwlBo27yB3L/iE8IAOR3vCcjmYUKjxcU3Rl9kbdkJlLsHkhb0m3hUIdAswA7i A91HutwwNs49bAB2YiBa6G45H8v2euROmP1wR6S/ibypJXcXsKrWACulYvGK6Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1714060095; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=APm0VQMF4vTTsHtPDWoWXXqVZvPYcHUAAWzk8j9INv8=; b=ImblZGHBIaSAxhr8z1B+7ZhqcCARujz+31ij73jEg4CZqw9zr613/9IccqGvlKLWtcMtot GT+hTdR1oNxupcAhnXqAvJ7Y722mbWetjhfHu2UM6p03M67fYPqicGie/GFPkKRX7lRwUv fJB5FXGNN0/62zgM00JD/hRVBgDXPhTldmJYaQtg+iwH+lXoiyt4wFrz0mxof/5xwhXJSF QIQOQfpspcL2O3pCmhQm6buaB1/+9V/rjbhszuZYikidfg+EoJz6zktwJheVkl4W+vqIwi 6ikhbpDXHwmJ8RU+Oeku/il0IvHf+74c3dC0MjBEj1xkZ/6fZCicalBgO1pGRA== Received: from margiolis.net (mail.margiolis.net [95.179.159.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) (Authenticated sender: christos/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VQKy64Y2yzdbG; Thu, 25 Apr 2024 15:48:14 +0000 (UTC) (envelope-from christos@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=mail; bh=heXzqM0K8XRoXQy 82BQiDNBASfGij4I91d73NVg5geA=; h=in-reply-to:references:subject:cc:to: from:date; d=margiolis.net; b=gxCFwtSpe5WsPMutkgDlmN8DwMq6ZyExahqryHnw yiDLqK4wxCrxpv04ucSa18MV3gyBGdKwEQF8q6EN3M7iV2VjzPPR0EyTi09mpQeckRF1Er y7xdx5Fw7ISDNh7RTWkBtSk90A2bvUI6fSBmebctrrK2YtzCS4u5H8UcQJ848= Received: from tpad (ip-45-81-121-44.ask4internet.com [45.81.121.44]) by margiolis.net (OpenSMTPD) with ESMTPSA id 6f87a271 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Thu, 25 Apr 2024 15:48:12 +0000 (UTC) Date: Thu, 25 Apr 2024 17:48:11 +0200 From: Christos Margiolis To: Tomek CEDRO Cc: freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates Message-ID: References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Hello Tomek, Tomek CEDRO wrote: > On Tue, Apr 23, 2024 at 7:33 PM Christos Margiolis wrote: > > > > I compiled the following list of PCI drivers that we could possibly > > purge. I've included the drivers that have either never been referenced > > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. > > > > snd_als4000 never (only auto-loaded by snd_driver.ko) > > snd_atiixp never > > snd_cmi 2004 > > snd_cs4281 2020 (OpenBSD), 2004 (FreeBSD) > > snd_csa 2006 (as well as a single 2020 reference) > > snd_emu10k1 2006 > > snd_envy24 never > > snd_envy24ht 2018 (only reference) > > snd_es137x 2004 > > snd_fm801 never (only auto-loaded by snd_driver.ko) > > snd_neomagic 2004 > > snd_solo 2004 > > snd_spicds never > > snd_t4dwave 2004 > > snd_via8233 2005 > > snd_via82c686 2004 > > snd_vibes never (only auto-loaded by snd_driver.ko) > > If these PCI drivers work fine then I would leave them as is. I have > three SounBlaster Live/Audigy cards that works fine here on FreeBSD > but not on Windoze anymore.. they enforce buying new hardware just > because drivers are unsupported. We do not want that on BSD. If > something works fine then don't touch it :-) No objection to keep supporting drivers that are still in use, even if by a few users. I only want to make sure that we do not keep stuff that is clearly _not_ used/working anymore. Christos From nobody Fri Apr 26 09:30:04 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VQnXP5JCdz5JKJc for ; Fri, 26 Apr 2024 09:31:01 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VQnXN36Bhz49YM; Fri, 26 Apr 2024 09:31:00 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1714123852; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4K2egUK939cWXq0c3KcFInW9CBouFGRiyoDW/ul1ngc=; b=RmTfxooyYTpUm24H+2H3pkluzCQ+QAnIbjpbs74401m9vXBpZCctlyOKiOKi17DVeZCsc0 qjobm4KKxTtkyLkLbWBITo6njFgHrnKqphZ+PPerOLJOcH7AtFJSEvlKlyteYkKbrc4XhR UXdyeTNF2rEewGuzprLuKZpYwirour+gG8P3yyR2Sgc+FD9HeTVQB/wSkmVsjk5lAY7aWK vslvj3ci9RtkizyHYyFoRkAUf52/tLpRBY7nMY0L/Sdvq+AeuBRmTtnrfJNfP1pfmArYXc AMD9LL8sn/NYzmjLUP+BhmfJAMMXGEFKH7n8JJgv39FygRskZtXX93B/lm4j8g== Date: Fri, 26 Apr 2024 11:30:04 +0200 From: Alexander Leidinger To: Christos Margiolis Cc: Tomek CEDRO , freebsd-arch@freebsd.org Subject: Re: sound(4) purge candidates In-Reply-To: References: <2b2zwiosyb24s7upkscrgmfws7j2f7fpytwyj2s2kgfhjut2bv@fziwor46qcgi> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_434639d10171383b938bbf6428b1d1a5"; micalg=pgp-sha256 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4VQnXN36Bhz49YM This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_434639d10171383b938bbf6428b1d1a5 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed Am 2024-04-25 17:48, schrieb Christos Margiolis: > Hello Tomek, > > Tomek CEDRO wrote: >> On Tue, Apr 23, 2024 at 7:33 PM Christos Margiolis wrote: >> > >> > I compiled the following list of PCI drivers that we could possibly >> > purge. I've included the drivers that have either never been referenced >> > in NYC*BUG dmesgd [1] or whose last reference is prior to 2010. >> > >> > snd_als4000 never (only auto-loaded by snd_driver.ko) >> > snd_atiixp never >> > snd_cmi 2004 >> > snd_cs4281 2020 (OpenBSD), 2004 (FreeBSD) >> > snd_csa 2006 (as well as a single 2020 reference) >> > snd_emu10k1 2006 >> > snd_envy24 never >> > snd_envy24ht 2018 (only reference) >> > snd_es137x 2004 >> > snd_fm801 never (only auto-loaded by snd_driver.ko) >> > snd_neomagic 2004 >> > snd_solo 2004 >> > snd_spicds never >> > snd_t4dwave 2004 >> > snd_via8233 2005 >> > snd_via82c686 2004 >> > snd_vibes never (only auto-loaded by snd_driver.ko) >> >> If these PCI drivers work fine then I would leave them as is. I have >> three SounBlaster Live/Audigy cards that works fine here on FreeBSD >> but not on Windoze anymore.. they enforce buying new hardware just >> because drivers are unsupported. We do not want that on BSD. If >> something works fine then don't touch it :-) > > No objection to keep supporting drivers that are still in use, even if > by a few users. I only want to make sure that we do not keep stuff that > is clearly _not_ used/working anymore. If the sound hardware is only availble in a package (e.g. mainboard only) for hardware which can not be bought anymore and is not supported anymore by release binaries (e.g. pure i386 vs. i486 and more modern), I would not oject to remove them. For stuff which is available on PCI cards and could be still in use in todays hardware, I do not think we should remove them based on age. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_434639d10171383b938bbf6428b1d1a5 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmYrdCoACgkQEg2wmwP4 2IbjNQ/9FhSGYh1cul5Cw4xuHwr23PcghcnApSKBSCkZK7PL7gBONvZQMhN5gJuv +WLP1FYj0umy5z6/CcTbepy18q3RZbPXdIs1mG2LpWIATKFOK7DJm/1sK3uWP6aI uazM5iHNWFj2RfNytBDtDAZA3+uUXd489VBxbrHAOw/6wNsUFbdW/hdudaSn3F3r dLkpNGX/grDf7GIgX04nqsFhYSFM5swX+/yC4JDjVjGcIewdYp4zN/sMQRF5DqYs L/cWlDqkhpF2Mf77v9OLXTs1XkjhGnt94E3SqIVXwrc5qowjakH1glxibrq/0TDw /AxBjL5+VoPduijwZg4oIunHgCrRawhUIXqdt0CFrHXPogyZPdXWOQC/i2EPgFTg BuV6+0cNay3hwno2FwTuVeWkFOHelBtg2vWuY/X5OIrp/Gps19nyxRELYERWUHzP 1tePTw9z075/656e2uyn4RSAuKHYGxRY9Sj77coEoXm5TlDxtfIpUd7Zt7ZxpfSG GUKPkVnbpJ78+c+u+4vAzFlhD8vBC50FoOL1o62QQ41k72fw+JTkxEbpclawUpWU IOAzW+YYvi+4bgvwpBTA0NhlUeX421awUsW7YxlsAgwEez5ix2scKXm7q5jBX8BV 8taSvsc4GptLzXTDtjwVAQXu0oJY3OSqGferRMUd0pBtkxvLQJE= =pISQ -----END PGP SIGNATURE----- --=_434639d10171383b938bbf6428b1d1a5--