MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SMP-on-Xtensa",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "35": {
                "pageid": 35,
                "ns": 0,
                "title": "RedBoot Example",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= Booting Linux Using RedBoot =\n\nHere is an example series of steps that setup RedBoot to boot Linux on an\nXT-AV60 (LX60) or XT-AV200 (LX200) board.\n\n*  Build Linux for the LX60 (see the [http://wiki.linux-xtensa.org/index.php/Buildroot_Build_Instructions Buildroot Build Instructions]).   \n**  When configuring the kernel, include <tt>ip=bootp</tt> or <tt>ip=dhcp</tt> in the kernel command line, as desired.\n\n*  Flash RedBoot on the board (see Tensilica XT-AV60 (LX60) docs for how).\n** Reset the board.\n** Wait for RedBoot to boot to its prompt.\n*  The Tensilica docs show two methods of putting RedBoot into flash using OCD.  If you used RedBoot to flash itself, the flash filesystem is probably already initialized.  Otherwise you have to init the flash filesystem.  To check just do:\n RedBoot> fis list\nand see whether you get a useful list of flash images.  If not, do:\n RedBoot> fis init -f\n y\n RedBoot> fconfig -i -l\n y\n* Download the kernel image <tt>''<build>''/arch/xtensa/boot/zImage.redboot</tt> to address <tt>0xd1000000</tt>.  For example, put that file on a TFTP server, and load it using RedBoot like this:\n RedBoot> load -r -b 0xd1000000 zImage.redboot\n(use the proper pathname for accessing the file over TFTP instead of <tt>zImage.redboot</tt>, as needed).\n* Now that the kernel image is in memory, you can execute it directly:\n RedBoot> exec -w 3 0xd1000000\n* Or, you can instead put the image in flash so you can boot it multiple times without loading again:\n RedBoot> fis create -b 0xd1000000 -l 0xNNNNNN -e 0xd1000000 -r 0xd1000000 linux\nwhere 0xNNNNNN is the size of the downloaded image\nand \"linux\" is just some name for the image.  (You can have multiple\nimages with different names, as flash space allows;\nuse the same name in the <tt>fis load <name></tt> command below.)\n* You might double check that the image is now there.  Something like:\n RedBoot> fis list\n Name              FLASH addr  Mem addr    Length      Entry point\n RedBoot           0xF8000000  0xF8000000  0x00020000  0x00000000\n RedBoot[backup]   0xF8020000  0xF8020000  0x00020000  0x00000000\n RedBoot config    0xF83E0000  0xF83E0000  0x00001000  0x00000000\n FIS directory     0xF83F0000  0xF83F0000  0x00010000  0x00000000\n linux             0xF8020000  0xD1000000  0x001C0000  0xD1000000\n RedBoot>\n* You can reload the image from flash to memory using:\n RedBoot> fis load linux\n* Now the fun part.  You can setup RedBoot with a script to load the image (from network or flash) and execute it, automatically at reset.  Here is an example that loads from flash, with a timeout set to 5 seconds so that you can Ctrl-C to avoid booting Linux if you want a boot prompt:\n RedBoot> fconfig\n Run script at boot: true\n Boot script:\n Enter script, terminate with empty line\n  >> fis load linux\n  >> exec -w 3 0xd1000000\n  >>\n Boot script timeout (1000ms resolution): 5\n Use BOOTP for network configuration: true\n Console baud rate: 38400\n GDB connection port: 9000\n Network debug at boot time: false\n Update RedBoot non-volatile configuration - are you sure (y/n)? y\n ... Erase from 0xf83e0000-0xf83e1000: .\n ... Program from 0xd3f6e000-0xd3f6f000 at 0xf83e0000: .\n RedBoot>\n(although I left BOOTP enabled above, you might not need it\nif always loading from flash)\n*  Now you should be able to reset the board, and see RedBoot booting, and see Linux automatically booting afterwards.\n*  At the Linux login prompt, login as root as usual"
                    }
                ]
            },
            "34": {
                "pageid": 34,
                "ns": 0,
                "title": "Repository Access",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= Access to GIT Repositories =\n\nThe <tt>linux-xtensa.org</tt> site hosts a number of GIT repositories.\nThey provide access to the latest sources for their respective projects.\nAlternatively, one can download\n[[Buildroot_Snapshots|snapshot releases]] which\nare updated much less frequently.\n\n\nThe following sections describe how to access these source repositories.\n\n== Accessing buildroot sources ==\n\nBuildroot is used to build the toolchain and root filesystem.\nThe following downloads a copy of the entire GIT repository:\n\n   $ git clone git://git.linux-xtensa.org/git/buildroot/buildroot-xtensa buildroot\n\nThose with write access to the repository should use the <tt>git+ssh</tt> method instead, like this:\n\n   $ git clone git+ssh://git.linux-xtensa.org/git/buildroot/buildroot-xtensa buildroot\n\nCommits to this tree are automatically posted to the\n[http://lists.linux-xtensa.org/mailman/listinfo/buildroot-xtensa-commits buildroot-xtensa-commits list].\n\n== Accessing Linux kernel sources ==\n\nThere are normally multiple Linux kernel trees to choose from.\nAt the time of writing, the <tt>xtensa-2.6.24</tt> tree is the lastest \"official\" tree.\nThis tree is based on the released 2.6.24 kernel from <tt>kernel.org</tt>.\nHowever, most of the activity currently is in an unofficial <tt>2.6.29-smp</tt> tree.\n\nTo get the <tt>xtensa-2.6.24</tt> tree into directory ''<dir>'' (which must not already exist),\ndo this:\n\n   $ git clone git://git.linux-xtensa.org/git/kernel/xtensa-2.6.24 <dir>\n\nThis creates and populates the ''<dir>'' directory.  If ''<dir>'' is omitted, it defaults to <tt>xtensa-2.6.24</tt> (the last non-extension part of the cloned path).\nThose with write access to the repository should use the <tt>git+ssh</tt> method instead, like this:\n\n   $ git clone git+ssh://git.linux-xtensa.org/git/kernel/xtensa-2.6.24 <dir>\n\nCommits to this tree are automatically posted to the\n[http://lists.linux-xtensa.org/mailman/listinfo/linux-xtensa-devel-commits linux-xtensa-devel-commits list].\n\n== Accessing U-Boot bootloader sources ==\n\nA preliminary version of U-Boot for the Xtensa architecture is available.\nThe following downloads a copy of the entire GIT repository:\n\n   $ git clone git://git.linux-xtensa.org/git/u-boot/u-boot-xtensa.git u-boot\n\nThose with write access to the repository should use the <tt>git+ssh</tt> method instead, like this:\n\n   $ git clone git+ssh://git.linux-xtensa.org/git/u-boot/u-boot-xtensa.git u-boot\n\n'' '''PLEASE NOTE:'''  These paths are likely to change when the port becomes official.''\n\nCommits to this tree are not yet automatically posted to any list.\n\n== Write Access ==\n\nOnly a small number of core developers have write access to these\nrepositories.  To submit changes, you are encouraged to submit patches to\nthe [http://lists.linux-xtensa.org/mailman/listinfo/linux-xtensa linux-xtensa mailing list].\nContributors are expected to consistently provide\ngood patches, and have a certain level of involvement and commitment\nto the relevant project, before being considered for write access."
                    }
                ]
            }
        }
    }
}