<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://etherboot.org/dokuwiki-2017-02-19b/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://etherboot.org/dokuwiki-2017-02-19b/feed.php">
        <title>Etherboot/gPXE Wiki e820irc</title>
        <description></description>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/</link>
        <image rdf:resource="http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico" />
       <dc:date>2026-04-18T03:39:57-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/dokuwiki-2017-02-19b/e820irc/irc_logs_for_e820_issue?rev=1150350630&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico">
        <title>Etherboot/gPXE Wiki</title>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/</link>
        <url>http://etherboot.org/dokuwiki-2017-02-19b/lib/tpl/monobook/images/favicon.ico</url>
    </image>
    <item rdf:about="http://etherboot.org/dokuwiki-2017-02-19b/e820irc/irc_logs_for_e820_issue?rev=1150350630&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T22:50:30-07:00</dc:date>
        <title>e820irc:irc_logs_for_e820_issue</title>
        <link>http://etherboot.org/dokuwiki-2017-02-19b/e820irc/irc_logs_for_e820_issue?rev=1150350630&amp;do=diff</link>
        <description>(14:07:39) alanshieh: I could not find a KEEP_IT_REAL option in Etherboot 5.4, so I am going to build a call stub into 16:32 protected mode.
(14:10:32) alanshieh: Also, I don't know if adding an interface to export segment limits like we talked about is strictly needed; I think it's possible to use a flat (4GB) segment limit, and use the holes in the e820 output from ksyslog() to infer the possible memory that the PXE stack might need to use, and map in those holes from the undi-user program.
(1…</description>
    </item>
</rdf:RDF>
