From nobody Sat Mar 11 16:45:44 2023 X-Original-To: freebsd-hackers@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 4PYphM1wN0z3xq7B for ; Sat, 11 Mar 2023 16:45:55 +0000 (UTC) (envelope-from mail@souji-thenria.net) Received: from alisa.souji-thenria.net (alisa.souji-thenria.net [188.68.37.165]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4PYphK5CJnz3hjx for ; Sat, 11 Mar 2023 16:45:53 +0000 (UTC) (envelope-from mail@souji-thenria.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=souji-thenria.net header.s=20220813rsa header.b=0FYe6zAm; spf=pass (mx1.freebsd.org: domain of mail@souji-thenria.net designates 188.68.37.165 as permitted sender) smtp.mailfrom=mail@souji-thenria.net; dmarc=pass (policy=none) header.from=souji-thenria.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=souji-thenria.net; s=20220813rsa; t=1678553144; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=p6Ch8NB1SN8aTFMVilkwPBK28ZGIsCmHwPIKrvPLweI=; b=0FYe6zAm0DroQXVVoj7lUu2+pXyhehocqnxdiwlLoUDi4NdKFeBjAoe7w0C1MnoA1Ndhux 1dKygQAFJNIlvvwoO1T4rZCUKuK1HA3iyj8LPiFw0IQaQcPWvTavYbuaZaBbVjMk4LnlWR PLNC5fcpIku6lAWR6YjJnIcyq95cGoakoK79K8goCuVaxeqdjiV1LWLLcNi8ToQjOEm7e2 AWeRAxEGIOQ48/nXzTcq9Sj4B8YC/JNixav6a1JCb1cGEdYL+gj7gQUCDW3dzAlQzZoraP B5yLATQJBd0GAN9iTKU89h9f4q+z014FId/4IhSsCcEnSBdr/nUeca+fRjRn9A== Received: from [192.168.178.41] (nat-178-19-229-24.net.encoline.de [178.19.229.24]) by alisa.souji-thenria.net (OpenSMTPD) with ESMTPSA id 8072ffea (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sat, 11 Mar 2023 17:45:44 +0100 (CET) Message-ID: Date: Sat, 11 Mar 2023 17:45:44 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: quirks To: freebsd-hackers@freebsd.org References: Content-Language: en-US From: Souji Thenria In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[souji-thenria.net,none]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[souji-thenria.net:s=20220813rsa]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[souji-thenria.net:+]; ASN(0.00)[asn:197540, ipnet:188.68.32.0/20, country:DE]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PYphK5CJnz3hjx X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 3/11/23 16:43, void wrote: > What are 'quirks', how are they applied, why, where can I read up about > them, are they documented? Hey tia, I have found this [http://www.root.org/~nate/freebsd/scsi/quirks.html]: FreeBSD drivers make every attempt possible to support the standards behind hardware. Where possible and not in conflict with the standard, they also attempt to work around hardware which doesn't strictly conform. However, some devices have flaws which can't be worked around while keeping the driver compatible with the standard. For these devices, we have created a quirks mechanism to indicate to the driver that it must avoid certain commands or use them differently with a specific model and/or version of hardware. This document focuses on identifying and committing quirks for storage hardware involving CAM and UMASS but is applicable to other areas. Based on that, quirks are just identifiers for the driver, to compensate for non-standard hardware implementations. -- Souji Thenria