From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Date: Tue, 22 Oct 2013 11:34:51 +0100 Subject: [U-Boot] [PATCH] pxe: fix handling of absolute paths In-Reply-To: <1382119482-26224-1-git-send-email-robherring2@gmail.com> References: <1382119482-26224-1-git-send-email-robherring2@gmail.com> Message-ID: <1382438091.1657.87.camel@hastur.hellion.org.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, 2013-10-18 at 13:04 -0500, Rob Herring wrote: > From: Rob Herring > > pxelinux and syslinux differ in their handling of absolute paths in menu > files. A pxelinux path is aways prepended with the bootfile path while > syslinux allows for absolute paths. u-boot was always treating a leading > / as an absolute path breaking some pxelinux setups. Fix this by adding > a flag to distinguish pxelinux vs. syslinux behavior. > > Reported-by: Ian Campbell > Signed-off-by: Rob Herring You could also have Tested- or Acked-by from me if desired. I also took a gander at the syslinux code and found that core/fs/pxe/pxe.c:get_prefix() sets the initial cwd to the prefix. The lookups are done relative to this unless the path is a URL (roughly means it contains "::", see code/comments around the use of PXE_RELATIVE)). In particular a leading "/" isn't specially treated as far as I can see... Ian.