<?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</title>
        <description></description>
        <link>http://wiki.osll.ru/</link>
        <lastBuildDate>Tue, 05 May 2026 12:57:16 +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>binutils support for Xtensa</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:binutils-xtensa?rev=1710762446&amp;do=diff</link>
            <description>binutils support for Xtensa

	*  git tree: &lt;https://github.com/jcmvbkbc/binutils-gdb-xtensa&gt;

FDPIC support

	*  [+] static linking
	*  [+] PDE
	*  [+] PIE
	*  [±] PLT and lazy binding
	*  [+] TLS

FDPIC instruction sequences

Local call

Default local call


+0:     movi    tmp, target@GOT
+3:     add     tmp, tmp, localGOTptr
+5:     l32i    tmp, tmp, 0
+7:     mov     GOTptr, localGOTptr
+9:     callx0  tmp</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 18 Mar 2024 14:47:26 +0000</pubDate>
        </item>
        <item>
            <title>OSLL/ESR</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:esr?rev=1470678794&amp;do=diff</link>
            <description>OSLL/ESR

Технологии

	*  eCos -- операционная система реального времени; &lt;http://ecos.sourceware.org/docs.html&gt; ; &lt;http://en.wikipedia.org/wiki/ECos&gt;
	*  redboot -- загрузчик из eCos; &lt;http://sourceware.org/redboot/&gt;
	*  buildroot -- система сборки, на основе которой сделан linuxcrater;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>GCC support for Xtensa</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:gcc-xtensa?rev=1679023344&amp;do=diff</link>
            <description>GCC support for Xtensa

	*  Git tree: &lt;https://github.com/jcmvbkbc/gcc-xtensa&gt;

Compiler build for full testing

gcc testsuite requires libc, so the easiest way is the following:

	*  build toolchain with libc, e.g. by the buildroot
	*  configure and build gcc with sysroot of that toolchain:</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Fri, 17 Mar 2023 06:22:24 +0000</pubDate>
        </item>
        <item>
            <title>GLIBC support for Xtensa</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:glibc-xtensa?rev=1523644042&amp;do=diff</link>
            <description>GLIBC support for Xtensa

Testing

	*  &lt;https://sourceware.org/glibc/wiki/Release/2.26&gt;
	*  &lt;https://fossies.org/linux/glibc/math/README.libm-test&gt;

Testsuite results

Testsuite may be run natively (on linux system running on hardware or in system emulation) or on linux-user emulation. First is very accurate, but slow. Second is fast (10h wall clock for all tests) but not so accurate.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Fri, 13 Apr 2018 21:27:22 +0000</pubDate>
        </item>
        <item>
            <title>Hardware notes</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:hardware?rev=1470678794&amp;do=diff</link>
            <description>Hardware notes

ARM-USB-TINY-H

Chip datasheet: &lt;http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT2232H.pdf&gt;

Connector pinout


      9 5 1
 ----^^----
/oooooooooo\
\oooooooooo/
 ----------
        6 2


Low voltage UART mode

Pin functions

	*  1, 2: Vcc (connected)
	*  4, 6 and the rest of the low row: GND (connected)</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Opensource compiler for motorola internal language</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:isl?rev=1470678794&amp;do=diff</link>
            <description>Opensource compiler for motorola internal language

 Git repo (http)

 Project tracker

Orthogonal aspects

Orthogonal aspects must be decoupled to the maximal possible extent:

	*  output language
	*  output file structure
	*  user data structures and field names
	*  memory allocation</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Политика сосуществования библиотек собранных ...</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:lib_coexistence_policy?rev=1470678794&amp;do=diff</link>
            <description>Политика сосуществования библиотек собранных разными компиляторами c++

Ситуация

ОС: МСВС. Имеются gcc-2.95.4, qt-2.3, qt-3.3. Имеется другая версия gcc и набор библиотек (в т.ч. на с++), скомпилированных им. Хочется иметь возможность установить в систему как $0&quot;, то он после установки LD_LIBRARY_PATH запускает программу &quot;$…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>мсвс</category>
        <category>rfc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Linux developer starter page</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-dev-start?rev=1470678794&amp;do=diff</link>
            <description>Linux developer starter page

Development process

	*  Read Documentation/SubmittingPatches
	*  Patch format
	*  Patch rules
	*  linux-wireless process

Mailing lists

	*  VGER

Code

	*  Linux kernel archives
	*  Linux GIT
	*  Linux cross reference

Guides/HOWTOs

	*  The Linux Documentation Project
	*  Linux Weekly News articles indexed by topic

Books

	*  Understanding the Linux Kernel, 3rd edition
	*  Linux Kernel Development, 3rd edition</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Linux memory management summary</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-mm?rev=1470678794&amp;do=diff</link>
            <description>Linux memory management summary

Every part of process address space is some sort of mapping.

Memory accounting

ps terminology:

	*  %mem (pmem) -- ratio of the process’s resident set size  to the physical memory on the machine, expressed as a percentage;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Linux port for Xtensa</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux-xtensa?rev=1689132320&amp;do=diff</link>
            <description>Linux port for Xtensa

	*  Linux git tree: &lt;https://github.com/jcmvbkbc/linux-xtensa&gt;
	*  Build/test tools git tree: &lt;https://github.com/jcmvbkbc/xtensa-linux-test&gt;
	*  Toolchain build scripts/overlays git tree: &lt;https://github.com/jcmvbkbc/xtensa-toolchain-build&gt;
	*  Patch review check list
	*  Patch/pull request check list
	*  Rootfs notes

TODO

	*  dynamic ftrace
	*  kgdb/kdb
	*  kexec
	*  NX

In Progress

	*  kprobes
	*  Booting linux on ESP32
	*  Booting linux on ESP32s3
	*  Booting wifi-e…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Wed, 12 Jul 2023 06:25:20 +0000</pubDate>
        </item>
        <item>
            <title>GNU/Linux, rootfs </title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:linux128?rev=1470678794&amp;do=diff</link>
            <description>GNU/Linux, rootfs &lt;128 Mb

Проблема: имеется множество разных конфигураций машин, на которых хочется запускать свой софт. Общее в них -- это PC, x86, не хуже Pentium-200. Хочется иметь базовую конфигурацию, которая будет работать</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>Little things every day</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:little-things?rev=1470678794&amp;do=diff</link>
            <description>Little things every day

The idea

I've so many things that I'd like to get familiar with. At least to know them practically.
But it always turns that there's no time for the little ones and not enough skills for the big ones.

So, I'm going to pick every day one thing off this heap, cut it so that it would get 1.5 - 2 hours to complete it and do it!</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>LiveCD Wi-Fi router</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:livecd-router?rev=1470678794&amp;do=diff</link>
            <description>LiveCD Wi-Fi router

Сделано по мотивам старой песни “хочу чтобы работало искаропки”.

Внешний интерфейс -- eth0, внутренний -- wlan0.

То что помечено  FILL IN YOURS</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:14 +0000</pubDate>
        </item>
        <item>
            <title>LLVM/clang-based compiler for multiclet</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:llvm-mc?rev=1470678795&amp;do=diff</link>
            <description>LLVM/clang-based compiler for multiclet

Links

	*  R1 ISA
	*  Writing an LLVM Backend</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>802.11s mesh powersaving for linux</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:mesh-power?rev=1470678795&amp;do=diff</link>
            <description>802.11s mesh powersaving for linux

Scope

	*  Implement non-realtime powersaving features of 802.11s draft:
		*  powersaving level indication;
		*  traffic buffering for sleeping peers;
		*  TIM/DTIM in beacons;
		*  peer service period;

	*  Provide powersaving level control on MSTA/peer link basis;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>Booting linux on qemu-mpc85xx on x86</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:mpc85xx-qemu-linux?rev=1470678795&amp;do=diff</link>
            <description>Booting linux on qemu-mpc85xx on x86

Even though qemu have ppce500_mpc8544ds board inside, it relies on kvm to manage MMU stuff. Thus to run it one need PPC host (correct me if I'm wrong).
Let's try to emulate BookE MMU in qemu and boot linux.

Plan</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>NORCPU hackme challenge</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:norcpu?rev=1470678795&amp;do=diff</link>
            <description>NORCPU hackme challenge

	*  NORCPU hackme #1
	*  NORCPU hackme #2
	*  My solution</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>N8x0 support in linux-omap</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:omap-support-pieces?rev=1470678795&amp;do=diff</link>
            <description>N8x0 support in linux-omap

Current kernel: 2.6.35

Rootfs and kernel config

Startup plan

	*  [2/3] find optimal debugging techniques and real HW/qemu split;
	*  [3/4] make minimal working/debuggable configuration;
	*  [0] compile domain glossary.

Debug interfaces

Subsystems' status</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>Reverse-engineering p54spi firmware</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:p54spi-firmware-re?rev=1470678795&amp;do=diff</link>
            <description>Reverse-engineering p54spi firmware

It's just for fun. And maybe to fix SPI transfer alignment bug. And to find how the things are done in such devices.

And definitely to get acquainted with ARM assembly.

Firmware is loaded at 0x20000.
arm-linux-gnu-objdump -b binary -m arm -D 2.13.0.0.a.13.14.arm</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>QEMU support for Xtensa</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:qemu-target-xtensa?rev=1705854179&amp;do=diff</link>
            <description>QEMU support for Xtensa

	*  Git tree: &lt;https://github.com/OSLL/qemu-xtensa&gt;
	*  Official QEMU wiki feature page: &lt;http://wiki.qemu.org/Features/Xtensa&gt;
	*  Official xtensa linux wiki page: &lt;https://wiki.linux-xtensa.org/index.php?title=Xtensa_on_QEMU&gt;

Description

qemu/target-xtensa is a project aimed at development of a free simulator for Tensilica Xtensa processor family.

Although xtensa instruction set specification is open and there's even linux port for xtensa there were no free simulato…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Sun, 21 Jan 2024 19:22:59 +0000</pubDate>
        </item>
        <item>
            <title>SSH over HTTP proxy: connection issue</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:ssh-over-http-proxy?rev=1470678795&amp;do=diff</link>
            <description>SSH over HTTP proxy: connection issue

Setup

SSH client tries to connect to SSH server through HTTP proxy that supports method CONECT (using e.g. corkscrew).

Symptoms

SSH client establishes TCP connection, but after a while disconnects with message</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>UNIX и инновационность</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:unix_and_innovation?rev=1470678795&amp;do=diff</link>
            <description>UNIX и инновационность

Преамбула

Мне довелось поучаствовать в неформальной дискуссии, начавшейся с обсуждения предпочтений в синтаксисе ассемблерных исходников</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>Wine под МСВС</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:wine_mcbc?rev=1470678795&amp;do=diff</link>
            <description>Wine под МСВС

Начало истории для меня

&lt;http://etersoft.ru&gt;

Проблемы времени выполнения

Первоначальный запуск wine неполностью инициализирует ~/.wine

Симптомы:


$ wine
WINE@Etersoft 1.0.8
First running... Using WINEPREFIX=/home/dumb/.wine
Creating default file tree...
/usr/bin/wine: line 194:  2506 Segmentation fault      WINESAFE=yes &quot;${WINELOADER}&quot; rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 wine.inf
/usr/bin/wine: line 195:  2509 Segmentation fault      WINESAFE=yes &quot;…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>мсвс</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
        <item>
            <title>Booting xtensa linux on qemu</title>
            <link>http://wiki.osll.ru/doku.php/etc:users:jcmvbkbc:xtensa-linux?rev=1470678795&amp;do=diff</link>
            <description>Booting xtensa linux on qemu

It boots:


parse_bootparam(phys_tag:fe000020): 
Linux version 2.6.29-rc7-ga0f0129-dirty (dumb@octofox.metropolis) (gcc version 4.4.5 (GCC) ) #10 Tue Jun 21 23:13:31 MSD 2011
bootmem_init: sysmem.bank[i:0].{type:0, start:0x1000, end:0x3000}
bootmem_init: sysmem.bank[i:1].{type:0, start:0x142000, end:0x8000000}
bootmem_init: min_low_pfn:0x1, max_low_pfn:0x8000, max_pfn:0x8000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32480
Kernel command li…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>etc:users:jcmvbkbc</category>
            <pubDate>Mon, 08 Aug 2016 20:53:15 +0000</pubDate>
        </item>
    </channel>
</rss>
