From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8A7C6C04A6B for ; Wed, 8 May 2019 15:24:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 55D5220989 for ; Wed, 8 May 2019 15:24:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="htAIppr5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728393AbfEHPYF (ORCPT ); Wed, 8 May 2019 11:24:05 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:35860 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727407AbfEHPYC (ORCPT ); Wed, 8 May 2019 11:24:02 -0400 Received: by mail-pg1-f195.google.com with SMTP id a3so1028686pgb.3; Wed, 08 May 2019 08:24:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=+ht7GrFTU79fToPKb9Iep8eH6HLgwHBDoqhSDEh8xGU=; b=htAIppr5b/40B3bFZ+3X/36bRT7P8wvcYrDwc8mQOJv7LWE7rZ/yFNaMNs/U/wNuKv EV9uMszyp9uMpHnPARC7YOQPSAe8SvYGlSuUfzyGYuAoeZKpI0Nv51Ga++uTZDtNUiXd Zlu6/hpvsUgYf+kKN1Bfta/WbqI07YvEdLVvP1ZZXxpfcbDRfsMLZ44T3GCSZRU33S5F 2sbN1/wuYjKuft1VPHT91q0Xz+5vWtlvIeJDFMxDgv0D+gXoUYKDyQjT2Arj2C9fUvZe FlPNYzVOzlA/KR4/q9elRtQ/kDeQtuvu7cOImamEyOhpVaSJz94tC5yNWTwecITqdMiC 5Byw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=+ht7GrFTU79fToPKb9Iep8eH6HLgwHBDoqhSDEh8xGU=; b=AtV/rqGkTWyf4Uvrerndl30eUAn34NOHZ/rEFSdjLELi1ocbKGcknfzhdz97L4FrUC 2hfWDgduDKqxOd7hReMuxfDL2y0aGyyNybv4GKcmVfndHTK+OU9liW/UEA21+FUmc/HT szwdv2+/eiwsL7HLG23F4Mev5BasRnIfIJQ7qwEmj1ONXVGFXnxN0Uus2CJ51QIdLpbp 8NVDDHXW5Ul5B6H86ekt0p5b/z1RZ8ltNt0RlIOUZ/E04bZiolG5KjRBTry2TEAsEoQx lGACT2osqkobM2xuVITgpTQjCQAU3Jba6YI6jZdrxotVaWinGAh71pzJKMniqepVDkoU NojA== X-Gm-Message-State: APjAAAWiGKsKLuudrRF9VydG9PY5QxULCEUPqFLzkcCz1gCcegQ9VEVq HcVvuqUCxsKOJno9uiCZJ64= X-Google-Smtp-Source: APXvYqyO6eF3ygcjZfZODYs0ywNbScA8IBwo5vLf88+2yY8QRVKXpAwCBe6DzwYnUh2fpZtOyQSMkA== X-Received: by 2002:a63:5c5b:: with SMTP id n27mr37701411pgm.52.1557329041653; Wed, 08 May 2019 08:24:01 -0700 (PDT) Received: from localhost.localdomain ([104.238.181.70]) by smtp.gmail.com with ESMTPSA id o73sm7459360pfi.137.2019.05.08.08.23.56 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 08 May 2019 08:24:01 -0700 (PDT) From: Changbin Du To: corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de Cc: x86@kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Changbin Du , Mauro Carvalho Chehab Subject: [PATCH v4 19/27] Documentation: x86: convert usb-legacy-support.txt to reST Date: Wed, 8 May 2019 23:21:33 +0800 Message-Id: <20190508152141.8740-20-changbin.du@gmail.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190508152141.8740-1-changbin.du@gmail.com> References: <20190508152141.8740-1-changbin.du@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This converts the plain text documentation to reStructuredText format and add it to Sphinx TOC tree. No essential content change. Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab --- Documentation/x86/index.rst | 1 + ...acy-support.txt => usb-legacy-support.rst} | 40 +++++++++++-------- 2 files changed, 24 insertions(+), 17 deletions(-) rename Documentation/x86/{usb-legacy-support.txt => usb-legacy-support.rst} (53%) diff --git a/Documentation/x86/index.rst b/Documentation/x86/index.rst index 453557097743..3eb0334ae2d4 100644 --- a/Documentation/x86/index.rst +++ b/Documentation/x86/index.rst @@ -25,3 +25,4 @@ x86-specific Documentation pti microcode resctrl_ui + usb-legacy-support diff --git a/Documentation/x86/usb-legacy-support.txt b/Documentation/x86/usb-legacy-support.rst similarity index 53% rename from Documentation/x86/usb-legacy-support.txt rename to Documentation/x86/usb-legacy-support.rst index 1894cdfc69d9..e01c08b7c981 100644 --- a/Documentation/x86/usb-legacy-support.txt +++ b/Documentation/x86/usb-legacy-support.rst @@ -1,7 +1,11 @@ + +.. SPDX-License-Identifier: GPL-2.0 + +================== USB Legacy support -~~~~~~~~~~~~~~~~~~ +================== -Vojtech Pavlik , January 2004 +:Author: Vojtech Pavlik , January 2004 Also known as "USB Keyboard" or "USB Mouse support" in the BIOS Setup is a @@ -27,18 +31,20 @@ It has several drawbacks, though: Solutions: -Problem 1) can be solved by loading the USB drivers prior to loading the -PS/2 mouse driver. Since the PS/2 mouse driver is in 2.6 compiled into -the kernel unconditionally, this means the USB drivers need to be -compiled-in, too. - -Problem 2) can currently only be solved by either disabling HIGHMEM64G -in the kernel config or USB Legacy support in the BIOS. A BIOS update -could help, but so far no such update exists. - -Problem 3) is usually fixed by a BIOS update. Check the board -manufacturers web site. If an update is not available, disable USB -Legacy support in the BIOS. If this alone doesn't help, try also adding -idle=poll on the kernel command line. The BIOS may be entering the SMM -on the HLT instruction as well. - +Problem 1) + can be solved by loading the USB drivers prior to loading the + PS/2 mouse driver. Since the PS/2 mouse driver is in 2.6 compiled into + the kernel unconditionally, this means the USB drivers need to be + compiled-in, too. + +Problem 2) + can currently only be solved by either disabling HIGHMEM64G + in the kernel config or USB Legacy support in the BIOS. A BIOS update + could help, but so far no such update exists. + +Problem 3) + is usually fixed by a BIOS update. Check the board + manufacturers web site. If an update is not available, disable USB + Legacy support in the BIOS. If this alone doesn't help, try also adding + idle=poll on the kernel command line. The BIOS may be entering the SMM + on the HLT instruction as well. -- 2.20.1