<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://wiki.osll.ru/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>Open Source &amp; Linux Lab etc:users:jcmvbkbc:linux-xtensa</title>
        <description></description>
        <link>http://wiki.osll.ru/</link>
        <lastBuildDate>Wed, 08 Jul 2026 08:30:03 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>http://wiki.osll.ru/lib/tpl/dokuwiki/images/favicon.ico</url>
            <title>Open Source &amp; Linux Lab</title>
            <link>http://wiki.osll.ru/</link>
        </image>
        <item>
            <title>Booting linux on ESP32</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:esp32?rev=1684889961&amp;do=diff</link>
            <description>Booting linux on ESP32

See Booting linux on ESP32s3 for an updated version with userspace.

Sources:

	*  &lt;https://github.com/jcmvbkbc/esp-idf/tree/linux&gt;
	*  &lt;https://github.com/jcmvbkbc/linux-xtensa/tree/xtensa-5.19-esp32&gt;
	*  buildroot mainline


$ cd examples/get-started/linux_boot
$ idf.py build
$ idf.py -p /dev/ttyUSB0 flash
$ parttool.py -p /dev/ttyUSB0 write_partition --partition-name linux --input xip-esp32-esp32/arch/xtensa/boot/xipImage
$ parttool.py -p /dev/ttyUSB0 write_partition -…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Wed, 24 May 2023 03:59:21 +0000</pubDate>
        </item>
        <item>
            <title>Booting linux on ESP32s3</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:esp32s3?rev=1717898788&amp;do=diff</link>
            <description>Booting linux on ESP32s3

Sources:

	*  &lt;https://github.com/jcmvbkbc/xtensa-dynconfig/tree/original&gt;
	*  &lt;https://github.com/jcmvbkbc/config-esp32s3&gt;
	*  &lt;https://github.com/jcmvbkbc/esp-hosted/tree/ipc-5.1.1&gt;
	*  &lt;https://github.com/jcmvbkbc/linux-xtensa/tree/xtensa-6.10-rc2-esp32&gt;
	*  &lt;https://github.com/jcmvbkbc/binutils-gdb-xtensa/tree/xtensa-fdpic-abi-spec-1.4&gt;
	*  &lt;https://github.com/jcmvbkbc/gcc-xtensa/tree/xtensa-fdpic-abi-spec-1.4&gt;
	*  &lt;https://github.com/jcmvbkbc/uclibc-ng-xtensa/tree/…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Sun, 09 Jun 2024 05:06:28 +0000</pubDate>
        </item>
        <item>
            <title>Booting wifi-enabled linux on ESP32s3</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:esp32s3wifi?rev=1695112991&amp;do=diff</link>
            <description>Booting wifi-enabled linux on ESP32s3

Script that builds and flashes everything: &lt;https://github.com/jcmvbkbc/esp32-linux-build/blob/master/rebuild-esp32s3-linux-wifi.sh&gt;

What can be done after booting:

Joining open network


# ip link set espsta0 up
# iw dev espsta0 connect &lt;ssid&gt;
# udhcpc -i espsta0


Joining WPA2 network


# ip link set espsta0 up
# cat &gt; /tmp/ws.conf &lt;&lt;EOF
network={
        ssid=&quot;ssid-name&quot;
        psk=&quot;password&quot;
}
EOF
# wpa_supplicant -i espsta0 -c /tmp/ws.conf &amp;
# udhcp…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Tue, 19 Sep 2023 11:43:11 +0000</pubDate>
        </item>
        <item>
            <title>Issues</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:issues?rev=1470678816&amp;do=diff</link>
            <description>Issues

	*  multihit_exception -- fixed
	*  signal_delivery_scheduling_atomic_tif_flags_checking_on_kernel_exit -- fixed
	*  strange_tlb_values_on_smp -- fixed
	*  intercore_ccount_synchronization</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Mon, 08 Aug 2016 20:53:36 +0000</pubDate>
        </item>
        <item>
            <title>Patch/pull request check list</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:patch-pull-checklist?rev=1580882602&amp;do=diff</link>
            <description>Patch/pull request check list

Does it build for

	*  allmodconfig
	*  MMUv2/MMUv3, CONFIG_MMU on/off
	*  all platforms (xtfpga, iss, xt2000)
	*  CONFIG_OF on/off
	*  CONFIG_HIGHMEM on/off
	*  CONFIG_SMP on/off
	*  CONFIG_MODULES on/off
	*  cache aliasing core</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Wed, 05 Feb 2020 09:03:22 +0000</pubDate>
        </item>
        <item>
            <title>Patch review check list</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:patch-review-checklist?rev=1470678794&amp;do=diff</link>
            <description>Patch review check list

	*  If it has inline asm
		*  Does it use specific instructions, does it correctly handle cores w/o such instructions
		*  Does it correctly specify argument constraints (e.g. earlyclobber (=&amp;) arguments)
		*  Does it use possibly reserved registers (e.g. a7 with CONFIG_FRAME_POINTER)</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Rootfs notes</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:rootfs?rev=1678996583&amp;do=diff</link>
            <description>Rootfs notes

Rootfs in FLASH (UBIFS)

The easiest way to generate UBIFS image is by setting BR2_TARGET_ROOTFS_UBIFS to y in the buildroot config. Buildroot will also need the following file system parameters, that can be queried with mtdinfo tool:</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Thu, 16 Mar 2023 22:56:23 +0000</pubDate>
        </item>
        <item>
            <title>etc:users:jcmvbkbc:linux-xtensa:signal_delivery_scheduling_atomic_tif_flags_checking_on_kernel_exit</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:signal_delivery_scheduling_atomic_tif_flags_checking_on_kernel_exit?rev=1470678794&amp;do=diff</link>
            <description>msgctl06    1  FAIL  :  msgctl(msqid, IPC_STAT, &amp;buf) failed errno = 22
[  246.090000] BUG: sleeping function called from invalid context at /home/dumb/ws/tensilica/linux/linux/include/linux/freezer.h:46
[  246.090000] in_atomic(): 0, irqs_disabled(): 1, pid: 1996, name: msgctl07
[  246.090000]
Stack: d5f93d90 d5f93d70 00000004 3fa9a8f4 d5f93d70 00000004 00000006 00000018
       9001720d d5f93db0 00060403 00000001 00000001 000007cc d4c12900 3fa9a8f4
       900030d0 d5f93dd0 d4c60504 d4c60000 000…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>etc:users:jcmvbkbc:linux-xtensa:strange_tlb_values_on_smp</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:strange_tlb_values_on_smp?rev=1470678794&amp;do=diff</link>
            <description>update_mmu_cache is used to update TLB entries after do_pagefault. It used


       invalidate_itlb_mapping(addr);
       invalidate_dtlb_mapping(addr);


to invalidate TLB entry that appeared with the fault. This works with single CPU, but in SMP case update_mmu_cache may be called on a CPU different from that that took the exception. Without TLB sanity debugging this leads to looping over the instruction that caused initial pagefault until the wrong TLB entry is kicked out. With TLB sanity deb…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>XIP kernel</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa:xip?rev=1581019773&amp;do=diff</link>
            <description>XIP kernel
 cat &lt;(head -c 96M /dev/zero) builds/xip-nommu-kc705-de212/arch/xtensa/boot/xipImage /dev/zero | head -c 128M &gt; xip-nommu-kc705-de212.image
 # or with CRAMFS rootfs:
 cat &lt;(head -c 96M &lt;(cat /home/jcmvbkbc/ws/tensilica/buildroot/build-xtensa-nommu-de108/images/rootfs.cramfs /dev/zero ) ) \
     builds/xip-nommu-kc705-de212/arch/xtensa/boot/xipImage /dev/zero | head -c 128M &gt; xip-nommu-kc705-de212.image
 qemu/qemu-system-xtensa -cpu de212 -M kc705-nommu -nographic -monitor none -serial…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc:linux-xtensa</category>
            <pubDate>Thu, 06 Feb 2020 23:09:33 +0000</pubDate>
        </item>
    </channel>
</rss>
