similar to: [PATCH] [memdisk] Additional comments in memdisk.inc and postprocess.pl

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Hi, how can I make it so that printing to a cups PDF printer can successfully run the postprocessing script I specified in /etc/cups/cups-pdf.conf? It does work with 'sentenforce permissve', and after creating and installing some selinux modules from audit.log entries, it still doesn't work, and there doesn't seem to be anything else that might prevent the postprocessing

https://bugs.freedesktop.org/show_bug.cgi?id=95190 Bug ID: 95190 Summary: Tomb Raider with PostProcessing enable and Depth of Field set to Ultra has white stuff in the foreground Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Joerg: > I propose to add the ability to ignore undefined symbols during initial > resolution, and then postprocess only those undefines for the second time > after the pass manager execution. Do you want to do that before or after dead code elimination? I think dead code elimination should be performed after all possible object code modifications done by lld. Therefore, it should be

+ Nick On 2/19/2015 9:00 AM, Shankar Easwaran wrote: > On 2/19/2015 3:58 AM, Denis Protivensky wrote: >> Joerg: >>> I propose to add the ability to ignore undefined symbols during initial >>> resolution, and then postprocess only those undefines for the second >>> time >>> after the pass manager execution. >> Do you want to do that before or

On Thu, Feb 19, 2015 at 10:40 PM, Denis Protivensky <dprotivensky at accesssoftek.com> wrote: > Shankar, > > Okay, I guessed the correct interface. > But what about the moment at which the function is called? > If it's called from Resolver::resolve(), it doesn't make any difference to > me as I cannot determine the need of specific symbols at that time. > > -

Hi everyone, In lld, I need to conditionally add symbols (like GLOBAL_OFFSET_TABLE) during static linking because they may be used by relocations (R_ARM_TLS_IE32) or by some other stuff like STT_GNU_IFUNC symbols. The problem is that now symbols are added in a declarative way by specifying in ExecutableWriter::addDefaultAtoms() override. At that stage, there's no way to determine if

Okay, I understood that you're proposing to add all undefined symbols during the resolution step, and not try to collect extra symbols during execution and then check if some undefines left (as I originally planned). This sounds reasonable as in any case we must have all undefines resolved in order to continue the linking process. Concerning the implementation, why not to add this virtual

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.