Displaying 14 results from an estimated 14 matches for "kernel_end".
Did you mean:
kernel_env
2006 Jun 26
0
[klibc 07/43] Eliminate unnecessary whitespace delta vs. Linus' tree
...screen_info = SCREEN_INFO;
edid_info = EDID_INFO;
diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c
index 6d4f025..003667e 100644
--- a/arch/x86_64/kernel/setup.c
+++ b/arch/x86_64/kernel/setup.c
@@ -599,7 +599,7 @@ void __init setup_arch(char **cmdline_p)
{
unsigned long kernel_end;
- ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV);
+ ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV);
screen_info = SCREEN_INFO;
edid_info = EDID_INFO;
saved_video_mode = SAVED_VIDEO_MODE;
2006 Jun 26
0
[klibc 06/43] Re-create ROOT_DEV, too many architectures need it.
...screen_info = SCREEN_INFO;
edid_info = EDID_INFO;
diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c
index cadbe33..6d4f025 100644
--- a/arch/x86_64/kernel/setup.c
+++ b/arch/x86_64/kernel/setup.c
@@ -599,6 +599,7 @@ void __init setup_arch(char **cmdline_p)
{
unsigned long kernel_end;
+ ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV);
screen_info = SCREEN_INFO;
edid_info = EDID_INFO;
saved_video_mode = SAVED_VIDEO_MODE;
diff --git a/init/initramfs.c b/init/initramfs.c
index 0cbd783..7ea4127 100644
--- a/init/initramfs.c
+++ b/init/initramfs.c
@@ -10,10 +10,6 @@ #include <l...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
.... / 512;
+
+ _ = ASSERT(_end <= 0x8000, "Setup too big!");
+ _ = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
+
+ .notes : {
+ notes = .;
+ *(.note*)
+ notes_end = .;
+ }
+ notes_size = notes_end - notes;
+
+ .kernel : {
+ kernel = .;
+ *(.kernel)
+ kernel_end = .;
+ kernel_size = kernel_end - kernel;
+ kernel_size_para = (kernel_size + 15) / 16;
+ }
}
===================================================================
--- a/arch/i386/boot/tools/.gitignore
+++ /dev/null
@@ -1,1 +0,0 @@
-build
===========================================================...
2007 Jun 01
2
another RFC patch: bzImage with ELF payload
.... / 512;
+
+ _ = ASSERT(_end <= 0x8000, "Setup too big!");
+ _ = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
+
+ .notes : {
+ notes = .;
+ *(.note*)
+ notes_end = .;
+ }
+ notes_size = notes_end - notes;
+
+ .kernel : {
+ kernel = .;
+ *(.kernel)
+ kernel_end = .;
+ kernel_size = kernel_end - kernel;
+ kernel_size_para = (kernel_size + 15) / 16;
+ }
}
===================================================================
--- a/arch/i386/boot/tools/.gitignore
+++ /dev/null
@@ -1,1 +0,0 @@
-build
===========================================================...
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
.... / 512;
+
+ _ = ASSERT(_end <= 0x8000, "Setup too big!");
+ _ = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
+
+ .notes : {
+ notes = .;
+ *(.note*)
+ notes_end = .;
+ }
+ notes_size = notes_end - notes;
+
+ .kernel : {
+ kernel = .;
+ *(.kernel)
+ kernel_end = .;
+ kernel_size = kernel_end - kernel;
+ kernel_size_para = (kernel_size + 15) / 16;
+ }
}
diff -r b9a73007e203 arch/i386/boot/tools/.gitignore
--- a/arch/i386/boot/tools/.gitignore Wed May 30 18:41:32 2007 -0700
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-build
diff -r b9a7...
2007 May 31
1
[patch rfc wip] first cut of ELF bzImage
.... / 512;
+
+ _ = ASSERT(_end <= 0x8000, "Setup too big!");
+ _ = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
+
+ .notes : {
+ notes = .;
+ *(.note*)
+ notes_end = .;
+ }
+ notes_size = notes_end - notes;
+
+ .kernel : {
+ kernel = .;
+ *(.kernel)
+ kernel_end = .;
+ kernel_size = kernel_end - kernel;
+ kernel_size_para = (kernel_size + 15) / 16;
+ }
}
diff -r b9a73007e203 arch/i386/boot/tools/.gitignore
--- a/arch/i386/boot/tools/.gitignore Wed May 30 18:41:32 2007 -0700
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-build
diff -r b9a7...
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
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
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 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