:: commit 2f4f645ea7d1e5884b514652ffa70e5748197258

diff --git a/CONFIG.md b/CONFIG.md
index eb21cd20..0f31d191 100644
--- a/CONFIG.md
+++ b/CONFIG.md
@@ -86,3 +86,4 @@ The format for `root` changes depending on the resource used.
 A resource can be one of the following:
 * `bios` - The `root` takes the form of `drive:partition`; for example: `bios://3:1/...` would use BIOS drive 3, partition 1. Partitions and BIOS drives are both 1-based. Omitting the drive is possible; for example: `bios://:2/...`. Omitting the drive makes Limine use the boot drive.
 * `guid` - The `root` takes the form of a GUID/UUID, such as `guid://736b5698-5ae1-4dff-be2c-ef8f44a61c52/...`. It is a filesystem GUID and not a partition GUID.
+* `tftp` - The `root` is the ip address of the tftp server to load the file from, if the root is left empty (`tftp:///file.elf`) the file will be loaded from the server limine booted from.
diff --git a/PXE.md b/PXE.md
new file mode 100644
index 00000000..704dc7e3
--- /dev/null
+++ b/PXE.md
@@ -0,0 +1,8 @@
+# Limine PXE support
+
+The `limine-pxe.bin` binary is a valid pxe boot image, in order to set up limine with pxe you need to setup a dhcp server
+with support for pxe booting, this can either be set up using a single dhcp server or your existing dhcp server and a proxy
+dhcp server such as dnsmasq.
+
+The limine configuration file is assumed to be on the server that it booted from, for further information on pxe specific
+configuration consult `CONFIG.md`