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 Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E87EEC433EF for ; Mon, 28 Mar 2022 02:44:09 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 8BAFC83A96; Mon, 28 Mar 2022 04:44:06 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="fOB41eGv"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id C4DCB83ABC; Mon, 28 Mar 2022 04:44:02 +0200 (CEST) Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 3FBAE839FD for ; Mon, 28 Mar 2022 04:43:59 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=bmeng.cn@gmail.com Received: by mail-pj1-x102d.google.com with SMTP id gb19so12723647pjb.1 for ; Sun, 27 Mar 2022 19:43:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=61Ffshw5A98/yFYrMtqqGeggzmEcxHywQstSBli4Kfc=; b=fOB41eGvPiJghguVsaKJYC/NSK4Bj2mxD8wB36SEVhOv3L/YO470UxzgXYgRuI7UfL TpWS8SN2mt6qn3bq1O1pTAOchDIRhpIGuk9GHnLsCSb1xzZEbSZvb6azEjKieF6vFghl fqUAY0i/nYvxd0HfntPL03hGBbjzwGZNgZvAsBTMtfEVjCTwsRgUTVIRFlbZ+bug+uNY WVXKpPUvISO011WsLmxs1JfXOEyUEaOydIazCmgma2+CVnU5ZaJcLoqBPc9GUUP2Ygv/ xbuHyNu7hI5S6Fr2yAed7V4Kj5LsyPO1r6KhTwg7g+hi45Dpq8PLixj5R8eweUDkO9uD /LTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=61Ffshw5A98/yFYrMtqqGeggzmEcxHywQstSBli4Kfc=; b=ksejuYSh3PhDdC/4MWCQIENvY2A02HhC3i+tRFeJ2UykWjDl522Nz7cYTn2jiTxpfu XNJ+ipTjpBwR9Tt+nlGxgGKZjvaT2khLvFWAgifKZxXzB8gDTw+yazR5AA488dzTtARJ VjCDewxMndMIIcFSYgQt2dXjJJJfNGmQn4UhjLOtGFvk8UkGukqgDkOFa3hbgczroeNv 7qF5yYOgzHiF48/hhGsgv/wD/vylmj2nA1IuETJdbX2xmSWwa8Xe+qaX+OsDL0IR9lp3 /fo9wLRqG2L7uWsMa2zNk24eLevmJtWvbuSNLe1MGP2JEKWNyhMYFi5QlHzuY17kXn6C TWCw== X-Gm-Message-State: AOAM5328Xs53llrCbjV/nd5Z3iccgJjvm3K4XFaPQOPuMXLPUB7lHysu N28ouWj/wtHNfieZm5rTARY= X-Google-Smtp-Source: ABdhPJy3GC7a1BwRA+RAJxXsmHJXmM4jtBDJj94HnArkpBEKfSw+/sCeQtTqYqbhn8KVSPjrnvqZjQ== X-Received: by 2002:a17:90b:3c03:b0:1c9:afca:75b3 with SMTP id pb3-20020a17090b3c0300b001c9afca75b3mr2792732pjb.71.1648435437515; Sun, 27 Mar 2022 19:43:57 -0700 (PDT) Received: from pek-vx-bsp2.wrs.com (unknown-176-192.windriver.com. [147.11.176.192]) by smtp.gmail.com with ESMTPSA id p10-20020a637f4a000000b00373a2760775sm11266095pgn.2.2022.03.27.19.43.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 27 Mar 2022 19:43:57 -0700 (PDT) From: Bin Meng To: Tom Rini , U-Boot Mailing List Subject: [PATCH 1/3] doc: usage: Convert README.vxworks to reST Date: Mon, 28 Mar 2022 10:43:49 +0800 Message-Id: <20220328024351.629189-1-bmeng.cn@gmail.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean This converts the existing README.vxworks to reST, and puts it under the doc/usage/os directory. Signed-off-by: Bin Meng --- doc/usage/index.rst | 8 +++++++ doc/{README.vxworks => usage/os/vxworks.rst} | 22 ++++++++++---------- 2 files changed, 19 insertions(+), 11 deletions(-) rename doc/{README.vxworks => usage/os/vxworks.rst} (93%) diff --git a/doc/usage/index.rst b/doc/usage/index.rst index 0aacf531b2..b8916971bc 100644 --- a/doc/usage/index.rst +++ b/doc/usage/index.rst @@ -52,3 +52,11 @@ Shell commands size true ums + +Booting OS +---------- + +.. toctree:: + :maxdepth: 1 + + os/vxworks diff --git a/doc/README.vxworks b/doc/usage/os/vxworks.rst similarity index 93% rename from doc/README.vxworks rename to doc/usage/os/vxworks.rst index 12a0d744d8..e696c639b2 100644 --- a/doc/README.vxworks +++ b/doc/usage/os/vxworks.rst @@ -1,11 +1,10 @@ -# SPDX-License-Identifier: GPL-2.0+ -# -# Copyright (C) 2013, Miao Yan -# Copyright (C) 2015-2018, Bin Meng -# Copyright (C) 2019, Lihua Zhao +.. SPDX-License-Identifier: GPL-2.0+ +.. Copyright (C) 2013, Miao Yan +.. Copyright (C) 2015-2018, Bin Meng +.. Copyright (C) 2019, Lihua Zhao -VxWorks Support -=============== +VxWorks +======= This document describes the information about U-Boot loading VxWorks kernel. @@ -20,7 +19,7 @@ With CONFIG_EFI_LOADER option, it's possible to chain load a VxWorks x86 kernel via the UEFI boot loader application for VxWorks loaded by 'bootefi' command. VxWorks 7 on PowerPC and ARM ---------------------------- +---------------------------- From VxWorks 7, VxWorks starts adopting device tree as its hardware description mechanism (for PowerPC and ARM), thus requiring boot interface changes. This section will describe the new interface. @@ -35,11 +34,11 @@ For legacy bootm flow, make sure the least significant bit of flags in bootargs is cleared. The calling convention is described below: For PowerPC, the calling convention of the new VxWorks entry point conforms to -the ePAPR standard, which is shown below (see ePAPR for more details): +the ePAPR standard, which is shown below (see ePAPR for more details):: void (*kernel_entry)(fdt_addr, 0, 0, EPAPR_MAGIC, boot_IMA, 0, 0) -For ARM, the calling convention is shown below: +For ARM, the calling convention is shown below:: void (*kernel_entry)(void *fdt_addr) @@ -47,7 +46,7 @@ When using the Linux compatible standard DTB, the calling convention of VxWorks entry point is exactly the same as the Linux kernel. When booting a VxWorks 7 kernel (uImage format), the parameters passed to bootm -is like below: +is like below:: bootm - @@ -108,6 +107,7 @@ BIOS of the graphics card first. CONFIG_FRAMEBUFFER_SET_VESA_MODE need remain set but care must be taken at which VESA mode is to be set. The supported pixel format is 32-bit RGBA, hence the available VESA mode can only be one of the following: + * FRAMEBUFFER_VESA_MODE_10F * FRAMEBUFFER_VESA_MODE_112 * FRAMEBUFFER_VESA_MODE_115 -- 2.25.1