Displaying 20 results from an estimated 5000 matches similar to: "[PATCH] reenable pygrub build"
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2004 Feb 08
2
xeno-1.2.bk compilation question?
The system is Mandrake-9.1 Linux wih gcc-3.2.2.
I am trying to compile xenolinux-2.4.24 (with vanilla sources from
ftp.kernel.org for linux-2.4.24). The steps of
mkbuildtree
ARCH=xeno make menuconfig
ARCH=xeno make dep
produce no errors, but
ARCH=xeno make bzImage
results in following error messages.
Any pointers will be appreciated.
-ishwar
---
gcc -D__KERNEL__
2002 Nov 18
4
Problems with old hardware
Hi all
I have a Zenith N-Station (1997) P166 64 Mb of Ram
it has a Intel LANDesk Service Agent version 0.98i
it doesn't seem to be flashable
I have tried methode from http://syslinux.zytor.com/pxe.php
Each time I use ethereal to check the protocol
The behavior is quite strange :
I have the "Boot :" line the pxelinux is loading correctly
But when I ask my image pxe, I have dumps
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 May 25
4
Extending boot protocol & bzImage for paravirt_ops
Well, it seems to be about time to have this conversation again.
A rough overview of the previous thread and requirements is:
1. bzImage would not be a bare ELF file, but it would contain an ELF
header+file within it
2. We need some way to add extra ELF notes into that ELF file
3. We use a "paravirtualized" bootloader type, with some other field
to determine which
2007 May 25
4
Extending boot protocol & bzImage for paravirt_ops
Well, it seems to be about time to have this conversation again.
A rough overview of the previous thread and requirements is:
1. bzImage would not be a bare ELF file, but it would contain an ELF
header+file within it
2. We need some way to add extra ELF notes into that ELF file
3. We use a "paravirtualized" bootloader type, with some other field
to determine which
2007 Apr 18
43
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths
2007 Apr 18
43
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2017 Feb 07
2
Clang option to provide list of target-subarchs.
There are at least four clang frontends for offloading to accelerators:
1 Cuda clang 2 OpenMP 3 HCC and 4 OpenCL. These frontends will
want to embed object code for multiple offload targets into a single
application binary to provide portability across different subarchitectures
(e.g. sm_35, sm_50) and across different architectures (e.g nvptx64,amdgcn).
Problem: Different frontends
2013 Nov 01
17
[PATCH v2 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration
I''ve addressed all (I think/hope) of the review comments.
The main change is to expose the guest virtual platform (e.g. memory
layout and interrupt usage etc) to the toolstack via the public
interface. This is then used during FDT generation. I have just codified
the current defacto standard layout, it''s probably not the best layout
but any change can be a separate patch/series.
2007 Apr 18
8
Phone meeting about kernel virtualization hooks
I would like to host a phone meeting to discuss the plans for the xen
sub-architecture of x86. Hopefully Chris can share his vision and we
can agree on some next steps to getting this done and into the mainline
kernel. From my understanding, it would be good if the "To" list could
make it. If anyone believes others should attend, please let them
know.
Please let me know if you are
2007 Apr 18
8
Phone meeting about kernel virtualization hooks
I would like to host a phone meeting to discuss the plans for the xen
sub-architecture of x86. Hopefully Chris can share his vision and we
can agree on some next steps to getting this done and into the mainline
kernel. From my understanding, it would be good if the "To" list could
make it. If anyone believes others should attend, please let them
know.
Please let me know if you are
2013 Oct 24
5
Boot iPXE from syslinux/isolinux
Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14:
> Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56:
> > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35:
> > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote:
> > > > Hello everybody,
> > > >
> > > > iPXE builds
2013 Nov 19
23
[PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration
Biggest change is to switch the new DTB node to /xen-core-devices
instead of /xen at Stefano''s request.
I also dropped the few patches title HACK etc which weren''t supposed to
be there and fixed up some bits and pieces which folks commented on.
George, WRT the freeze I think this is functionality which we cannot
ship Xen 4.4 without. The impact is entirely constrained to the
2015 Feb 08
2
regression: relocatable kernels on a chromebook
On Sat, 7 Feb 2015, Ady via Syslinux wrote:
> Thank you for this meaningful report. Ideally, I would suggest
> performing a similar test (at least with the same kernel built with all
> the above "config_*=y" settings) with official pre-built Syslinux
> versions 4.07 and 3.86 (remembering that all Syslinux-related files,
> including c32 modules, if being used, shall