<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://192.168.180.206:8001/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="http://192.168.180.206:8001/feed.php">
        <title>wiki.niziak.spox.org - sw:yocto:kernel</title>
        <description></description>
        <link>http://192.168.180.206:8001/</link>
        <image rdf:resource="http://192.168.180.206:8001/_media/wiki:dokuwiki.svg" />
       <dc:date>2026-05-13T04:23:31+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://192.168.180.206:8001/sw:yocto:kernel:headers?rev=1762360586&amp;do=diff"/>
                <rdf:li rdf:resource="http://192.168.180.206:8001/sw:yocto:kernel:module?rev=1642083906&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://192.168.180.206:8001/_media/wiki:dokuwiki.svg">
        <title>wiki.niziak.spox.org</title>
        <link>http://192.168.180.206:8001/</link>
        <url>http://192.168.180.206:8001/_media/wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="http://192.168.180.206:8001/sw:yocto:kernel:headers?rev=1762360586&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-05T16:36:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>headers</title>
        <link>http://192.168.180.206:8001/sw:yocto:kernel:headers?rev=1762360586&amp;do=diff</link>
        <description>headers

kernel include vs libc include

How to use header file from current kernel not from distro /usr/include/linux ?
Package linux-libc-headers provides /usr/include.

This is a description of this use case:
Using Headers to Interface with Devices

There is no clean solution. If vendor provides custom kernel also should provides custom (patched)</description>
    </item>
    <item rdf:about="http://192.168.180.206:8001/sw:yocto:kernel:module?rev=1642083906&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-01-13T14:25:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>module</title>
        <link>http://192.168.180.206:8001/sw:yocto:kernel:module?rev=1642083906&amp;do=diff</link>
        <description>module

out of tree

Common tasks are provided by module.bbclass. See poky/plain/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb


SUMMARY = &quot;Example of how to build an external Linux kernel module&quot;
DESCRIPTION = &quot;${SUMMARY}&quot;
LICENSE = &quot;GPLv2&quot;
LIC_FILES_CHKSUM = &quot;file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e&quot;

inherit module

SRC_URI = &quot;file://Makefile \
           file://hello.c \
           file://COPYING \
          &quot;

S = &quot;${WORKDIR}&quot;

# The inherit of module.bbclass will autom…</description>
    </item>
</rdf:RDF>
