search for: yalamanchili

Displaying 20 results from an estimated 26 matches for "yalamanchili".

2006 Jan 14
3
Patch to add Symbols/segments loader for mboot.c
Hello, I use Tim's mboot.c32 to load multiboot kernels over pxelinux. However, some kernels require the symbol table and other information in the ELF section header table to be able to load properly. This functionality is not present in mboot.c now, so I added support for it. The patch is attached. It would be great if you can push this into the next release of syslinux so ELF multiboot
2007 Feb 06
3
Syslinux: Broken file reading for fat16 with 3.35+?
Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux
2006 Nov 21
1
ipappend behaviour for bootif
Is it normal for pxelinux to append something like BOOTIF=01-aa-bb-cc-dd-ee-ff ? the leading 01- is there in my config file name, but this doesn't seem to be right behaviour. Can someone confirm if this is a bug? I tried this on syslinux 3.21. thanks. -- Ram Yalamanchili
2007 Jan 11
1
Patch: Parse append arguments properly in mboot module
...e back-to-back to be considered "appened options", so this should be safe enough to not take out-of-place arguments and tack onto the kernel cmdline. Last time i sent in some of the elf section loader patches, i think Peter had trouble importing time. Hopefully it works now. thanks, Ram Yalamanchili -------------- next part -------------- A non-text attachment was scrubbed... Name: syslinux_mboot_parse_append_args.patch Type: text/x-patch Size: 1552 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20070111/f3f7a9e2/attachment.bin>
2007 Apr 18
2
[Patch]: Drive/Partition and extensible filesystem support for syslinux
Here is the patch for making syslinux enable opening partitions with fat filesystems (well, the architecture is in place to make it open other filesystems too). Usage is like this: #include <syslinux/io.h> #include <syslinux/partitions.h> #include <fs/fat/libfat.h> syslinux_devdesc dfd; struct libfat_filesystem* fs; diskinfo disk_info; char mbr[512]; static part_entry
2007 Feb 12
4
Read disk not working in 3.35+
Hey, Looks like read disk function which was launched in 3.35 isnt working. Did anyone test this on any hardware? I'm using it thru the com32 interface to read contents of the active partition of a USB boot key (syslinux). I did a sample test like: void scanAndPrint() { com32sys_t regs_in; char *sectorBuf = __com32.cs_bounce; int i; memset(sectorBuf, 0x0, 512); // XXX MARK 1
2006 Jan 14
1
Patch mboot.c with Symbols/segments loader for multiboot ELF kernels
The program segments loaded presently in mboot.c only consists of a subset of sections described by the ELF Section Header Table (SHT) in the ELF kernel binary. Segments with useful information often needed for debugging purposes (symbol tables, string tables, etc.) aren't usually present in the program segments and hence not loaded above. Some kernels use this debugging information to
2006 Mar 09
2
multiboot patch
Peter, Is this page update to date? http://www.kernel.org/git/?p=boot/syslinux/syslinux.git;a=shortlog I sent a multiboot symbol table loading patch (syslinux-3.11-mboot-sym_table-patch) a few months ago and I thought you have checked it in. I didn't follow up after that. But i dont see it in the changes now, should i resend it? thanks, Ram
2006 Nov 20
0
Patch: Parse append arguments properly in mboot module
...e back-to-back to be considered "appened options", so this should be safe enough to not take out-of-place arguments and tack onto the kernel cmdline. Last time i sent in some of the elf section loader patches, i think Peter had trouble importing time. Hopefully it works now. thanks, Ram Yalamanchili -------------- next part -------------- A non-text attachment was scrubbed... Name: syslinux_mboot_parse_append_args.patch Type: text/x-patch Size: 1552 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20061120/d203a7dd/attachment.bin>
2006 Nov 28
2
How to determine your bootloader from the kernel
If you have a multiboot kernel which is booted by syslinux/pxelinux/isolinux, etc., is there a way to determine who actually is the bootloader among the three? I'm wondering if the multiboot header or any part of memory has a consistent identifier somewhere. thanks, Ram
2007 Jan 22
1
Knowing your boot disk
folks, If you boot from syslinux based USB/harddisk, is there a way to know the partition or disk you booted from? I'm using the mboot module, so if the info is availble to thru the COM api, i can get it and append it to cmdline. thanks. -- Ram
2007 Feb 06
1
Patch: Building syslinux on gcc 4
For newer distro's (like ubuntu 6.10, FC5+), syslinux build fails due to gcc 4. Here is a patch to get it to build properly. The only thing it does is add -fno-stack-protection to CFLAGS in all the Makefiles. http://svn.borg.ch/patches/syslinux/syslinux-gcc4.patch thanks, Ram
2007 Feb 23
1
Patch: Readconfig wont parse certain options anymore
com32/modules/readconfig.c: This is a side effect of is_kernel_type() overwrite the current pointer in a loop context. Hence subsequent options aren't parsed ever. This is particularily visible, if you use timeout option, which wont work in the latest 3.40-pre7. Patch: --- com32/modules/readconfig.c /opensource/syslinux-3.40-pre7/com32/modules/readconfig.c#2 +++ com32/modules/readconfig.c
2007 Mar 15
1
my_isspace can be isblank
Hey, I noticed my_isspace() is being used in menu/mainmenu and readconfig com32 modules. Why not use isblank() instead? Here's a patch: thanks. Ram --- com32/modules/menu.h //depot/opensource/main/syslinux-3/com32/modules/menu.h#2 +++ com32/modules/menu.h 07-03-15 16:27:14 @@ -87,11 +87,6 @@ void parse_configs(char **argv); extern int (*draw_background)(const char *filename); -static
2007 Mar 21
1
api headers..
Hi Peter, I just noticed your check-in of the api headers. Are you planning on making the fat library also into an API? This would make things easier for me for my safeboot module (redundant bootloader which i mailed you about last week). I aleady moved some of the chainboot's partition finding logic into outside files, so I can add that to the API as well. thanks, Ram
2007 May 03
1
cbios disk read problems
Hey folks, I am seeing this issue with machines on which I do I/O ops thru cbios mode. I noticed some of the reads at high sectors seem to be returning the wrong data even though the op itself succeds. The output of the int 13 call returns EFLAGS: 0x246 (CF is 0) and EAX is 0x1, which indicates success according to ralph brown's int13/02h page. The I/O code is exactly the same as the one in
2007 May 30
1
Changing hotkey when booting thru syslinux
Hey, I want to change the default "shift" key to fall into the syslinux shell to something else but wasn't able to find the code where this is done. Can someone point me to this? thanks. Ram
2012 Dec 28
1
[LLVMdev] verification methods for correctness of a compiler
Hello, Are there any translation validation tools available to check the correctness of a compiler after each stage, or any tool to check the correction of translation after some particular stage like AST or .ll generation or after optimization ? I would like to know if any of those are being used in clang's development and if any such tools exist in first place. I have come across certain
2013 Oct 03
3
[LLVMdev] runtime performance benchmarking tools for clang
Hi All, Could anyone point me to some good benchmarking tools to measure the runtime performance of clang compiled C++ applications. Thanks ! - Jyoti -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131003/3cc029f1/attachment.html>
2012 Dec 24
1
[LLVMdev] Debugging LLVM IR with GDB
Could anyone list up reasons why we need LLVM IR level debugger in place ? I could only think of one reason and that is to debug IR portability issues (?)