From nobody Wed Dec 15 18:11:16 2021 X-Original-To: freebsd-current@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 5E4DE18D281D for ; Wed, 15 Dec 2021 18:11:28 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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 (2048 bits) client-digest SHA256) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JDjxD0zksz3Hrx; Wed, 15 Dec 2021 18:11:28 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.16.1/8.16.1) with ESMTPS id 1BFIBGsC004477 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 15 Dec 2021 10:11:17 -0800 (PST) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.glebi.us (8.16.1/8.16.1/Submit) id 1BFIBGkG004476; Wed, 15 Dec 2021 10:11:16 -0800 (PST) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@freebsd.org using -f Date: Wed, 15 Dec 2021 10:11:16 -0800 From: Gleb Smirnoff To: Emmanuel Vadot Cc: Ed Maste , FreeBSD Current Subject: Re: Any Cronyx Tau* (ce(4) or cp(4)) users ? Message-ID: References: <20211215162538.99d8d81650af56e2276f2f88@bidouilliste.com> <20211215175202.e1d101079a9c22c9094577f3@bidouilliste.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211215175202.e1d101079a9c22c9094577f3@bidouilliste.com> X-Rspamd-Queue-Id: 4JDjxD0zksz3Hrx X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Wed, Dec 15, 2021 at 05:52:02PM +0100, Emmanuel Vadot wrote: E> > > I've noticed this /sbin/sconfig binary and after looking it's for E> > > configuring Cronyx E1 PCI (PCI as in PCI, not PCIe). E> > > The products pages ([1], [2]) seems to say that FreeBSD >=7 isn't E> > > supported. E> > > We currently only build the drivers for i386 (and they contain native E> > > compiled code). E> > > E> > > Anyway, I'd like to remove this from the tree, I really doubt that E> > > anyone uses this cards nowadays (or even E1) but just in case I send E> > > this mail. E> > E> > I posted a similar query to -stable in 2020, at E> > https://lists.freebsd.org/pipermail/freebsd-stable/2020-February/092037.html E> > and did not get any response. E> > E> > I have D23928 for a deprecation notice for ce and cp. Gleb commented E> > there that he'd offer to maintain them (and as part of that, removed E> > sppp in 6aae3517ed25). E> > E> E> I'm not sure I understand the logic here. E> We're keeping drivers for museum grade hardware that no developer have E> access to and likely no one uses nowadays just for an hypothetical E> situation where someone will try to use those cards on FreeBSD 14 i386 E> in 2021 ? E> And we're doing that just because the drivers compiles ? We are doing that because the hardware is still produced and can be purchased at http://cronyx.ru/price/#taupci And this is not a dead website, I gave a call to tech support last year. Who uses it? No idea. For some obscure reason they are still produced along with conventional PCI industrial mainboards (you can google that). I agree that actual intersection of FreeBSD users and Cronyx users could be zero today. But potentially it can be non-zero. I would appreciate if somebody chooses FreeBSD for their very strange industrial communications equipment. Some corrections on above statements. 1) We build cp(4) on amd64. We don't build ce(4) on amd64 for a reason that some functions are marked with __attribute__ fastcall. I'm 99% sure that attribute can be removed and ce(4) will build on amd64. sconfig(8) is build on amd64. 2) Drivers don't contain native precompiled code. They contain obfuscated code. Does sconfig create any problems for you? I'm fine with removing the drivers and the tool if they do really create a burden for us. That was case with their sppp(4) half, and I removed it in 6aae3517ed25. If there is no maintainance burden, why remove them? Just to save disk space? -- Gleb Smirnoff