<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://etherboot.org/wiki/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/wiki/feed.php">
        <title>Etherboot/gPXE Wiki</title>
        <description></description>
        <link>http://etherboot.org/wiki/</link>
        <image rdf:resource="http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico" />
       <dc:date>2026-04-20T10:21:50-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/peper/notes/usermode_explained?rev=1276560027&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/winnt_iscsi_debug?rev=1256856685&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week5?rev=1246318967&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/gentoo_iscsi?rev=1288102739&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/usermanual?rev=1153484238&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/stefanha/journal/week7?rev=1216754764&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dev/devmanual?rev=1153069275&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/winnt_aoe?rev=1221237603&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week6?rev=1247012725&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/memsearch?rev=1237991763&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week7?rev=1247424371&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/ubuntu_iscsi?rev=1282017316&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/3c90x_issues?rev=1235941387&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/user/mdc/yazzy_test?rev=1240323823&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/todo/audit-the-shifts?rev=1249937568&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wirelessboot/implementation?rev=1250187770&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/fedora_iscsi_install?rev=1262987191&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week7?rev=1247422887&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/bootingmemdisk?rev=1151246104&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dev/gdbstub?rev=1269836865&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/ubuntu_aoe?rev=1284725017&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/srp/sbft?rev=1249929545&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/pravin/journal/bkodebianiscsi?rev=1253932645&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/notes/protocol?rev=1243469113&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/balajirrao/start?rev=1213620343&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/info?rev=1211468627&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/dverkamp/start?rev=1213620302&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/start?rev=1213620225&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week3?rev=1276466097&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week2?rev=1276465962&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week5?rev=1257670478&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/alanshieh?rev=1155328305&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/ubuntu_iscsi2?rev=1295439988&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/user/less1?rev=1245022900&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/transfer?rev=1256859555&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week4?rev=1245648994&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/centos?rev=1203549701&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week12?rev=1250325409&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/notes/design?rev=1245707645&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/esxi4.1?rev=1279098899&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/iscsi_install?rev=1279061952&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/git-usage?rev=1213018019&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/meteger/project_plan/start?rev=1306078529&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/git-usage?rev=1301171639&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/fedora?rev=1194745234&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week2?rev=1307154612&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/ideas?rev=1301171675&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/hardwareissues?rev=1289686457&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/old_news?rev=1295848443&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/syslinux?rev=1287711153&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/romburning/tg3?rev=1204817294&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week6?rev=1309670055&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/faq/start?rev=1266093248&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/alan_s_test_/development_infrastructure?rev=0&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week3?rev=1213563625&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week1?rev=1243642455&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week9?rev=1248399250&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week2?rev=1244410427&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week1?rev=1213129744&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/notes/buildbot?rev=1243960224&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/elf-ebi-initramfs-lnxi-howto/the_kernel/config?rev=1240543027&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week8?rev=1279548888&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week3?rev=1245102634&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/e820irc/irc_logs_for_e820_issue?rev=1150350630&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/welcome?rev=1488916923&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/ideas?rev=1266081209&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/meteger/journal/week6?rev=1309692062&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week7?rev=1215977020&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week8?rev=1216587081&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week6?rev=1215281128&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/debian_and_ubuntu?rev=1197468691&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/romburning/vbox?rev=1263117024&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week9?rev=1216956856&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/weekc?rev=1219109616&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/stefanha/journal/week3?rev=1213614684&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/stefanha/journal/week6?rev=1215525430&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/pravin/journal/pxeknifedsl?rev=1244930730&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2006/nikhilcrao/proposal?rev=1210408438&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/win2000?rev=1195673213&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/winxp?rev=1235597722&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/peper/journal/week1?rev=1275781254&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/pravin/notes/start?rev=1261923489&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/start?rev=1301164255&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/pxechaining?rev=1279138185&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/nikhil/proposal?rev=1150397504&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/centos_iscsi_install?rev=1203552517&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/dverkamp/journal/week8?rev=1216395697&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/winvista?rev=1243982488&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/faq/drivers?rev=1266092397&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week5?rev=1215017420&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/stefanha/journal/week11?rev=1218382284&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/stefanha/journal/week1?rev=1212572815&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/balajirrao/notes/uhci_design?rev=1214476004&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/balajirrao/journal/week3?rev=1214622088&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/win2k8_iscsi_install?rev=1295727363&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week2?rev=1213130066&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/dverkamp/notes/start?rev=1211296510&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2008/mdeck/journal/week4?rev=1214415268&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/wrapup?rev=1269384603&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/notes/rtl8169.c?rev=1247019992&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/notes/skge.c?rev=1247426281&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week4?rev=1277062067&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week2?rev=1244444068&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_pe?rev=1244584288&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/peper/project_plan/start?rev=1276558273&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week4?rev=1308317325&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/people/xl0/gpxe-timeline?rev=1184419730&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week11?rev=1281388373&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2006/derekpryor/start?rev=1210408070&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week1?rev=1306543498&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/pravin/project_plan/start?rev=1244065734&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/journal/week7?rev=1278952666&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/meteger/journal/week9?rev=1311335326&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week4?rev=1245643204&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week12?rev=1281688284&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/project_plan/start?rev=1306068627&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/andreif/project_plan/start?rev=1273747598&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_xp_iscsi?rev=1244846817&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/burningroms/willem?rev=1240261509&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week10?rev=1280488499&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week2?rev=1275655624&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/pravin/journal/fedora11bko?rev=1248698141&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week1?rev=1275052553&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/cooldavid/journal/weekb2?rev=1274891765&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/peper/journal/week0?rev=1275416775&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/derekpryor?rev=1153510382&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/navigation?rev=1259439602&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/notes/scripting_doc/features_added?rev=1250407194&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/notes/3c90x.c?rev=1247021101&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2010/peper/notes/usermode_howto?rev=1281909532&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/project_plan/start?rev=1244305285&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dev/fnrec?rev=1272799751&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/qemupxeknife?rev=1243096987&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dev/netdriverapi?rev=1187473421&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wiki/syntax?rev=1488916923&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/notes/generic.c?rev=1247022714&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week1?rev=1244253873&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week5?rev=1308970189&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/win2k8_physical?rev=1256854825&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/notes/linux_mkbootfs?rev=1245419468&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/journal/week10?rev=1248987358&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/dverkamp/journal/week1?rev=1243903441&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week9?rev=1248805725&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/bochs?rev=1157026523&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week6?rev=1246855558&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot/win2k3?rev=1187995713&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week3?rev=1245131141&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week1?rev=1243917508&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2009/oremanj/journal/week5?rev=1246080402&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/pcmattman/notes/start?rev=1313458477&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico">
        <title>Etherboot/gPXE Wiki</title>
        <link>http://etherboot.org/wiki/</link>
        <url>http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico</url>
    </image>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/peper/notes/usermode_explained?rev=1276560027&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-14T17:00:27-07:00</dc:date>
        <title>soc:2010:peper:notes:usermode_explained</title>
        <link>http://etherboot.org/wiki/soc/2010/peper/notes/usermode_explained?rev=1276560027&amp;do=diff</link>
        <description>Piotr Jaroszyński: Usermode debugging under Linux

How usermode under Linux is done

Intro

Porting any code to a substantially different environment is the hardest when no other ports have been done yet. Fortunately gPXE already supports two ARCHs (</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/winnt_iscsi_debug?rev=1256856685&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-29T15:51:25-07:00</dc:date>
        <title>sanboot:winnt_iscsi_debug</title>
        <link>http://etherboot.org/wiki/sanboot/winnt_iscsi_debug?rev=1256856685&amp;do=diff</link>
        <description>Debugging Windows iSCSI boot

[A null-modem cable]

To debug Windows iSCSI boot problems, you will need a second Windows machine running windbg, and a null-modem cable to connect the two machines together via their serial ports.  The debugging machine does not need to be running the same version of Windows as the iSCSI-booting machine.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week5?rev=1246318967&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-29T16:42:47-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week5</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week5?rev=1246318967&amp;do=diff</link>
        <description>June 22: 
I started out the evening of the 22nd working on a debugging issue...

I asked rwcr for some help and he gladly provided it. The issue of the night was debugging why open (or any other procedure) was not being called at all. 

rwcr showed me how to hook up to to a gdbstub with udp debugging and I inserted an rtl8139b into my testing machine. After a while tracing variables and stepping into procedures, I found (again, with much help from rwcr) that the reference to netdevice that I was…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/gentoo_iscsi?rev=1288102739&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-26T07:18:59-07:00</dc:date>
        <title>sanboot:gentoo_iscsi</title>
        <link>http://etherboot.org/wiki/sanboot/gentoo_iscsi?rev=1288102739&amp;do=diff</link>
        <description>Introduction

Scope

This How-To is intended for anyone who wants to install Gentoo Linux on an iSCSI target.

What is covered:

	*  Connecting to the iSCSI target
		*  Installing a generic base system
		*  Installing the kernel
		*  Installing the bootloader</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/usermanual?rev=1153484238&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-21T05:17:18-07:00</dc:date>
        <title>usermanual</title>
        <link>http://etherboot.org/wiki/usermanual?rev=1153484238&amp;do=diff</link>
        <description>Etherboot User Manual

Ken Yap - Markus Gutschke - Version 5.2.2

Copyright (C) 2001,2002,2003 Ken Yap and Markus Gutschke

2003-09-30

Revision History

	*  Revision 5.2.2   2003-09-30   Revised by: KY
	*  Revision 5.2.0   2003-08-11   Revised by: KY</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/stefanha/journal/week7?rev=1216754764&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-22T12:26:04-07:00</dc:date>
        <title>soc:2008:stefanha:journal:week7</title>
        <link>http://etherboot.org/wiki/soc/2008/stefanha/journal/week7?rev=1216754764&amp;do=diff</link>
        <description>Stefan Hajnoczi: GDB Remote Debugging

Week 7

Milestones:

	*  [b44] Tested and clean for mainline review.
	*  [gpxelinux.0] Merge Award BIOS return-to-PXE workaround.

Tue Jul 8

Git commits:

	*  [e820] Full clipping of regions into fragments
	*  [e820] Clean up new e820 memory mangler

Progress on e820 memory map mangler.  I finally made the push for an e820 memory map mangler that can clip regions into fragments.  The existing e820 memory map mangler works well when gPXE hides the beginning…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-20T14:10:11-07:00</dc:date>
        <title>appnotes:srp_install</title>
        <link>http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff</link>
        <description>SCSI RDMA Protocol (SRP) improves the read performance in terms of throughput which is increased significantly for both random read with good locality and sequential read.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dev/devmanual?rev=1153069275&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T10:01:15-07:00</dc:date>
        <title>dev:devmanual</title>
        <link>http://etherboot.org/wiki/dev/devmanual?rev=1153069275&amp;do=diff</link>
        <description>EtherBoot developers' manual

This manual is probably outdated and needs some rework.

Submitted unchanged into this wiki to allow transition to the upcoming wiki-only website  by Anselm Martin Hoffmeister.

Revision information

Written by Ken Yap, Georg Baum</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/winnt_aoe?rev=1221237603&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-09-12T09:40:03-07:00</dc:date>
        <title>sanboot:winnt_aoe</title>
        <link>http://etherboot.org/wiki/sanboot/winnt_aoe?rev=1221237603&amp;do=diff</link>
        <description>Adding AoE boot support to Microsoft Windows

Installing the AoE initiator

You need to download and install the Windows AoE initiator (WinAoE).  Download the latest WinAoE package from &lt;http://winaoe.org/&gt; and extract the contents of the .zip file to a temporary directory.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week6?rev=1247012725&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-07T17:25:25-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week6?rev=1247012725&amp;do=diff</link>
        <description>June 29 6:45 PM:

Current status: Up until now, I have completed most of the data structure definitions, skge_probe(), and skge_open(). I am obviously quite behind compared to my project plan, but that is not something I can easily resolve; However; It does look like I will have time still left over at the end of writing the skge driver for some other prospects in this task. Possibly tg3?</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/memsearch?rev=1237991763&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-25T07:36:03-07:00</dc:date>
        <title>soc:2008:memsearch</title>
        <link>http://etherboot.org/wiki/soc/2008/memsearch?rev=1237991763&amp;do=diff</link>
        <description>Summer of Code Sample Interview Exercise

This is the question that was generally given as the first (and easiest) of several programming exercises during our interviews for Google Summer of Code 2008.  It requires applicants to demonstrate the ability to write in C code, including the use of pointers.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week7?rev=1247424371&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-12T11:46:11-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week7</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week7?rev=1247424371&amp;do=diff</link>
        <description>July 6: Fixed a bug which prevented using for and while statements split over multiple lines. The problem was that the cur_command variable stored the last line of an incomplete command. Fixed by concatenating incomplete lines before storing. AndyTim suggested that instead of a memory-intensive list, I just store the offset into the script for interesting lines. A problem with that is that it would act differently for scripts and interactive input. But, it will use a lot less memory. So, this is…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/ubuntu_iscsi?rev=1282017316&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-16T20:55:16-07:00</dc:date>
        <title>sanboot:ubuntu_iscsi</title>
        <link>http://etherboot.org/wiki/sanboot/ubuntu_iscsi?rev=1282017316&amp;do=diff</link>
        <description>Ubuntu 9.04 (Jaunty Jackalope) and 9.10  (Karmic Koala)

(this howto is based on the Debian Etch iSCSI howto with some major changes)

Introduction

This howto shows how to make an existing installation of a recent *buntu (ubuntu, kubuntu, edubuntu, xubuntu and so on) bootable over the network using iSCSI.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/3c90x_issues?rev=1235941387&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-01T13:03:07-07:00</dc:date>
        <title>appnotes:3c90x_issues</title>
        <link>http://etherboot.org/wiki/appnotes/3c90x_issues?rev=1235941387&amp;do=diff</link>
        <description>2009-03-01 mdc
  Since the gPXE driver has been rewritten, this file is no longer
  accurate, but contains some potentially useful information that 
  should be cleaned up and integrated into the wiki.

	Instructions for use of the 3C90X driver for EtherBoot

		Original 3C905B support by:
			Greg Beeley (Greg.Beeley@LightSys.org),
			LightSys Technology Services, Inc.
			February 11, 1999

		Updates for 3C90X family by:
			Steve Smith (steve.smith@juno.com)
			October 1, 1999

		Minor documentat…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wiki/user/mdc/yazzy_test?rev=1240323823&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-21T07:23:43-07:00</dc:date>
        <title>wiki:user:mdc:yazzy_test</title>
        <link>http://etherboot.org/wiki/wiki/user/mdc/yazzy_test?rev=1240323823&amp;do=diff</link>
        <description>Introduction

gPXE is a new version of the well know Etherboot project.

The project created network booting code that allows computers to load their operating system from a network.

The code can be stored in a number of places, including BIOS Flash, EPROMs, floppy, CD, HD, or other bootable media.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/todo/audit-the-shifts?rev=1249937568&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-10T13:52:48-07:00</dc:date>
        <title>todo:audit-the-shifts</title>
        <link>http://etherboot.org/wiki/todo/audit-the-shifts?rev=1249937568&amp;do=diff</link>
        <description>Todo: Audit the use of &lt;&lt; and &gt;&gt; (shift) operators in gPXE

Per a discussion by mcb30:


[3:11pm] mcb30: rwcr: I am puzzled by this (1&lt;&lt;32) issue
[3:11pm] mcb30: (I just replied to your e-mail)
[3:12pm] ogreinside joined the chat room.
[3:13pm] rwcr: Hmm. I didn't think about the overflow; that *should* make it work.
[3:13pm] mcb30: It doesn't
[3:13pm] rwcr: Aha.
[3:13pm] mcb30: I just tested compiling the damn code
[3:13pm] mcb30: I understand why the x86 code fails, but
[3:13pm] rwcr: The x86 …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wirelessboot/implementation?rev=1250187770&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-13T11:22:50-07:00</dc:date>
        <title>wirelessboot:implementation</title>
        <link>http://etherboot.org/wiki/wirelessboot/implementation?rev=1250187770&amp;do=diff</link>
        <description>Some wireless implementation details

Network association

Before an 802.11 device can be used, it must become associated with a
network by exchanging a series of management frames with the Access
Point. In some cases there is additional security handshaking required
after association. gPXE's 802.11 layer handles this transparently by
always having the association task running if association has not yet
succeeded, and using the link-up bit in the wrapping</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/fedora_iscsi_install?rev=1262987191&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-08T13:46:31-07:00</dc:date>
        <title>sanboot:fedora_iscsi_install</title>
        <link>http://etherboot.org/wiki/sanboot/fedora_iscsi_install?rev=1262987191&amp;do=diff</link>
        <description>Installing Fedora to an iSCSI target

Fedora 12 and newer

Fedora 12 has a graphical installer which can attach to an iSCSI target and use it directly.  On the storage configuration screen, choose the 'Advanced configuration' option, choose to use an iSCSI target, and fill out the details requested.  The installer will then use that LUN as you see fit.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-22T10:28:51-07:00</dc:date>
        <title>appnoted</title>
        <link>http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff</link>
        <description>How to network boot operating systems with gPXE

Introduction

gPXE is a new version of the well know Etherboot project.

The project created network booting code that allows computers to load their operating system from a network.

The code can be stored in a number of places, including BIOS Flash, EPROMs, floppy, CD, HD, or other bootable media.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week7?rev=1247422887&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-12T11:21:27-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week7</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week7?rev=1247422887&amp;do=diff</link>
        <description>July 4: Meeting with Marty: There are obviously some shortcommings in my driver design; As my driver progress has been good up to this point, I'm going to take a step back for a while and do some personal education on other drivers and driver structure;</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/bootingmemdisk?rev=1151246104&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T07:35:04-07:00</dc:date>
        <title>bootingmemdisk</title>
        <link>http://etherboot.org/wiki/bootingmemdisk?rev=1151246104&amp;do=diff</link>
        <description>Etherbooting memdisk

Disclaimer / Warning

This wiki page documents the author's recent experience in making an etherbootable image (nbi) of memdisk. At its best, it is only a temporary reference for those who want to boot memdisk from etherboot directly. It is temporary because the etherboot project team are reviewing some of the features in the current release 1.4.3 of mknbi. Depending on the results of their review, some bugs might have been fixed and new features might have been added to th…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dev/gdbstub?rev=1269836865&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-03-28T21:27:45-07:00</dc:date>
        <title>dev:gdbstub</title>
        <link>http://etherboot.org/wiki/dev/gdbstub?rev=1269836865&amp;do=diff</link>
        <description>GDB remote debugging

Overview

You can use the GNU Project Debugger (GDB) to debug gPXE.  You either need two computers or virtualization software (e.g. QEMU).  One host runs gPXE while the other runs GDB.

gPXE supports debugging via serial port or over the network.  For serial, you need a null modem serial cable.  For network, you need the machine to be connected to a network with UDP port 43770 traffic allowed.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T07:33:54-07:00</dc:date>
        <title>disklessdos</title>
        <link>http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff</link>
        <description>Using MEMDISK to etherboot a diskless DOS

Please, read also the general memdisk introduction.

This page is about using memdisk to run DOS, plus a virtual harddrive in RAM.

Diskless DOS (big ram disk)

Cloning a harddisk, in its simplest form, is just like cloning a floppy. Assumptions:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/ubuntu_aoe?rev=1284725017&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-17T05:03:37-07:00</dc:date>
        <title>sanboot:ubuntu_aoe</title>
        <link>http://etherboot.org/wiki/sanboot/ubuntu_aoe?rev=1284725017&amp;do=diff</link>
        <description>Setting up an Ubuntu Installation to work with AOE

(Tested on Ubuntu Lucid 10.04 and Ubuntu Maverick 10.10)

First make sure you have a server with some aoe server software installed.  If you use Linux as a server, get and install the “vblade” package.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/srp/sbft?rev=1249929545&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-10T11:39:05-07:00</dc:date>
        <title>srp:sbft</title>
        <link>http://etherboot.org/wiki/srp/sbft?rev=1249929545&amp;do=diff</link>
        <description>SRP boot firmware table

Introduction

The SRP Boot Firmware Table (sBFT) is a block of information containing various parameters useful to the SRP boot process.  It is the mechanism whereby the boot firmware conveys information about the boot device to the loaded operating system.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/pravin/journal/bkodebianiscsi?rev=1253932645&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-25T19:37:25-07:00</dc:date>
        <title>soc:2009:pravin:journal:bkodebianiscsi</title>
        <link>http://etherboot.org/wiki/soc/2009/pravin/journal/bkodebianiscsi?rev=1253932645&amp;do=diff</link>
        <description>Booting debian over iscsi

Here I will be documenting my first attempt to boot linux over iscsi.

Reason to choose debian

	*  Chose debian because the squashfs of debian works fine and there are no other problems.
	*  Also, all the kernel modules needed for iscsi initiator are inside initramfs so, less work for me.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/notes/protocol?rev=1243469113&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-27T17:05:13-07:00</dc:date>
        <title>soc:2009:oremanj:notes:protocol</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/notes/protocol?rev=1243469113&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

802.11 protocol notes

Functional overview

An 802.11 wireless network is composed of a set of nodes (called STAs
in the standard) communicating over radio frequencies in the 2.4GHz
(b/g/n) or 5GHz (a/n) unlicensed band.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/balajirrao/start?rev=1213620343&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-16T05:45:43-07:00</dc:date>
        <title>soc:2008:balajirrao:start</title>
        <link>http://etherboot.org/wiki/soc/2008/balajirrao/start?rev=1213620343&amp;do=diff</link>
        <description>Balaji Rao: USB Support
 Quick info  Timezone  UTC + 5.5  Work hours  04:30 - 18:30 UTC  Weekly meeting  Fri 12:00 UTC 
Project pages

	*  Journal
	*  Git Repository
	*  Project Plan
	*  Notes</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-21T17:13:20-07:00</dc:date>
        <title>socint</title>
        <link>http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff</link>
        <description>Google Summer of Code 2008

Preparation

Coding will formally start on Monday 26th May (though you're welcome to start earlier, if you're ready).  You'll need to make sure that your build and test environment is up and running before this date.  Here's a rough checklist:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-27T20:09:14-07:00</dc:date>
        <title>appnotes:make_usb_drive</title>
        <link>http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff</link>
        <description>Making a bootable USB flash drive

How to upgrade your motherboard BIOS firmware from a USB thumb drive
How to make a USB memory key in to a bootable DOS drive
By: Jeff Campbell, Turks &amp; Caicos Islands, British West Indies
June 25, 2007

It happens all the time, you have a newish machine that lacks a floppy drive, and you have a need to either upgrade the BIOS from DOS or run some other esoteric application that can only be done from DOS – the problem is, with no floppy drive (and god only knows…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/info?rev=1211468627&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-22T08:03:47-07:00</dc:date>
        <title>soc:2008:info</title>
        <link>http://etherboot.org/wiki/soc/2008/info?rev=1211468627&amp;do=diff</link>
        <description>Google Summer of Code 2008

Using git during GSoC

Information on how to use git during GSoC 2008 can be found here.

Preparation

Coding will formally start on Monday 26th May (though you're welcome to start earlier, if you're ready).  You'll need to make sure that your build and test environment is up and running</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/dverkamp/start?rev=1213620302&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-16T05:45:02-07:00</dc:date>
        <title>soc:2008:dverkamp:start</title>
        <link>http://etherboot.org/wiki/soc/2008/dverkamp/start?rev=1213620302&amp;do=diff</link>
        <description>Daniel Verkamp: COMBOOT Support
 Quick info  Timezone  UTC - 4  Work hours  13:00 - ~21:00 UTC  Weekly meeting  Fri 13:00 UTC 
Project pages

	*  Journal
	*  Git Repository
	*  Project Plan
	*  Notes</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/start?rev=1213620225&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-16T05:43:45-07:00</dc:date>
        <title>soc:2008:mdeck:start</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/start?rev=1213620225&amp;do=diff</link>
        <description>Michael Decker: Driver Development
 Quick info  Timezone  UTC - 4  Work hours  13:00 - 22:00 UTC (Wednesday to Sunday)  Weekly meeting  Fri 13:30 UTC 
Project pages

	*  Journal
	*  Git Repository
	*  Project Plan
	*  Notes</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week3?rev=1276466097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-13T14:54:57-07:00</dc:date>
        <title>soc:2010:andreif:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week3?rev=1276466097&amp;do=diff</link>
        <description>Week 3 [ Mon 7 Jun 2010 - Sun 13 Jun 2010 ]

Day 1 [ Mon 7 Jun 2010 ]

Git commit: 52f6bbd8471893361f264d3749b3f8c78df224b2

I managed to get the .irq routine implemented. I'm not sure how to test this, so I'll ask on email. I hope to get another round of feedback from people after which I'll send a patch containing the driver.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week2?rev=1276465962&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-13T14:52:42-07:00</dc:date>
        <title>soc:2010:andreif:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week2?rev=1276465962&amp;do=diff</link>
        <description>Week 2 [ Mon 31 May - Sun 6 Jun 2010 ]

Day 1 [ Mon 31 May 2010 ]

Git commit: 318ca039b7381e67e04f92447d9b2a211fe9541a

Today was about reorganizing parts of what I've written so far and taking some time to analyze things and try to see the big picture. Also, I did some debugging in the Linux driver (insert printks, make modules, make modules_install, modprobe -r pcnet32, modprobe pcnet32) and found out that even that one takes an unneeded branch at one point and tries to modify some registers …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-10T01:24:51-07:00</dc:date>
        <title>soc:2006:alanshieh:start</title>
        <link>http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff</link>
        <description>Alan Shieh, Linux UNDI Driver

Comparing a UNDI driver to server-side initrd selection

It is possible to achieve the same effect as an UNDI driver with other approaches, such as loading all possible drivers into an initrd, or selecting an initrd based on MAC address, thus allowing Linux to load the right module. Such a design of this is much more conservative, as it relies on driver code that has been used by a larger population</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week5?rev=1257670478&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-08T00:54:38-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week5</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week5?rev=1257670478&amp;do=diff</link>
        <description>June 22: One of the things I had neglected to do was automating testing. So, I decided to do that:

	*  In src/config/defaults/pcbios.h: changed #define CONSOLE_PCBIOS to #define CONSOLE_SERIAL
	*  make
	*  qemu -tftp . -cdrom bin/gpxe.iso -bootp /tests/arith_test.gpxe -serial stdio &gt; result</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-29T02:55:58-07:00</dc:date>
        <title>appnotes:compaq-armada-flashing</title>
        <link>http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff</link>
        <description>Flashing gPXE ROM to a Compaq Armada Notebook

The Compaq Armada M700 (and also M300, V300, E500, E500S and Prosignia 170 and 190) has an build in PXE (Preboot eXecution Environment) Boot ROM for the internal Intel EtherExpress Pro 100 NIC (Network Interface Controller). This ROM is ok, if you only want to network boot from (the very stupid) TFTP Daemon. But what to do, if you want to netboot from i.e. HTTP or iSCSI? Yes right, you need gPXE.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/alanshieh?rev=1155328305&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-11T13:31:45-07:00</dc:date>
        <title>soc:alanshieh</title>
        <link>http://etherboot.org/wiki/soc/alanshieh?rev=1155328305&amp;do=diff</link>
        <description>Alan Shieh, Linux UNDI Driver

Comparing a UNDI driver to server-side initrd selection

It is possible to achieve the same effect as an UNDI driver with other approaches, such as loading all possible drivers into an initrd, or selecting an initrd based on MAC address, thus allowing Linux to load the right module. Such a design of this is much more conservative, as it relies on driver code that has been used by a larger population</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-13T06:10:09-07:00</dc:date>
        <title>vmwarebios</title>
        <link>http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff</link>
        <description>Using Etherboot inside the VMware BIOS

The following mail has been posted on June 26, 2006 by Borg Number One in the EtherBoot mailing list.

EtherBoot ROM in VMware and Bochs - The tutorial

(updated on 07.07.2006)

Declarations

	*  Expansion ROM / ExpansionROM , Extension ROM / ExtensionROM , Option ROM / OptionROM , Extension BIOS / ExtensionBIOS</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/ubuntu_iscsi2?rev=1295439988&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-19T04:26:28-07:00</dc:date>
        <title>sanboot:ubuntu_iscsi2</title>
        <link>http://etherboot.org/wiki/sanboot/ubuntu_iscsi2?rev=1295439988&amp;do=diff</link>
        <description>Getting iSCSI booting to work with Ubuntu including logon and ibft support!

Tested on the following releases:

	*  Lucid Lynx 10.04
	*  Maverick Meerkat 10.10

For this example, I will use these values:

	*  iSCSI Qualified Name: iqn.2010-09.org.test:diskimg</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wiki/user/less1?rev=1245022900&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-14T16:41:40-07:00</dc:date>
        <title>wiki:user:less1</title>
        <link>http://etherboot.org/wiki/wiki/user/less1?rev=1245022900&amp;do=diff</link>
        <description>Hello World

For information about me and my Google Summer of Code 2009 project please visit my GSoC notes pages and journal pages.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-22T15:26:22-07:00</dc:date>
        <title>appnotes:port_winnt_sanboot</title>
        <link>http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff</link>
        <description>Porting Windows XP, Windows 7 and Windows 2008 to New Target Hardware via SAN-Booting

Introduction

Experience the power of Free and Open-Source Software such as gPXE and the communities that develop and support such.  If you can appreciate what this article accomplishes, perhaps you'd be inclined to get in the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/transfer?rev=1256859555&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-29T16:39:15-07:00</dc:date>
        <title>sanboot:transfer</title>
        <link>http://etherboot.org/wiki/sanboot/transfer?rev=1256859555&amp;do=diff</link>
        <description>Transferring the disk image to a SAN target

	*  Shut down the operating system that you want to transfer to the SAN target.

	*  Unplug the disk containing the operating system image, and attach it to the SAN target machine.

	*  Take a look at the disk's partition table; on Linux this can be achieved by running</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week4?rev=1245648994&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-21T22:36:34-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week4</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week4?rev=1245648994&amp;do=diff</link>
        <description>June 15: 
- Completed: skge_devinit()

- Meeting with Marty: I spoke on the phone with Marty today for about 90 minutes. We discussed my progress and he reviewed my code up until now. Overall, it was a very constructive meeting.

- Key recomendations of that conversation were:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T07:41:33-07:00</dc:date>
        <title>disklesswin98</title>
        <link>http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff</link>
        <description>Diskless win98

Please, also read the page about generally using memdisk.

Here, we are talking about converting an existing win98 workstation on harddisk into its RAM disk equivalent. We assume the readers had gone through the exercises elaborated in Quick Start and Diskless DOS (big ram disk)</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/centos?rev=1203549701&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-20T15:21:41-07:00</dc:date>
        <title>sanboot:centos</title>
        <link>http://etherboot.org/wiki/sanboot/centos?rev=1203549701&amp;do=diff</link>
        <description>CentOS boot from SAN

[Start of CentOS installation]

CentOS supports booting from an iSCSI SAN.  You can install directly to the iSCSI target.  Before starting installation, you will need to

	*  Create an iSCSI target</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week12?rev=1250325409&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-15T01:36:49-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week12</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week12?rev=1250325409&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 12

I can hardly believe there's only a week left of SoC. It's been a wonderful experience working with such talented developers, and I hope my coursework in the fall will leave me enough time to continue contributing</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T15:51:25-07:00</dc:date>
        <title>appnotes:config</title>
        <link>http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff</link>
        <description>#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27.7
# Wed Apr 22 09:40:09 2009
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG=&quot;arch/x86/configs/i386_defconfig&quot;
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_H…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/notes/design?rev=1245707645&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-22T14:54:05-07:00</dc:date>
        <title>soc:2009:oremanj:notes:design</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/notes/design?rev=1245707645&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

gPXE 802.11 API design notes

The below are my thoughts about a week into the coding season. They may change without warning. This is not meant to be a complete API guide; there are comments in the header files for that.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/esxi4.1?rev=1279098899&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-14T02:14:59-07:00</dc:date>
        <title>sanboot:esxi4.1</title>
        <link>http://etherboot.org/wiki/sanboot/esxi4.1?rev=1279098899&amp;do=diff</link>
        <description>Overview

This tutorial assumes you know how to set up an iscsi targets on your SAN and, you already have gPXE up and running. With version 4.1 of ESXi (installable) boot from SAN is possible via software initiator.  This new feature works with gPXE!  Here's a quick tutorial on the easiest way to get you up and running in less than 10 minutes.  For ease of use I'll be doing this within my current ESXi host (physical box) and doing a virtual install of ESXi host #2 (the same steps as you would ph…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-20T07:59:53-07:00</dc:date>
        <title>mknbi</title>
        <link>http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff</link>
        <description>The mknbi utilities

Name

mknbi - make network bootable image

Synopsis


mknbi --version
mknbi --format=format --target=target [--output=outputfile] target-specific-arguments
mkelf-linux [--output=outputfile] kernelimage [ramdisk]
mknbi-linux [--output=outputfile] kernelimage [ramdisk]
mknbi-rom [--output=outputfile] ROM-image
mkelf-menu [--output=outputfile] [dataimage]
mknbi-menu [--output=outputfile] [dataimage]
mkelf-nfl [--output=outputfile] [dataimage]
mknbi-nfl [--output=outputfile] [da…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/iscsi_install?rev=1279061952&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-13T15:59:12-07:00</dc:date>
        <title>sanboot:iscsi_install</title>
        <link>http://etherboot.org/wiki/sanboot/iscsi_install?rev=1279061952&amp;do=diff</link>
        <description>Installing to an iSCSI target

[Start of Fedora installation]

Installing directly to an iSCSI target requires support from the operating system's installation program, in addition to requiring iSCSI boot support.  Select the operating system that you wish to install to an iSCSI target:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/git-usage?rev=1213018019&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-09T06:26:59-07:00</dc:date>
        <title>soc:2008:git-usage</title>
        <link>http://etherboot.org/wiki/soc/2008/git-usage?rev=1213018019&amp;do=diff</link>
        <description>Using git for gPXE development during GSoC 2008

Overview

During GSoC, you will be working with three git repositories:

	*  The master project repository

	*  Your local working repository

	*  Your personal public repository

You will edit code in your local working repository.  Every so often (at least once a week, preferably more) you will push changes from your local working repository to your personal public repository.  This allows us to see your code.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/meteger/project_plan/start?rev=1306078529&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-05-22T08:35:29-07:00</dc:date>
        <title>soc:2011:meteger:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2011/meteger/project_plan/start?rev=1306078529&amp;do=diff</link>
        <description>Project Plan

Abstract

The goal of this Project is to develop a new gPXE driver for the Broadcom 57xx(tg3) series of network cards.
There currently already is a tg3 driver in gPXE but it is outdated and several years behind in development compared to the linux tg3 driver. This leads to many new tg3 cards not being supported in gPXE. The new driver is supposed to support all device variants the linux driver supports.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/git-usage?rev=1301171639&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-26T13:33:59-07:00</dc:date>
        <title>git-usage</title>
        <link>http://etherboot.org/wiki/git-usage?rev=1301171639&amp;do=diff</link>
        <description>Using git for gPXE development

Overview

During development, you will be working with three git repositories:

	*  The master project repository

	*  Your local working repository

	*  Your personal public repository

You will edit code in your local working repository.  As applicable, you should push changes from your local working repository to your personal public repository.  This allows us to see your code.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/fedora?rev=1194745234&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-10T17:40:34-07:00</dc:date>
        <title>sanboot:fedora</title>
        <link>http://etherboot.org/wiki/sanboot/fedora?rev=1194745234&amp;do=diff</link>
        <description>Fedora boot from SAN

[Start of Fedora installation]

Fedora supports booting from an iSCSI SAN.  You can install directly to the iSCSI target.  Before starting installation, you will need to

	*  Create an iSCSI target</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week2?rev=1307154612&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-03T19:30:12-07:00</dc:date>
        <title>soc:2011:pcmattman:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/journal/week2?rev=1307154612&amp;do=diff</link>
        <description>Week 2 (May 30 to June 5)

Day 1 (May 30)

Breakthrough! Found the point where attempting to open an IPv6 connection was failing (debug line in core/open.c) and added an AF_INET6 socket opener to TCP. I'll probably have to do the same for UDP soon.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/ideas?rev=1301171675&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-26T13:34:35-07:00</dc:date>
        <title>soc:ideas</title>
        <link>http://etherboot.org/wiki/soc/ideas?rev=1301171675&amp;do=diff</link>
        <description>Etherboot Project GSoC Ideas

This list is not exhaustive, and we welcome new suggestions.  Some of these ideas are not in themselves complete projects; feel free to ask us how much work is likely to be involved, and how many ideas you might sensibly attempt as a Summer of Code project.  The approximate difficulty level of each idea has been marked with one or more</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/hardwareissues?rev=1289686457&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-11-13T14:14:17-07:00</dc:date>
        <title>hardwareissues</title>
        <link>http://etherboot.org/wiki/hardwareissues?rev=1289686457&amp;do=diff</link>
        <description>Hardware Issues

This page contains some issues that people had while using gpxe.

3Com 3C905-TX Card

This card is known to not support gpxe while using the MBA v4.0.

Symptoms

gPXE loads, negociate the link speed but the DHCP doesn't grab any valid adress even if the DHCP server make an offer.
This is due to a buggy PXE rom, this usually happens on the MBA (Master Boot Agent) v4.0.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-11-07T03:18:20-07:00</dc:date>
        <title>appnotes:pxelinux_tftp_to_http_migration</title>
        <link>http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff</link>
        <description>PXELINUX TFTP to HTTP Migration

The Problem

Migrate from PXELINUX/TFTP deployment environment to gPXE/HTTP based environment with easy roll out and back out, and zero changes to PXELINUX menu/configuration files and production application code that drives deployment operations. Eventually replace</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/old_news?rev=1295848443&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-23T21:54:03-07:00</dc:date>
        <title>old_news</title>
        <link>http://etherboot.org/wiki/old_news?rev=1295848443&amp;do=diff</link>
        <description>Old News

[LinuxWorld logo]

LinuxWorld Expo 2008, San Francisco

The Etherboot project will be exhibiting once again at LinuxWorld Expo in San Francisco from August 5-7.  We will also be presenting a tutorial on the morning of Monday August 4th, on the topic of “Virtualization of the Boot Process Using Open Source Software</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/syslinux?rev=1287711153&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-21T18:32:33-07:00</dc:date>
        <title>syslinux</title>
        <link>http://etherboot.org/wiki/syslinux?rev=1287711153&amp;do=diff</link>
        <description>Booting gPXE from a memory stick partition with SYSLINUX

Much like the howto usbwithstorage, this will guide you through installing gPXE on your flash drive (or any other FAT/ext234/btrfs partition for that matter) without losing ability to store files on it. In fact, using EXTLINUX or SYSLINUX, it's possible to use this method to make almost any medium gPXE-bootable.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/romburning/tg3?rev=1204817294&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-03-06T07:28:14-07:00</dc:date>
        <title>romburning:tg3</title>
        <link>http://etherboot.org/wiki/romburning/tg3?rev=1204817294&amp;do=diff</link>
        <description>Burning gPXE into Broadcom BCM57xx-based cards

&lt;referback&gt;This page is part of the ROM-burning tutorial.&lt;/referback&gt;

The Broadcom Diagnostic Utility set allows you to update the expansion ROM images in Broadcom BCM57xx gigabit network cards (and rebranded Broadcom cards such as the HP NC7771).</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week6?rev=1309670055&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-02T22:14:15-07:00</dc:date>
        <title>soc:2011:pcmattman:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/journal/week6?rev=1309670055&amp;do=diff</link>
        <description>Week 6 (June 27 to July 3)

Day 1 (June 27)

Today was mostly spent finalising the last couple of changes after Guo-Fu's review. I also spent a while upgrading my router's distribution version; I'm hoping I'll be able to get some neat IPv6 features that weren't in the older packages I was using. I still need to work on getting the ISC DHCPv6 server installed and tested, but I'm also wrapping my head around the actual architecture of DHCPv4 in gPXE before I go too deep into implementing it on my …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-13T00:09:52-07:00</dc:date>
        <title>appnotes:gpxeonqemu091</title>
        <link>http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff</link>
        <description>How to use gPXE with RHEL 5.4 (qemu-kvm 0.9.1)

Introduction

QEMU/KVM in RedHat Enterprise Linux 5.4 uses a version based on qemu
0.9.1 with kvm-83.
The etherboot roms are included by default in that package.

In order to use the gPXE some patches may be applied to the qemu
source as well as to gPXE source.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-10T12:44:31-07:00</dc:date>
        <title>todo</title>
        <link>http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff</link>
        <description>You probably want todo/start</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/faq/start?rev=1266093248&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-13T12:34:08-07:00</dc:date>
        <title>faq:start</title>
        <link>http://etherboot.org/wiki/faq/start?rev=1266093248&amp;do=diff</link>
        <description>Frequently Asked Questions

Below are links to pages that provide help with questions that have been asked by users of gPXE and Etherboot

General

	*  What does the Etherboot Project do?

Creating images

	*  How can I make gPXE and Etherboot images without compiling them myself?

Drivers

	*  How do I check if a network card is supported?
	*  What if there is no driver for my network card?
	*  Can open source Linux or BSD drivers be used with gPXE?
	*  Where do I start with developing a new dr…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/alan_s_test_/development_infrastructure?rev=0&amp;do=diff">
        <dc:format>text/html</dc:format>
        <title>soc:alan_s_test_:development_infrastructure</title>
        <link>http://etherboot.org/wiki/soc/alan_s_test_/development_infrastructure?rev=0&amp;do=diff</link>
        <description></description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week3?rev=1213563625&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-15T14:00:25-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week3?rev=1213563625&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 3

----------

10 June

Continued respinning my code today.  Most of the functionality has been respun now, and soon a few purely formatting commits will take place (comments, tabs, naming, reordering, splitting to .h file)</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week1?rev=1243642455&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-29T17:14:15-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week1?rev=1243642455&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 1

Thursday and Friday, 28-29 May

I got off to a bit of a late start due to an academic obligation, but I had done some work in the community bonding period on making sense of the IEEE 802.11 specification. I figured it would be best to start by getting the various IEEE constants and structures into code, and then figure out how gPXE's 802.11 layer will look:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week9?rev=1248399250&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-23T18:34:10-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week9</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week9?rev=1248399250&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 9

Tuesday, 21 July

I'm back! Trip was a lot of fun, but I'm glad to be back working on gPXE.

I spent a bit of time today getting my code up to date with the changes that have been made on gPXE mainline while I was away. The effect of this is a new mainline-review branch with its three core pending wireless commits slightly modified, and a merge commit on the wireless branch.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week2?rev=1244410427&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-07T14:33:47-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week2?rev=1244410427&amp;do=diff</link>
        <description>June 1, vacation.

June 2, Meeting with Marty. After a very slow start, I feel confident in this meeting. Marty and I spoke for just under an hour about where I am, where I am headed, and how to get there. For the first time ever, I successfully compiled gPXE. A good start.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week1?rev=1213129744&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-10T13:29:04-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week1?rev=1213129744&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 1

----------

26 May 2008

	*  Converted #ifdef DEBUG printf(..) and hd(..) statements to DBG(..) and DBG_HD(..) in eepro100.c
	*  Collected &amp; sorted notes on Etherboot and gPXE driver API

27 May 2008

	*  Further gPXE network driver</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/notes/buildbot?rev=1243960224&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-02T09:30:24-07:00</dc:date>
        <title>soc:2009:dverkamp:notes:buildbot</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/notes/buildbot?rev=1243960224&amp;do=diff</link>
        <description>BuildBot setup notes

I am currently using a Debian stable (5.01) system, but this should work similarly on other distributions or with BuildBot installed from source.
$ sudo aptitude install buildbot
edit /etc/default/buildbot:
BB_NUMBER[0]=0                  # index for the other values; negative disables the bot
BB_NAME[0]=&quot;foo&quot;                # short name printed on startup / stop
BB_USER[0]=&quot;buildbot&quot;           # user to run as
BB_BASEDIR[0]=&quot;/var/lib/buildmaster&quot;            # basedir argum…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/elf-ebi-initramfs-lnxi-howto/the_kernel/config?rev=1240543027&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T20:17:07-07:00</dc:date>
        <title>elf-ebi-initramfs-lnxi-howto:the_kernel:config</title>
        <link>http://etherboot.org/wiki/elf-ebi-initramfs-lnxi-howto/the_kernel/config?rev=1240543027&amp;do=diff</link>
        <description>#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27.7
# Wed Apr 22 09:40:09 2009
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG=&quot;arch/x86/configs/i386_defconfig&quot;
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_H…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week8?rev=1279548888&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-19T07:14:48-07:00</dc:date>
        <title>soc:2010:andreif:journal:week8</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week8?rev=1279548888&amp;do=diff</link>
        <description>Week 8 [ Mon 12 Jul 2010 - Sun 18 Jul 2010 ]

Day 1 [ Mon 12 Jul 2010 ]

Git commit: a8e9adfd4a8e3775c227a5f8f8138ef9d2a9d922

I started out today by creating a new local branch and removing any non-critical code, constantly comparing what I had with the old driver. Eventually I reached a point where the new driver was very very similar to the old one, yet it still didn't work. I then remembered that Marty suggested that there might be alignment issues. And indeed there were. Using</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week3?rev=1245102634&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-15T14:50:34-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week3?rev=1245102634&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 3

Monday, 8 June

It's ALIIIIIVE!

After a long day of head-scratching and bug-squashing, I've gotten the wireless to work in my test system with no apparent problems. :-)

First, the commits:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/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/wiki/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>
    <item rdf:about="http://etherboot.org/wiki/wiki/welcome?rev=1488916923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-03-07T12:02:03-07:00</dc:date>
        <title>wiki:welcome</title>
        <link>http://etherboot.org/wiki/wiki/welcome?rev=1488916923&amp;do=diff</link>
        <description>Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,

-- the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn't exist, this link will be red:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/ideas?rev=1266081209&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-13T09:13:29-07:00</dc:date>
        <title>soc:2009:ideas</title>
        <link>http://etherboot.org/wiki/soc/2009/ideas?rev=1266081209&amp;do=diff</link>
        <description>This is an archived version of the Ideas page for 2009. You may want to look at our 2010 Ideas.

Etherboot Project GSoC Ideas

This list is not exhaustive, and we welcome new suggestions.  Some of these ideas are not in themselves complete projects; feel free to ask us how much work is likely to be involved, and how many ideas you might sensibly attempt as a Summer of Code project.  The approximate difficulty level of each idea has been marked with one or more</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/meteger/journal/week6?rev=1309692062&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-03T04:21:02-07:00</dc:date>
        <title>soc:2011:meteger:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2011/meteger/journal/week6?rev=1309692062&amp;do=diff</link>
        <description>Day 1 ( June 27 )

In yesterdays weekly meeting we decided to split the driver into several .c files. I started splitting the driver into tg3_hw.c which contains all the low-level NIC hardware access functions, and tg3_main.c which contains all the code that directly interacts with gPXE(e.g. tg3_open, tg3_transmit, etc).</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-26T11:03:15-07:00</dc:date>
        <title>msris</title>
        <link>http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff</link>
        <description>Using Etherboot with RIS

What is RIS?

RIS stands for Remote Installation Services, it is a Microsoft technology that is used to install Windows 2000 and above from a remote server to a PXE enabled client machine. It is different from drive imaging technologies such as Symantec Ghost because it actually boots an installer off a network server and then installs Windows from scratch.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week7?rev=1215977020&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-13T12:23:40-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week7</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week7?rev=1215977020&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 7

----------

9 July

A new branch, drivers6 was created.  This branch was merged with the mainline via git pull origin master.  This brought the GDB code into my tree.  Experimenting with GDB, a segfault was reported following the point where gPXE was freezing during the second NIC boot.  I ran a backtrace:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week8?rev=1216587081&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-20T13:51:21-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week8</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week8?rev=1216587081&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 8

----------

16 July

This morning I created a new Windows disk image to test AoE with.  The last image I made was on a different machine, so that wouldn't work.  The AoE driver seemed most sensitive to the change of hardware.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week6?rev=1215281128&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-05T11:05:28-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week6?rev=1215281128&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 6

----------

2 July

Today, I'll be doing some testing with the eepro100.  I've been using one PCI card for testing thus far, so I'll toss in another and run more tests.

Testing revealed a problem on the 82559.  A series of TX overflows occurred.  Testing with the original legacy driver did not show this behavior, so faulty hardware is not likely the root cause.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/debian_and_ubuntu?rev=1197468691&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-12T06:11:31-07:00</dc:date>
        <title>sanboot:debian_and_ubuntu</title>
        <link>http://etherboot.org/wiki/sanboot/debian_and_ubuntu?rev=1197468691&amp;do=diff</link>
        <description>Debian or Ubuntu

Preparing an existing installation for AoE

You can either work with an installation on

	*  a physical disk on a client machine or
	*  a chroot(8) environment operating on a loopback-mounted disk image

Install the aoetools package. For Ubuntu, you need to put the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/romburning/vbox?rev=1263117024&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-10T01:50:24-07:00</dc:date>
        <title>romburning:vbox</title>
        <link>http://etherboot.org/wiki/romburning/vbox?rev=1263117024&amp;do=diff</link>
        <description>VirtualBox LAN boot ROM

You can use gPXE as the LAN boot ROM in VirtualBox.  The boot ROM can be set per-VM or globally for all VMs.  Using gPXE instead of the default LAN boot ROM, VMs can be booted over HTTP, iSCSI, AoE, and gPXE's other advanced features are available.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-04T01:46:28-07:00</dc:date>
        <title>appnotes:gpxeonvmware</title>
        <link>http://etherboot.org/wiki/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff</link>
        <description>Adding a gPXE ROM image directly into a VMware virtual machine

	*  This guide covers VMWare virtual machines and should be nearly identical for all VMware hypervisor prodcuts.  VMWare Workstation is covered specifically by this guide, but you can adapt it easily for VMWare Server or ESX.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-29T12:30:55-07:00</dc:date>
        <title>wirelessboot</title>
        <link>http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff</link>
        <description>Wireless booting

Thanks to some work done during Summer of Code 2009, gPXE supports the 802.11 protocol for accessing Wi-Fi wireless networks.

Note: the contents of this page rely on some features that are not yet present in mainline gPXE, but hopefully they should be there soon.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-11T06:47:03-07:00</dc:date>
        <title>iscsiboot</title>
        <link>http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff</link>
        <description>Booting via iSCSI

This tutorial describes a simple three-step process for getting your first iSCSI-booting operating system up and running.  The three stages are:

	*  
	*  
	*  

[Fedora Core 5 booting via iSCSI]

Preparing the operating system image

The first stage is to prepare the operating system image for iSCSI boot.  This generally involves installing an iSCSI initiator and adjusting a few configuration parameters.  Instructions are available for:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week9?rev=1216956856&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-24T20:34:16-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week9</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week9?rev=1216956856&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 9

----------

23 &amp; 24 July

Marty reported the eepro100 stopped receiving packets after a delay on occasion.  He was testing with an 82557, which I unfortunately don't have available to test with.  I did manage to reproduce the behavior with an 82558.  It is a very intermittent bug.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/weekc?rev=1219109616&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-18T18:33:36-07:00</dc:date>
        <title>soc:2008:mdeck:journal:weekc</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/weekc?rev=1219109616&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week C

----------

13 August

This morning I installed an iSCSI server on my laptop.  It turned out much simpler than anticipated.  I am running Ubuntu 8.04 (Hardy Heron), and it turns out the iSCSI target kernel module is present by default?  So, a point &amp; click install via Synaptic Package Manager, and modification of</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/stefanha/journal/week3?rev=1213614684&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-16T04:11:24-07:00</dc:date>
        <title>soc:2008:stefanha:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2008/stefanha/journal/week3?rev=1213614684&amp;do=diff</link>
        <description>Stefan Hajnoczi: GDB Remote Debugging

Week 3

Milestones:

	*  GDB remote debugging over UDP.
	*  Hardware watchpoint support for trapping read/write/execute on memory.

Mon Jun 9

I had a refreshing weekend with only a little bit of Etherboot hacking on Saturday.  The weather was excellent and I was able to recharge batteries a bit</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/stefanha/journal/week6?rev=1215525430&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-08T06:57:10-07:00</dc:date>
        <title>soc:2008:stefanha:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2008/stefanha/journal/week6?rev=1215525430&amp;do=diff</link>
        <description>Stefan Hajnoczi: GDB Remote Debugging

Week 6

Milestones:

	*  [b44] Tested and clean for mainline review.
	*  [r-o-m] Fix known ROM-o-matic bugs.

Mon Jun 30

Git commits:

	*  [DMA] Add test for bounce buffers.
	*  [b44] Begin driver clean up work
	*  [b44] Auto-negotiate link

Posted DMA mapping patches to the mailing list.  I am hoping to get feedback on whether this approach looks good.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/pravin/journal/pxeknifedsl?rev=1244930730&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-13T15:05:30-07:00</dc:date>
        <title>soc:2009:pravin:journal:pxeknifedsl</title>
        <link>http://etherboot.org/wiki/soc/2009/pravin/journal/pxeknifedsl?rev=1244930730&amp;do=diff</link>
        <description>Adding DSL to pxeKnife

Initially, I will add just menu entry, kernel and initramfs. I plan to modify initramfs later to support http mounting.

HTTP mounting

This will involve following things.

	*  Add FUSE module to initramfs.
	*  Add httpfs to initramfs.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-18T12:03:21-07:00</dc:date>
        <title>iscsibootprepfc5</title>
        <link>http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff</link>
        <description>Preparing Fedora Core 5 for iSCSI boot

These instructions assume that you have an installation of Fedora Core 5 on a local hard disk.  We will make this installation iSCSI-boot-capable, then copy it to a remote iSCSI target and boot from it.

Start by installing the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-07T14:44:37-07:00</dc:date>
        <title>amibios</title>
        <link>http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff</link>
        <description>Adding gPXE to an AMI BIOS

In systems with a motherboard-integrated NIC, the NIC's ROM generally does not exist as a separate entity. Instead, it is read as a sort of “option ROM module” out of the overall BIOS flash. This page contains instructions for replacing the vendor PXE image with gPXE in the flash image of an AMIBIOS-based machine.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2006/nikhilcrao/proposal?rev=1210408438&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-10T01:33:58-07:00</dc:date>
        <title>soc:2006:nikhilcrao:proposal</title>
        <link>http://etherboot.org/wiki/soc/2006/nikhilcrao/proposal?rev=1210408438&amp;do=diff</link>
        <description>Summer of Code - Implementing support for IPv6

Project Title: Implementing support for IPv6

Summary: Redesign the TCP/IP stack implementation in gPXE to provide support for IPv6

Mentoring Organization: Etherboot


Synopsis

gPXE uses uIP to implement its TCP/IP stack. uIP is an implementation of the TCP/IP stack which uses a fraction of the resources used by a full fledged TCP/IP implementation.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/win2000?rev=1195673213&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-21T11:26:53-07:00</dc:date>
        <title>sanboot:win2000</title>
        <link>http://etherboot.org/wiki/sanboot/win2000?rev=1195673213&amp;do=diff</link>
        <description>Windows 2000 boot from SAN

Windows 2000 supports booting from an AoE SAN.  You cannot install directly to the SAN target; you must first install Windows 2000 to a physical disk.

Installation

Start by installing Windows 2000 to a physical disk.  It is best to use an external USB, FireWire, or eSATA disk; this will make later stages easier.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/winxp?rev=1235597722&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-25T13:35:22-07:00</dc:date>
        <title>sanboot:winxp</title>
        <link>http://etherboot.org/wiki/sanboot/winxp?rev=1235597722&amp;do=diff</link>
        <description>Windows XP boot from SAN

Windows XP supports booting from either an iSCSI or AoE SAN. You cannot install directly to the SAN target; you must first install Windows XP to a physical disk.

Installation

Start by installing Windows XP to a physical disk.  It is best to use an external USB, FireWire, or eSATA disk; this will make later stages easier.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/peper/journal/week1?rev=1275781254&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-05T16:40:54-07:00</dc:date>
        <title>soc:2010:peper:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2010/peper/journal/week1?rev=1275781254&amp;do=diff</link>
        <description>Piotr Jaroszyński: Usermode debugging under Linux

Week 1  [ 24 May - 30 May 2010 ]

Monday, 24 May 2010

	*  Refreshed my gPXE memory a little
	*  Had a meeting with Josh:
		*  Went over my previous work
		*  Decided upon the tasks for the nearest and more distant future</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/pravin/notes/start?rev=1261923489&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-27T06:18:09-07:00</dc:date>
        <title>soc:2009:pravin:notes:start</title>
        <link>http://etherboot.org/wiki/soc/2009/pravin/notes/start?rev=1261923489&amp;do=diff</link>
        <description>place to log useful random commands

Useful to find the dependency of given executable on other shared libraries.


ldd


Useful information

AndyTim: By the way, if you ever get the ^M problem again.
 Try following it by a ^J

Links to watch-out

	*</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-10T00:49:58-07:00</dc:date>
        <title>debug</title>
        <link>http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff</link>
        <description>gPXE debugging

Sat Jun 10 07:40:52 UTC 2006

I've started to work on getting more drivers working in gPXE 0.5, and have come across an interesting problem.

I am not sure what is causing the problem, so I need to debug it.  It occurred to me that this is a perfect opportunity to show how the process works, and get more people involved.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/start?rev=1301164255&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-26T11:30:55-07:00</dc:date>
        <title>start</title>
        <link>http://etherboot.org/wiki/start?rev=1301164255&amp;do=diff</link>
        <description>Etherboot/gPXE Wiki

[A network card]

gPXE is an open source (GPL) network bootloader.  It provides a direct replacement for proprietary PXE ROMs, with many extra features such as DNS, HTTP, iSCSI, etc.  Take a look at our Screenshots page and the HowTo Guides for some ideas of what we can do, and grab the code from our</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-11T12:53:11-07:00</dc:date>
        <title>appnotes:sanboot-zfs</title>
        <link>http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff</link>
        <description>The volume management functions of ZFS, combined with the COMSTAR (STMF) system in Opensolaris create a very powerful storage platform for boot-from-SAN functionality.  This document endeavors to describe that configuration.

Components

The following are the major components of this system:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/pxechaining?rev=1279138185&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-14T13:09:45-07:00</dc:date>
        <title>pxechaining</title>
        <link>http://etherboot.org/wiki/pxechaining?rev=1279138185&amp;do=diff</link>
        <description>PXE chainloading

If you have a large number of machines which already have a legacy PXE implementation (e.g. network cards containing an Intel PXE ROM), then you may want to avoid having to reflash each machine's network card.  You can achieve this by placing gPXE on your TFTP server.  The PXE-capable machines will download gPXE via TFTP, and instantly become gPXE-capable machines.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-15T19:55:44-07:00</dc:date>
        <title>qemu</title>
        <link>http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff</link>
        <description>How to use gPXE with QEMU

Step by step

	*  Install Qemu
	*  Compile or download gpxe.pdsk.
	*  Type on the command line: 
 qemu -fda gpxe.pdsk -net nic -net user -bootp http://etherboot.org/gtest/gtest.gpxe 


Quick start

First make sure you have</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-05T07:34:57-07:00</dc:date>
        <title>winpe</title>
        <link>http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff</link>
        <description>Booting Windows PE

[Windows AIK installation screen]

Overview

Windows Preinstallation Environment (WinPE) is a network-bootable version of Windows designed for installation, troubleshooting or system recovery.  It is not a general-purpose Windows system; it can be used only for these specific tasks.  If you want to boot a fully functional version of Windows, you need to</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/nikhil/proposal?rev=1150397504&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-15T11:51:44-07:00</dc:date>
        <title>soc:nikhil:proposal</title>
        <link>http://etherboot.org/wiki/soc/nikhil/proposal?rev=1150397504&amp;do=diff</link>
        <description>Summer of Code - Implementing support for IPv6

Project Title: Implementing support for IPv6

Summary: Redesign the TCP/IP stack implementation in gPXE to provide support for IPv6

Mentoring Organization: Etherboot


Synopsis

gPXE uses uIP to implement its TCP/IP stack. uIP is an implementation of the TCP/IP stack which uses a fraction of the resources used by a full fledged TCP/IP implementation.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T06:46:24-07:00</dc:date>
        <title>safebootmode</title>
        <link>http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff</link>
        <description>SafeBootMode

Trust and Security in network booting

On regular PC systems, the aspect of which operating system is booted, where the kernel will be loaded from etc. can be controlled (more or less) reliably. For example, with a proper setup GRUB bootloader, in combination with an operating system like GNU/Linux, users will not be able to change the boot options without opening the PC case and (for example) resetting the BIOS or attach additional drivers - which is rather unlikely in most office…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/centos_iscsi_install?rev=1203552517&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-20T16:08:37-07:00</dc:date>
        <title>sanboot:centos_iscsi_install</title>
        <link>http://etherboot.org/wiki/sanboot/centos_iscsi_install?rev=1203552517&amp;do=diff</link>
        <description>Installing CentOS to an iSCSI target

The CentOS installation process is somewhat fragile, and the built-in support for iSCSI installation does not function properly (except in very limited circumstances).  However, it is possible to work around this limitation and install to an iSCSI target.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/dverkamp/journal/week8?rev=1216395697&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-18T08:41:37-07:00</dc:date>
        <title>soc:2008:dverkamp:journal:week8</title>
        <link>http://etherboot.org/wiki/soc/2008/dverkamp/journal/week8?rev=1216395697&amp;do=diff</link>
        <description>Daniel Verkamp: COMBOOT Support

Journal

Week 8

----------

15-17 July 2008

	*  After a conversation with mcb30 last Thursday on how to fix the problems with COM32 stack overwrites during image loading, I've implemented his suggestions.  This resulted in a 3-day debugging marathon until I switched to a simpler test case and just single stepped through the entire image execution process</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/winvista?rev=1243982488&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-02T15:41:28-07:00</dc:date>
        <title>sanboot:winvista</title>
        <link>http://etherboot.org/wiki/sanboot/winvista?rev=1243982488&amp;do=diff</link>
        <description>For Vista, you can either:

	*  adapt the Windows XP AoE guide. Most of it is the same.
	*  adapt the Windows 2008 iSCSI guide. Vista has built-in support for booting over iSCSI.

IMPORTANT NOTE for installing vista over iSCSI:

The installation process is the same as windows 2008. But</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/faq/drivers?rev=1266092397&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-13T12:19:57-07:00</dc:date>
        <title>faq:drivers</title>
        <link>http://etherboot.org/wiki/faq/drivers?rev=1266092397&amp;do=diff</link>
        <description>Driver FAQ

How do I check if a network card is supported?

When a PCI network card is detected, its PCI ID is used to identify it and choose an appropriate driver.  Each network card driver has a list of PCI IDs it supports.

The format of a PCI ID is</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week5?rev=1215017420&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-02T09:50:20-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week5</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week5?rev=1215017420&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 5

----------

23 &amp; 24 June

OK, so I rewrote the tx path again, using the suspend bit as necessary. To give you an idea of what I'm working with, here is a short overview.

The 8255x processes command blocks to perform actions, such as configuration and transmit.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/stefanha/journal/week11?rev=1218382284&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-10T08:31:24-07:00</dc:date>
        <title>soc:2008:stefanha:journal:week11</title>
        <link>http://etherboot.org/wiki/soc/2008/stefanha/journal/week11?rev=1218382284&amp;do=diff</link>
        <description>Stefan Hajnoczi: GDB Remote Debugging

Week 11

Milestones:

	*  [b44] Tested and clean for mainline review.

Fri 8 Aug

Ouch, lowest productivity this week.  I am visiting my family and have spent time with friends, swimming, studying for the theory driving test, and organizing for the end of student life and the start of work in October</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/stefanha/journal/week1?rev=1212572815&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-04T02:46:55-07:00</dc:date>
        <title>soc:2008:stefanha:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2008/stefanha/journal/week1?rev=1212572815&amp;do=diff</link>
        <description>Stefan Hajnoczi: GDB Remote Debugging

Journal Week 1

Milestone: Set up IDT and write an interrupt handler.

Fri May 23

Some notes after chatting with mdc and mcb30:

	*  Place IDT code in arch/i386/transitions/librm.S - in similar places to lgdt and</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/balajirrao/notes/uhci_design?rev=1214476004&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-26T03:26:44-07:00</dc:date>
        <title>soc:2008:balajirrao:notes:uhci_design</title>
        <link>http://etherboot.org/wiki/soc/2008/balajirrao/notes/uhci_design?rev=1214476004&amp;do=diff</link>
        <description>UHCI Driver Desgin



An example schedule is shown above. It consists of a frame list made up of 1024 frames. In each frame, the UHCI controller inserts number of TDs that can fit into a it. The gPXE since we don't support isochronous TDs, the UHCI starts scanning at the first Queue Head (QH). It executes the first TD queued below, sets its status, updates the QH to point to the executed TD's next TD, and goes to the next QH. Thus, UHCI executes one TD belonging to a particular QH at a time. Thi…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/balajirrao/journal/week3?rev=1214622088&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-27T20:01:28-07:00</dc:date>
        <title>soc:2008:balajirrao:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2008/balajirrao/journal/week3?rev=1214622088&amp;do=diff</link>
        <description>Balaji Rao: USB Support Project

Journal

Week 3

Saturday, June 14th

Whole day spent on identifying the reason for tx failure. Looked like a very scary bug. Spend more than 10 hours debugging it. Finally I tracked it down to the improper setting of the Data Toggle synchronization bits. Next comes the rx part which is the most interesting. I'll hopefully clean up the source and commit it tomorrow.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/win2k8_iscsi_install?rev=1295727363&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-22T12:16:03-07:00</dc:date>
        <title>sanboot:win2k8_iscsi_install</title>
        <link>http://etherboot.org/wiki/sanboot/win2k8_iscsi_install?rev=1295727363&amp;do=diff</link>
        <description>Installing Windows Server 2008 to an iSCSI target

To install Windows Server 2008 to an iSCSI target, you must first configure your system to attempt to boot via iSCSI, and fall back to booting from DVD-ROM if the iSCSI boot fails.  The exact procedure for doing this will vary depending on your computer's BIOS.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-08T05:11:20-07:00</dc:date>
        <title>troubleshooting</title>
        <link>http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff</link>
        <description>Troubleshooting FAQ

&quot;No IP address&quot;

Problem:
You have setup a DHCP server, boot EtherBoot, but it will fail to accept an IP address from the server.

Solution:
As of version 3.0.3 of the ISC DHCP server, the value of “next-server” does not have a reasonable default any more (it used to contain the IP address of the DHCP server, which would act as TFTP server then). You will have to set it to the IP address of the TFTP server (in most cases, the same machine as the DHCP server):</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week2?rev=1213130066&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-10T13:34:26-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week2?rev=1213130066&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 2

----------

4 June

	*  More coding.  
	*  Renamed some functions for more consistency.  
	*  Migrated global state into net_device private data structure.  
	*  Separated some EEPROM code into a separate routine.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-08T01:47:44-07:00</dc:date>
        <title>appnotes:bootbymacaddress</title>
        <link>http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff</link>
        <description>Network booting by Mac Address

Author: Edward King




The environment

A collection of headless, diskless servers, utilising a range of operating system images.

A web-based control system enables a system administrator to pick from a range of operating system images for use by the specific machine, thereby adding it to the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/dverkamp/notes/start?rev=1211296510&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-20T08:15:10-07:00</dc:date>
        <title>soc:2008:dverkamp:notes:start</title>
        <link>http://etherboot.org/wiki/soc/2008/dverkamp/notes/start?rev=1211296510&amp;do=diff</link>
        <description>Daniel Verkamp: COMBOOT Support

Notes

COMBOOT

	*  &lt;http://syslinux.zytor.com/wiki/index.php/Comboot_API&gt;
	*  What should happen if/when a COMBOOT executable returns?  Do any other image types ever return?

Basic COMBOOT execution sequence

	*  Detect image type (.com/.cbt -&gt; 16-bit COMBOOT; .c32 or magic number B8 FF 4C CD 21</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2008/mdeck/journal/week4?rev=1214415268&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-25T10:34:28-07:00</dc:date>
        <title>soc:2008:mdeck:journal:week4</title>
        <link>http://etherboot.org/wiki/soc/2008/mdeck/journal/week4?rev=1214415268&amp;do=diff</link>
        <description>Michael Decker: Driver Development

Week 4

----------

16 &amp; 17 June

I added dynamic allocation of RFDs today.

	*  Commit: [Drivers-eepro100] Implemented dynamic allocation of RFDs.

The struct ifec_rfd rfa[RFD_COUNT] member of struct ifec_private was replaced with a struct io_buffer *rx_iobs[RFD_COUNT] member.  Thus, the NIC private data holds an array of pointers to io_buffers.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/wrapup?rev=1269384603&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-03-23T15:50:03-07:00</dc:date>
        <title>soc:2009:wrapup</title>
        <link>http://etherboot.org/wiki/soc/2009/wrapup?rev=1269384603&amp;do=diff</link>
        <description>Google Summer of Code 2009 Wrapup Report

Overview

In 2009 the Etherboot Project was pleased to participate in Google Summer of Code 2009.  

Our main project page for Google Summer of Code 2009 is here.

A full record of our Google Summmer of Code participation for all years is available
here.

This marks our fourth consecutive annual participation in this excellent mentoring program.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/notes/rtl8169.c?rev=1247019992&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-07T19:26:32-07:00</dc:date>
        <title>soc:2009:asdlkf:notes:rtl8169.c</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/notes/rtl8169.c?rev=1247019992&amp;do=diff</link>
        <description>rtl8169_probe
	alloc_etherdev
	netdev_init
	pci_set_drvdata
	adjust_pci_Device
	rtl8169_irq_mask_and_ack
	rtl_soft_reset 
	rtl8169_get_mac_version 
	rtl8169_init_phy 
		rtl_hw_phy_config
			[one of several versions of rtlXXXXX_X_hw_phy_config]
		pci_write_config_byte
		mdio_write
		rtl8169_phy_reset 
			phy_reset_enable
			phy_reset_pending
		rtl8169_set_speed
			set_speed
	netdev_link_up

rtl8169_open
	rtl8169_setup_tx_resources
	rtl8169_setup_rx_resources
		rtl8169_refill_rx_ring
			rtl8169_po…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/notes/skge.c?rev=1247426281&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-12T12:18:01-07:00</dc:date>
        <title>soc:2009:asdlkf:notes:skge.c</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/notes/skge.c?rev=1247426281&amp;do=diff</link>
        <description>skge_probe
	alloc_etherdev
	netdev_init
	pci_set_drvdata
	adjust_pci_device
	skge_get_register_address
	skge_hardware_reset
	skge_load_chip_identifiers
	skge_initialize
		skge_genesis_init
		skge_generic_init
		skge_stop_and_configure_clocks
	skge_devinit
		skge_supported_modes
		netdev_link_down
	netdev_link_up

skge_open
	//no separation done on allocation... 

	//setup rxresources
	skge_ring_alloc
	skge_rx_fill
		populate_rx_descriptor
	//setup_tx_resources
	skge_ring_alloc
			
	skge_start_cl…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week4?rev=1277062067&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-20T12:27:47-07:00</dc:date>
        <title>soc:2010:andreif:journal:week4</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week4?rev=1277062067&amp;do=diff</link>
        <description>===== Week 4 [ Mon 14 Jun 2010 - Sun 20 Jun 2010 ] =====

==== Day 1 [ Mon 14 Jun 2010 ] ====

Git commit: [[http://git.etherboot.org/?p=people/andreif/gpxe.git;a=commit;h=50c10591aaba4a808abd935df81df03cd0562e84|50c10591aaba4a808abd935df81df03cd0562e84]]

I've started working on the forcedeth driver's .probe routine. After several lines of code I remembered stefanha's advice that I should start to familiarise myself with gPXE's core source code. And so I did. Since I was working on .probe I wan…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week2?rev=1244444068&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-07T23:54:28-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week2?rev=1244444068&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 2

Monday, 1 June

Banged out the rtl8180 driver today, based on the Linux code, and tweaked things that came up while doing it.

	*  
[drivers 802.11] Initial import Realtek 8180/8185 driver from Linux
	*  
[nvs] Add init function for Atmel 93C66 EEPROM
	*  
[802.11] Tweaks to API for clarity and practicality
	*  
[drivers rtl8180] First shot at an rtl8180/8185 driver
	*  
[drivers rtl8180] Fix the main rtl8180 driver filename

It doesn't…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_pe?rev=1244584288&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-09T14:51:28-07:00</dc:date>
        <title>soc:2009:dverkamp:notes:windows_pe</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_pe?rev=1244584288&amp;do=diff</link>
        <description>Windows PE boot

Test

Boot into a Windows PE operating system generated according to these instructions via TFTP.

DUT configuration

No physical disks present.  System configured to boot from NIC equipped with gPXE ROM.

Environment configuration

TFTP server hosting WinPE files.  DHCP server providing network configuration and path to WinPE's</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/peper/project_plan/start?rev=1276558273&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-14T16:31:13-07:00</dc:date>
        <title>soc:2010:peper:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2010/peper/project_plan/start?rev=1276558273&amp;do=diff</link>
        <description>Piotr Jaroszyński: Usermode debugging under Linux

Project Plan

Summary

Allow gPXE to run as a usermode application under Linux on both i386 and x86_64. Hence opening new debugging possibilities and shortening the development cycle considerably.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week4?rev=1308317325&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-17T06:28:45-07:00</dc:date>
        <title>soc:2011:pcmattman:journal:week4</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/journal/week4?rev=1308317325&amp;do=diff</link>
        <description>Week 4 (June 13 to June 20)

Day 1 (June 13)

Today was a public holiday in Queensland. I used the day to recover from the sickness over the weekend.

I talked to Guo-Fu about DHCPv6 - I'll be implementing it this week.

I'm beginning to realise I might want to make soliciting a prefix an operation that returns a status code. This way the caller can determine whether or not a DHCPv6 request needs to be made to find information such as</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/people/xl0/gpxe-timeline?rev=1184419730&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-14T06:28:50-07:00</dc:date>
        <title>people:xl0:gpxe-timeline</title>
        <link>http://etherboot.org/wiki/people/xl0/gpxe-timeline?rev=1184419730&amp;do=diff</link>
        <description>gPXE ARM Port Time Line

July week 2

Rewrite the timer subsystem, update the i386 and ixp4xx timers.

July week 3

Code to pass configuration tags to the Linux kernel.

Make the Linux kernel boot.

Teach the bImage prefix to preserve the tags passed from the previous boot loader.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week11?rev=1281388373&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-09T14:12:53-07:00</dc:date>
        <title>soc:2010:andreif:journal:week11</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week11?rev=1281388373&amp;do=diff</link>
        <description>Week 11 [ Mon 2 Aug 2010 - Sun 8 Aug 2010 ]

Day 1 [ Mon 2 Aug 2010 ]

Git commit: aa205b0d6b511e989af68d07794859dac6829be3

Back after a long week with not much activity. I am commited to finish this last mini-project, consisting of getting Xen to work under gPXE, using multiboot.

After yesterday's meeting it has been decided that an extra</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2006/derekpryor/start?rev=1210408070&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-10T01:27:50-07:00</dc:date>
        <title>soc:2006:derekpryor:start</title>
        <link>http://etherboot.org/wiki/soc/2006/derekpryor/start?rev=1210408070&amp;do=diff</link>
        <description>Derek Pryor, gPXE Secure Network Booting

Some useful links

	*  My Project Proposal

----------

Update (2006/07/21)

Have almost finished porting the MatrixSSL versions of SHA1 and MD5. (Just one function I have to track down). Going to work on RSA next and see how small we can get it.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week1?rev=1306543498&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-05-27T17:44:58-07:00</dc:date>
        <title>soc:2011:pcmattman:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/journal/week1?rev=1306543498&amp;do=diff</link>
        <description>Week 1 (May 23 to May 29)

Day 1 (May 23)

Jumped into the code and had a look at the existing IPv6 implementation. I managed to figure out how to enable it again (with the right #defines in config.h) and was able to dump information about each IPv6 packet passing through the system. So far so good! The next steps will be getting IPv6 packets to the next layer up (ICMPv6, UDP and TCP) so I can start working on stateless autoconfiguration.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/pravin/project_plan/start?rev=1244065734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-03T14:48:54-07:00</dc:date>
        <title>soc:2009:pravin:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2009/pravin/project_plan/start?rev=1244065734&amp;do=diff</link>
        <description>Pravin Shinde: boot.kernel.org - Universal remote network booting for the masses

Project aims for creation of website, which can be used by any user for creating and downloading
customized boot images, system tools, utilities and network installation images based on needs.
It will also support HTTP based booting with PXELinux and allow users to customize the system using
the flexibility of interface provided be Syslinux and boot from it without installation. We plan to enable normal
users to ex…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/journal/week7?rev=1278952666&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-12T09:37:46-07:00</dc:date>
        <title>soc:2010:andreif:journal:week7</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/journal/week7?rev=1278952666&amp;do=diff</link>
        <description>Week 7 [ Mon 5 Jul 2010 - Sun 11 Jul 2010 ]

Day 1 [ Mon 5 Jul 2010 ]

Git commit: 959381fd2d516e50324047113bf7a5bd160d07e3

Started working on the .transmit routine. As a minor off-topic, I just want to say that even though this driver hasn't been so much fun to develop ( because it involved a lot more copy and paste than the old one ), it definitely compensated through a large number of theoretical concepts ( see my previous entries for more details ). The first thing I ran into today was</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/meteger/journal/week9?rev=1311335326&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-22T04:48:46-07:00</dc:date>
        <title>soc:2011:meteger:journal:week9</title>
        <link>http://etherboot.org/wiki/soc/2011/meteger/journal/week9?rev=1311335326&amp;do=diff</link>
        <description>Day 0 ( July 17 )

Daily meeting, thanks to Stefan transmit seems to work now, even with 1GBit/s.

Day 1 ( July 18 )

In the meeting yesterday we discussed moving all functions relevant to rx ring and other memory allocations to tg3_main.c. I implemented this change today and also implemented the tx completion code. It seems to work so far, but isn't fully tested yet. The NIC hardware forces us to use a ring size of 512 ring entries, I haven't transmitted &gt; 512 packets yet to see if wrapping aro…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week4?rev=1245643204&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-21T21:00:04-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week4</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week4?rev=1245643204&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 4

Monday, 15 June

Worked on a bunch of small things today. My video card didn't come until late in the day, so I was only able to do a little iSCSI testing, but what I found was revealing.

Commits:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week12?rev=1281688284&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-13T01:31:24-07:00</dc:date>
        <title>soc:2010:cooldavid:journal:week12</title>
        <link>http://etherboot.org/wiki/soc/2010/cooldavid/journal/week12?rev=1281688284&amp;do=diff</link>
        <description>Port wscale branch against current gPXE master

Recent TCP updates is a lot different from previous base of wscale branch.

Hit a GCC optimization trap

For the following code


#include &lt;stdio.h&gt;

struct foo {
        char huge_gap[0x4005d0];
        int v;
};

void store_and_print(int *val, struct foo *f)
{
        *val = f-&gt;v;
        if ( !f ) {
                printf(&quot;Value is wrong.\n&quot;);
        } else {
                printf(&quot;Value is correct.\n&quot;);
        }
}

int main()
{
        int u…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/project_plan/start?rev=1306068627&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-05-22T05:50:27-07:00</dc:date>
        <title>soc:2011:pcmattman:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/project_plan/start?rev=1306068627&amp;do=diff</link>
        <description>Project Plan

Project Summary

This project aims to clean up the existing IPv6 implementation in gPXE and continue implementing such features as autoconfiguration (via router advertisement and stateless autoconfiguration), DNS AAAA records, and DHCPv6.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/andreif/project_plan/start?rev=1273747598&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-13T03:46:38-07:00</dc:date>
        <title>soc:2010:andreif:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2010/andreif/project_plan/start?rev=1273747598&amp;do=diff</link>
        <description>Andrei Faur: Device driver implementation

Project Plan

Summary

The aim of this project is to implement a driver for a currently unsupported NIC either by writing one from scratch or by porting an already existing open-source implementation.

Milestones and Timeline</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_xp_iscsi?rev=1244846817&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-12T15:46:57-07:00</dc:date>
        <title>soc:2009:dverkamp:notes:windows_xp_iscsi</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/notes/windows_xp_iscsi?rev=1244846817&amp;do=diff</link>
        <description>Windows iSCSI forward authentication

Test

Boot into a Windows XP operating system stored on an iSCSI target.

DUT configuration

No physical disks present.  System configured to boot from NIC equipped with gPXE ROM.

Environment configuration

iSCSI target running IETD set up to require forward CHAP authentication.  DHCP server providing network configuration and iSCSI root-path.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/burningroms/willem?rev=1240261509&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-20T14:05:09-07:00</dc:date>
        <title>burningroms:willem</title>
        <link>http://etherboot.org/wiki/burningroms/willem?rev=1240261509&amp;do=diff</link>
        <description>alpha relese --- Pär Moberg

Willem

Burning EPROMs using willem based programmers.

Shopping List

You will need:

	*  PC with a IBM parallel port
	*  Willem based programmer
	*  Power supply (optional, see below)
	*  EPROM, UV or electronic erasable
	*  Network card with a ROM socket or ROM-card so you can use/test your new burned EPROM</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week10?rev=1280488499&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-30T04:14:59-07:00</dc:date>
        <title>soc:2010:cooldavid:journal:week10</title>
        <link>http://etherboot.org/wiki/soc/2010/cooldavid/journal/week10?rev=1280488499&amp;do=diff</link>
        <description>Create a branch to merge latest iPXE TCP related commits based on gPXE master

Shortlog of iPXE merge commits

Git-branch

	*  Guo-Fu Tseng (2):
		*  [tcp] Randomize TCP bind port
		*  [hci] Continue processing while prompting for shell banner


	*  Michael Brown (8):</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week2?rev=1275655624&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-04T05:47:04-07:00</dc:date>
        <title>soc:2010:cooldavid:journal:week2</title>
        <link>http://etherboot.org/wiki/soc/2010/cooldavid/journal/week2?rev=1275655624&amp;do=diff</link>
        <description>Week 2 [ 31 May - 6 Jun 2010 ]: Discuss TCP and memory changes, update jme driver

jme driver

	*  From Joshua Oreman
		*  jme_check_link(struct net_device *netdev, int testonly)

			*  In this function, I believe the code and string data used in constructing linkmsg will make it into even non-debug versions of the executable. If that's true it would be better if you could perform all the manipulations in the final DBG() line, using the ?: operator and such. It's possible the compiler is clever …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/pravin/journal/fedora11bko?rev=1248698141&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-27T05:35:41-07:00</dc:date>
        <title>soc:2009:pravin:journal:fedora11bko</title>
        <link>http://etherboot.org/wiki/soc/2009/pravin/journal/fedora11bko?rev=1248698141&amp;do=diff</link>
        <description>Booting Fedora with BKO

Where I am getting stuck

Following are the messages which are showen before getting stuck


Mounting proc filesystem
Mounting sysfs filesystem
Creating initial /dev
Running plymouthd
udev: starting version 141


and It hangs after this point. I have bad feeling that it is not even reaching the step where it will execute /init script</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/cooldavid/journal/week1?rev=1275052553&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-28T06:15:53-07:00</dc:date>
        <title>soc:2010:cooldavid:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2010/cooldavid/journal/week1?rev=1275052553&amp;do=diff</link>
        <description>Week 1: Update wiki, TCP tunning

May 27th.

	*  Update wiki for week -4 to week 0 progress.

May 28th.

Weekly meeting

	*  Post JMicron driver to gpxe-devel as a patch.
	*  Start a discussion on gpxe-devel regarding to TCP and memory changes.
	*  Update plan to reflect my current work.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/cooldavid/journal/weekb2?rev=1274891765&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-26T09:36:05-07:00</dc:date>
        <title>soc:2010:cooldavid:journal:weekb2</title>
        <link>http://etherboot.org/wiki/soc/2010/cooldavid/journal/weekb2?rev=1274891765&amp;do=diff</link>
        <description>Week -2: Implement JMicron driver

Apr. 28th to May 1st

Day 1

Start to write JMicron Driver.

	*  Helper functions
		*  jme_reload_eeprom(): Which cause the MAC processor to place MAC Address to register.

		*  j{read,write}32(): Register reading/writing wrapper.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/peper/journal/week0?rev=1275416775&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-01T11:26:15-07:00</dc:date>
        <title>soc:2010:peper:journal:week0</title>
        <link>http://etherboot.org/wiki/soc/2010/peper/journal/week0?rev=1275416775&amp;do=diff</link>
        <description>Piotr Jaroszyński: Usermode debugging under Linux

Previous work [ Prior to 24 May 2010 ]

Unrelated work

Before I even started thinking about a proposal for my project I decided to do some pretty much random unrelated work to get a better feeling of gPXE in general. This resulted in a few trivial patches:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/derekpryor?rev=1153510382&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-21T12:33:02-07:00</dc:date>
        <title>soc:derekpryor</title>
        <link>http://etherboot.org/wiki/soc/derekpryor?rev=1153510382&amp;do=diff</link>
        <description>Derek Pryor, gPXE Secure Network Booting

Some useful links

	*  My Project Proposal

----------

Update (2006/07/21)

Have almost finished porting the MatrixSSL versions of SHA1 and MD5. (Just one function I have to track down). Going to work on RSA next and see how small we can get it.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wiki/navigation?rev=1259439602&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-28T12:20:02-07:00</dc:date>
        <title>wiki:navigation</title>
        <link>http://etherboot.org/wiki/wiki/navigation?rev=1259439602&amp;do=diff</link>
        <description>* [[:start|Home]]
  * [[:about|About our Project]]
  * [[:download|Download]]
  * [[:screenshots|Screenshots]]
  * Documentation
    * [[:howtos|HowTo Guides]]
    * [[:appnotes|Application Notes]]
    * [[:faq:|FAQs]]
    * [[:doc|General Doc]]
    * [[:talks|Videos, Talks, and Papers]]
    * [[:hardwareissues|Hardware Issues]]
  * [[:mailinglists|Mailing lists]]
  * [[http://support.etherboot.org/|Bugtracker]]
  * [[:contributing|Contributing]] 
    * [[:editing_permission|Wiki Edit Permission…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-19T01:20:55-07:00</dc:date>
        <title>biosext</title>
        <link>http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff</link>
        <description>Adding gPXE to BIOSes

Add gPXE to the BIOS of the Jetway J7F2WE family of motherboards (replacing the Intel UNDI PXE code)

Jeff Campbell, Turks &amp; Caicos Islands, February 27, 2008

 Note:  This is completely without warranty.  It worked for me.  It may not work for you.  It may wreck your system.  If you don't know what you're doing, don't do it.  You have no recourse but to blame yourself and sit in the dark rocking in the fetal position if this fails.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/notes/scripting_doc/features_added?rev=1250407194&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-16T00:19:54-07:00</dc:date>
        <title>soc:2009:lynusvaz:notes:scripting_doc:features_added</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/notes/scripting_doc/features_added?rev=1250407194&amp;do=diff</link>
        <description>Scripting Features

The features mentioned here are NOT YET part of mainline gPXE, and are still under development. The modified code can be found in my git repository, in the expt branch.

	*  Identifiers
	*  Arithmetic evaluator
	*  Quoting
	*  Branches</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/notes/3c90x.c?rev=1247021101&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-07T19:45:01-07:00</dc:date>
        <title>soc:2009:asdlkf:notes:3c90x.c</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/notes/3c90x.c?rev=1247021101&amp;do=diff</link>
        <description>a3c90x_probe
	alloc_etherdev
	netdev_init
	pci_set_drvdata
	adjust_pci_device
	a3c90x_reset
	netdev_link_up
	(netdev_put)

a3c90x_open
	a3c90x_hw_start
	a3c90x_setup_tx_ring
	a3c90x_setup_rx_ring
		a3c90x_refill_rx_ring
			 a3c90x_prepare_rx_desc
	(a3c90x_free_resources)
	(a3c90x_reset)

a3c90x_transmit
	a3c90x_internal_IssueCommand

a3c90x_poll
	a3c90x_process_tx_packets
		netdev_tx_complete
	a3c90x_process_rx_packets
		(netdev_rx_err)
		iob_put
		netdev_rx
		a3c90x_refill_rx_ring
			alloc_iob
…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2010/peper/notes/usermode_howto?rev=1281909532&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-15T14:58:52-07:00</dc:date>
        <title>soc:2010:peper:notes:usermode_howto</title>
        <link>http://etherboot.org/wiki/soc/2010/peper/notes/usermode_howto?rev=1281909532&amp;do=diff</link>
        <description>Piotr Jaroszyński: Usermode debugging under Linux

How to use Linux usermode

Building
$ make bin-x86_64-linux/gpxe.linux
Runing
$ ./bin-x86_64-linux/gpxe.linux --net tap,if=tap3,mac=52:54:00:12:34:56 --net tap,if=tap4,mac=52:54:00:12:34:57 # etc
Setting up tap</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/project_plan/start?rev=1244305285&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-06T09:21:25-07:00</dc:date>
        <title>soc:2009:asdlkf:project_plan:start</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/project_plan/start?rev=1244305285&amp;do=diff</link>
        <description>Chris Kluka: Network driver development

Project Plan

Summary

Outline

Milestones and Timeline

Given that drivers for this card exist for BSD and Linux, implementing a
driver for gPXE should not be too difficult. After looking through the gPXE API</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-03-10T18:39:58-07:00</dc:date>
        <title>rplchaining</title>
        <link>http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff</link>
        <description>RPL chainloading

If you have a large number of machines which already have a legacy RPL implementation (e.g. network cards containing a Novell RPL ROM), then you may want to avoid having to reflash each machine's network card.  You can achieve this by placing gPXE on your RPL server.  The RPL-capable machines will download gPXE via RPL, and instantly become gPXE-capable machines.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dev/fnrec?rev=1272799751&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-02T04:29:11-07:00</dc:date>
        <title>dev:fnrec</title>
        <link>http://etherboot.org/wiki/dev/fnrec?rev=1272799751&amp;do=diff</link>
        <description>Overview

Fnrec is a tool that collects a
trace of functions called before a crash or hang.  It can be used to
determine what led to the issue and which function was called last.

How tracing works

Fnrec uses the gcc
-finstrument-functions compiler flag to trace each function call
and record it into a memory buffer.  The memory buffer has a magic
number at the start to identify it as valid and not just random bytes
in memory.  As gPXE runs, it records each function call into the
memory buffer. …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wiki/qemupxeknife?rev=1243096987&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-23T09:43:07-07:00</dc:date>
        <title>wiki:qemupxeknife</title>
        <link>http://etherboot.org/wiki/wiki/qemupxeknife?rev=1243096987&amp;do=diff</link>
        <description>Get PXE Knife working with QEMU

If you dont know what is PXE Knife, better visit &lt;http://pxeknife.erebor.org/&gt; because I will be assuming you know all on that site.

Get PXE Knife working with QEMU with tftp

	*  Downloaded &lt;http://pxeknife.erebor.org/releases/pxeknife-0.0.2.tar.gz&gt; at /home/myname/pxeknife/
	*  unpacked it in /home/myname/pxeknife</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-07T04:00:12-07:00</dc:date>
        <title>eb_imagetypes</title>
        <link>http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff</link>
        <description>Etherboot image types

Using rom-o-matic, or compiling Etherboot yourself, you will be able to generate different file types, depending on your needs.

Those file types shall be explained here:

Floppy bootable ROM image (.zdsk)

These files are meant to be used on floppy disks. If you obtained such a file, copy it to a floppy: Under Linux,</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dev/netdriverapi?rev=1187473421&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-18T14:43:41-07:00</dc:date>
        <title>dev:netdriverapi</title>
        <link>http://etherboot.org/wiki/dev/netdriverapi?rev=1187473421&amp;do=diff</link>
        <description>gPXE Network Driver API Documentation

net_device::open ( struct net_device *netdev )

Here MAC address is programmed over the device (NIC). Then receive buffer for the device is created 
and its memory is released in net_device::close(). This address for the ring buffer is transfer to the NIC’s 
register. This is the place where configuration of the device is also done like enable transmission, 
receive. Other parameters like burst rate, transfer threshold, reception of broadcast and multicast …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wiki/syntax?rev=1488916923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-03-07T12:02:03-07:00</dc:date>
        <title>wiki:syntax</title>
        <link>http://etherboot.org/wiki/wiki/syntax?rev=1488916923&amp;do=diff</link>
        <description>Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/notes/generic.c?rev=1247022714&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-07T20:11:54-07:00</dc:date>
        <title>soc:2009:asdlkf:notes:generic.c</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/notes/generic.c?rev=1247022714&amp;do=diff</link>
        <description>probe
	alloc_etherdev
	netdev_init
	pci_set_drvdata
	adjust_pci_Device
	setup_IRQ
	software_reset_device
	read information from the card to identify version/etc...&gt;
	Initialize_phy
		write_standard_init_config
			write_card_version_specific_config
		configure_and_stop_clocks
		determine_and_configure_wire_speed
	netdev_link_up

open
	setup_tx_resources
	setup_rx_resources
		refill_rx_ring
			populate_rx_descriptor
	start_clocks
		software_reset_device

transmit
	write_new_packets_to_tx_ring

pol…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/asdlkf/journal/week1?rev=1244253873&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-05T19:04:33-07:00</dc:date>
        <title>soc:2009:asdlkf:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2009/asdlkf/journal/week1?rev=1244253873&amp;do=diff</link>
        <description>Chris Kluka: Network driver development

Journal Week 1

Prior to week 1: Before week one began, I constructed a basic environment for the development to take place over the following weeks. This entailed:

- Existing components on one box were consolodated into another box (approx 2 hours)
- System was format-reinstalled with ubuntu. This system is to be the host 'booting' server and where I will be developing code. I also prepared a local git repository, configured port forwarding for SSH and …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/journal/week5?rev=1308970189&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-24T19:49:49-07:00</dc:date>
        <title>soc:2011:pcmattman:journal:week5</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/journal/week5?rev=1308970189&amp;do=diff</link>
        <description>Week 5 (June 20 to June 27)

Day 1 (June 20)

I managed to get my commits rebased and merged ready for upstream merge today... finally! It still took quite a while but I managed to sort out the conflicts as they came and it's all come together quite nicely. I also realised I've forgotten to sign off all my commits as they are committed, so I went through and signed them all off as well.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/win2k8_physical?rev=1256854825&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-29T15:20:25-07:00</dc:date>
        <title>sanboot:win2k8_physical</title>
        <link>http://etherboot.org/wiki/sanboot/win2k8_physical?rev=1256854825&amp;do=diff</link>
        <description>Windows Server 2008 boot from SAN

Installation

Start by installing Windows Server 2008 to a physical disk.  It is best to use an external USB, FireWire, or eSATA disk; this will make later stages easier.

When installing, use a small partition (around 8GB) rather than the whole disk.  At the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/notes/linux_mkbootfs?rev=1245419468&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-19T06:51:08-07:00</dc:date>
        <title>soc:2009:dverkamp:notes:linux_mkbootfs</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/notes/linux_mkbootfs?rev=1245419468&amp;do=diff</link>
        <description>Linux bzImage boot

Test

Boot into a minimal Linux/busybox system created using mkbootfs via HTTP.

DUT configuration

No physical disks present.  System configured to boot from NIC equipped with gPXE ROM.

Environment configuration

Apache HTTP server providing gPXE script, kernel, initrd, and modules as separate files.  gPXE script set to instruct client to download kernel, initrd and relevant modules.  DHCP server providing network configuration and path to gPXE script on HTTP server.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/journal/week10?rev=1248987358&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-30T13:55:58-07:00</dc:date>
        <title>soc:2009:dverkamp:journal:week10</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/journal/week10?rev=1248987358&amp;do=diff</link>
        <description>Daniel Verkamp: Automated regression testing

Journal Week 10

Monday, July 27

Attempting to debug Test::Machine::Qemu lockup with -curses and -monitor on a PTY.

Noted that with -curses and -serial stdio, no lockup occurs, so this seems to be unique to -curses.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/dverkamp/journal/week1?rev=1243903441&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-01T17:44:01-07:00</dc:date>
        <title>soc:2009:dverkamp:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2009/dverkamp/journal/week1?rev=1243903441&amp;do=diff</link>
        <description>Daniel Verkamp: Automated regression testing

Journal Week 1

Monday, May 25

Wrote up a list of some potential test cases on notes page.

Tuesday, May 26

Discussed Autotest framework with mcb30; goals for the week:

	*  Create a list of test cases
	*  Get Autotest running and add a simple test to verify gPXE builds, then document</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week9?rev=1248805725&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-28T11:28:45-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week9</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week9?rev=1248805725&amp;do=diff</link>
        <description>July 20: More comments today. Got some feedback from Stefan about the quotes patch. Also added the automated test to the same patch. Decided to have a look at the sizes before and after the quoting (make bin/rtl8139.dsk.sizes):
Before
 text    data     bss     dec     hex filename
  629	      8	      0	    637	    27d	bin/exec.o
  321	     16	      4	    341	    155	bin/shell.o</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-10-13T05:56:18-07:00</dc:date>
        <title>openwrt</title>
        <link>http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff</link>
        <description>Create an appliance running OpenWRT serving gpxelinux.0

Edit the file /etc/init.d/dnsmasq to add the right location and arguments:
start() {
  include /lib/network
  scan_interfaces
  config_load /var/state/network
  config_load dhcp
#      args=&quot;&quot;
  args=&quot; --enable-tftp --tftp-root=/mnt/usbdrive --dhcp-boot=/mnt/usbdrive/pxelinux.0&quot;</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/bochs?rev=1157026523&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T05:15:23-07:00</dc:date>
        <title>bochs</title>
        <link>http://etherboot.org/wiki/bochs?rev=1157026523&amp;do=diff</link>
        <description>Running Etherboot within Bochs

Orginal documentation by Michael Brown mbrown@fensystems.co.uk 
Based on an idea suggested by H. Peter Anvin hpa@zytor.com 
Wikified By Tim Fletcher tim@parrswood.manchester.sch.uk 
Reformatted by Anselm M. Hoffmeister</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week6?rev=1246855558&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-05T21:45:58-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week6</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week6?rev=1246855558&amp;do=diff</link>
        <description>June 29: Implemented while-done loops and for-done loops. The current idea is:

	*  I have a global variable prog_ctr, that is the program counter
	*  A stack (not as a stack, but just for storage space) is used to store the commands
	*  Another stack is used to store the information for a loop.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot/win2k3?rev=1187995713&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-24T15:48:33-07:00</dc:date>
        <title>sanboot:win2k3</title>
        <link>http://etherboot.org/wiki/sanboot/win2k3?rev=1187995713&amp;do=diff</link>
        <description>Windows Server 2003 boot from SAN

Windows Server 2003 supports booting from either an iSCSI or AoE SAN.  You cannot install directly to the SAN target; you must first install Windows Server 2003 to a physical disk.

Installation

Start by installing Windows Server 2003 to a physical disk.  It is best to use an external USB, FireWire, or eSATA disk; this will make later stages easier.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week3?rev=1245131141&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-15T22:45:41-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week3</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week3?rev=1245131141&amp;do=diff</link>
        <description>June 6: Weekly meeting today. We discussed about the syntax:

	*  Variable names can contain '-' and '/'. So, something like ${a+2} is not possible.
	*  Decided we needed a formal document describing the syntax.

June 7: Spent today writing down a formal grammar. Discussed it with Stefan, who suggested some changes, which I put in.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week1?rev=1243917508&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-01T21:38:28-07:00</dc:date>
        <title>soc:2009:lynusvaz:journal:week1</title>
        <link>http://etherboot.org/wiki/soc/2009/lynusvaz/journal/week1?rev=1243917508&amp;do=diff</link>
        <description>Lynus Vaz: Enhanced scripting language

Journal Week 1

23 May: Had a look at the current code in gPXE. Decided to start off with an arithmetic parser. Tried implementing a precedence parser, as described on wikipedia, and ended up with a rather large code. Stefan put together a much smaller recursive descent parser for addition/subtraction and multiplication/division, so I'll modify that tomorrow.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2009/oremanj/journal/week5?rev=1246080402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-26T22:26:42-07:00</dc:date>
        <title>soc:2009:oremanj:journal:week5</title>
        <link>http://etherboot.org/wiki/soc/2009/oremanj/journal/week5?rev=1246080402&amp;do=diff</link>
        <description>Joshua Oreman: 802.11 wireless development

Journal Week 5

Monday, 22 June

Had a very long meeting with the mentors this morning. Things discussed:

	*  Encryption thoughts: use netX/key for the encryption key setting, to avoid interfering with the iSCSI</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/pcmattman/notes/start?rev=1313458477&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-15T18:34:37-07:00</dc:date>
        <title>soc:2011:pcmattman:notes:start</title>
        <link>http://etherboot.org/wiki/soc/2011/pcmattman/notes/start?rev=1313458477&amp;do=diff</link>
        <description>Matthew Iselin: IPv6 Implementation

Notes

I'll update this with notes and links to websites I find as I'm working on the project that might be handy later on. The notes here may also be the foundation for the IPv6 documentation later on.

Useful RFCs</description>
    </item>
</rdf:RDF>
