<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs.intenogroup.com/juci/v4.1.x/en/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/feed.php">
        <title>V4.1.x sw</title>
        <description></description>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/</link>
        <image rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/lib/tpl/inteno/images/favicon.ico" />
       <dc:date>2026-04-03T19:54:35+0200</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/blocks?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/broadcom?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/iopsys?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/mediatek?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/openwrt?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/relation?rev=1574428944&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.intenogroup.com/juci/v4.1.x/en/sw/start?rev=1574428944&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/lib/tpl/inteno/images/favicon.ico">
        <title>V4.1.x</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/</link>
        <url>https://docs.intenogroup.com/juci/v4.1.x/en/lib/tpl/inteno/images/favicon.ico</url>
    </image>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/blocks?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Iopsys building blocks</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/blocks?rev=1574428944&amp;do=diff</link>
        <description>Iopsys building blocks

Iopsys uses a combination of different building blocks to achieve the optimal results.

Overview

The bulding blocks in iopsys are in part developed inhouse, and in parts taken from different sources, such as OpeWRT.

[enter image description here]

Orange blocks are made by inteno. Light blue are OpenWRT blocks that have been integrated to work with inteno SDK. The Asterisk pbx has been integrated by inteno into iopsys to support Voip.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/broadcom?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Broadcom Integration</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/broadcom?rev=1574428944&amp;do=diff</link>
        <description>Broadcom Integration

The Broadcom SDK is integrated into iopsys in its entirety as a package.

Overview

To integrate Broadcom into the iopsys sdk.

The whole Broadcom sdk has become its own package.

[Iopsys Broadcom]

This packet will compile a kernel and drivers that are then moved into the iopsys user space.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/iopsys?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>What is iopsys</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/iopsys?rev=1574428944&amp;do=diff</link>
        <description>What is iopsys

Iopsys takes the OpenWRT build system and adds it own packages and targets to handle the closed source architecture of the different chip vendors. Iopsys enables other chip vendors closed SDK’s to be integrated into the open architecture of OpenWRT.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/mediatek?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Mediatek Integration</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/mediatek?rev=1574428944&amp;do=diff</link>
        <description>Mediatek Integration

The integration with Mediatek uses a combination of OpenWRT and Mediatek proprietary drivers.

Overview

The mediatek integration uses all the tool chains and kernels from OpenWRT.

Iopsys adds the integrated proprietary drivers from mediatek into the OpenWRT build system.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/openwrt?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>OpenWRT</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/openwrt?rev=1574428944&amp;do=diff</link>
        <description>OpenWRT

OpenWRT is a linux distribution for embedded device based on the Linux kernel, primarily used for devices that route network traffic.

Overview

OpenWRT's main component is a build system that can build images for several different hardware models. The build system has besides the overall toolchain and build environment three main components: targets, packages, and feeds.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/relation?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Iopsys and OpenWRT</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/relation?rev=1574428944&amp;do=diff</link>
        <description>Iopsys and OpenWRT

Overview

Iopsys being based on openwr't starts with clean OpenWRT sdk and then add a feed manifesto that overlays on top of standard OpenWRT. Making it a iopsys SDK. The manifesto adds new targets(board profiles), feeds and packages.</description>
    </item>
    <item rdf:about="https://docs.intenogroup.com/juci/v4.1.x/en/sw/start?rev=1574428944&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-11-22T14:22:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Software Design &amp; Architecture</title>
        <link>https://docs.intenogroup.com/juci/v4.1.x/en/sw/start?rev=1574428944&amp;do=diff</link>
        <description>Software Design &amp; Architecture

/* TODO: Introduction */





OpenWRT

OpenWRT is a linux distribution for embedded device based on the Linux kernel, primarily used for devices that route network traffic.

→ Read more...



What is iopsys

Iopsys takes the OpenWRT build system and adds it own packages and targets to handle the closed source architecture of the different chip vendors. Iopsys enables other chip vendors closed SDK’s to be integrated into the open architecture of OpenWRT.</description>
    </item>
</rdf:RDF>
