search for: itarget

...gi; >> + /* ICFG */ >> + ext->icfg[0] = rank->icfg[0]; >> + ext->icfg[1] = rank->icfg[1]; >Can you use memcpy? OK. > >> + /* IPRIORITY */ >> + memcpy(ext->ipriority, rank->ipriority, sizeof(rank->ipriority)); >> + /* ITARGETS */ >> + memcpy(ext->itargets, rank->itargets, sizeof(rank->itargets)); >> + spin_unlock(&rank->lock); >> +} >> + >> +static void vgic_irq_rank_restore(struct vgic_irq_rank *rank, >> + struct vgic_rank *ext)...

From: Sylvain Gault <sylvain.gault at gmail.com> The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes above the current stack frame. This area can be used by a called function in order to avoid the overhead of modifying the stack pointer. The direct effect is that interrupt/event/signal handlers must not write to this area. In the UEFI calling convention,

...-print0 | xargs -r0 cp --target-dir=/home/sam/stuff/otherstuff/morestuff -- then xargs puts all of the files found by find after the -- Before I learned about this argument I used to do stuff like the "-i" and "-n" options find ./ -type file -mindepth 3 -print0 | xargs -r0 -iTARGET -n1 cp TARGET /home/sam/stuff/otherstuff/morestuff Which limits xargs to doing one file per invocation.

I'm just curious. The older klibc tarballs had a syslinux dir used to build a syslinux image with klibc. While I haven't used it, I was planning on messing with it at some point in the future. However, the syslinux stuff was removed from recent klibc images. Is there a technical reson for this, or would is still be acceptable to use the old Makefiles from that dir to build syslinux?

...for win32 platforms only +# +ifdef WIN32 +INSTALL_AUX_OPT = win32/syslinux.exe +else +INSTALL_AUX_OPT = +endif + +# # The BTARGET refers to objects that are derived from ldlinux.asm; we # like to keep those uniform for debugging reasons; however, distributors # want to recompile the installers (ITARGET). @@ -43,7 +52,7 @@ BOBJECTS = $(BTARGET) \ mbr/mbr_c.bin mbr/altmbr_c.bin mbr/gptmbr_c.bin \ mbr/mbr_f.bin mbr/altmbr_f.bin mbr/gptmbr_f.bin \ core/pxelinux.0 core/isolinux.bin core/isolinux-debug.bin \ - gpxe/gpxelinux.0 dos/syslinux.com win32/syslinux.exe \ + gpxe/gpxelinux.0 dos/syslinux....

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See