Date: Wed, 19 Jan 2022 17:06:27 -0500 From: grarpamp <grarpamp@gmail.com> To: freebsd-stable@freebsd.org Cc: freebsd-advocacy@freebsd.org, freebsd-chat@freebsd.org Subject: Re: Intel + Thunderbolt Driver Message-ID: <CAD2Ti2921W1iTvDHQx8bXNFJ22zW3fdvTz6%2BKO3AaPeVRgoipg@mail.gmail.com> In-Reply-To: <DM6PR02MB5228AF640057643CA922EA8CFA599@DM6PR02MB5228.namprd02.prod.outlook.com> References: <DM6PR02MB522854F196C25EF0ECBA32DAFA549@DM6PR02MB5228.namprd02.prod.outlook.com> <20220118235203.GJ35602@funkthat.com> <DM6PR02MB5228AF640057643CA922EA8CFA599@DM6PR02MB5228.namprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/19/22, Gerard E. Seibert <gerard_seibert@outlook.com> wrote: > FreeBSD's inability to support this technology will come back > to bite them in the ass. Even if writing drivers is not their thing, users can actually do a lot to help relieve such situations. Have people considered buying some snake traps or at least some Preparation-H at the shoppe below? And speaking to manufacturers to get #OpenDocs and more #OpenHW built on #OpenFabs. And dropping hints of the GoodNews of FreeBSD and passing that collection box around in all the surfaceweb fora where the unwashed bidet-needing masses congregate waiting to crowdfund a cute saintly daemon that could help lead them out of the dark walled-in lands of wintel? https://freebsdfoundation.org/donate/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2921W1iTvDHQx8bXNFJ22zW3fdvTz6%2BKO3AaPeVRgoipg>