Displaying 20 results from an estimated 100 matches similar to: "[klibc 07/43] Eliminate unnecessary whitespace delta vs. Linus' tree"
2006 Jun 26
0
[klibc 06/43] Re-create ROOT_DEV, too many architectures need it.
ROOT_DEV carries a root device number communicated in an architecture-
specific way. We now pass it to kinit via the real-root-dev sysctl call.
Signed-off-by: H. Peter Anvin <hpa at zytor.com>
---
commit 0f5a324d655ad582246b6830843114d09835f593
tree fd3a96a69b6d74ee33dcd54a58b8666c02139a3a
parent f3e41698e540a7d39658d6590fde1379c0f5bab0
author H. Peter Anvin <hpa at zytor.com> Thu,
2005 Jan 11
17
[Fwd: Installing from distribution CDs]
Sorry, hit send instead of attach again. Rest of patches included.
--
Anthony Liguori
Samba, Linux/Windows Interoperability
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208
Tie Line: 678-1208
2010 Apr 27
2
gpllib write_sectors() patch
Here is a partial patch that I'm using to illustrate a few questions
that I have.
Looking at the gpllib write_sectors (com32/gpllib/disk/write.c) it
looks like the allocated
size is wrong; size is in sectors so we should adjust the alloc/memcpy
by size*SECTOR.
Also, comparing core/diskio.c it looks like the registers aren't even
setup right.
In the patch below I put an #if 0 around the
2015 Aug 07
1
[PATCH] com32: write_sectors fixes
Based on syslinux 6.03
Memory allocation and copy length should be SECTOR * size for sectors operation.
Signed-off-by: Robert <luyao-c at 360.cn>
diff --git a/com32/gpllib/disk/write.c b/com32/gpllib/disk/write.c
index d183ade..3c9edff 100644
--- a/com32/gpllib/disk/write.c
+++ b/com32/gpllib/disk/write.c
@@ -40,7 +40,7 @@ int write_sectors(const struct driveinfo *drive_info, const
2012 Jun 26
2
[GIT PULL] elflink bug fixes
Hi Peter,
Please pull the following changes.
Paulo, I had to revert your "pxe: resolve names via DNS from
protected-mode code" change because dns_resolv() is only implemented for
PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel
free to make the change again on top of the revert.
The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:
2006 Jun 26
0
[klibc 17/43] sparc32: transfer arch-specific options to /arch.cmd
Boot options which have been obtained in an architecture-specific
fashion have to be copied to /arch.cmd in the rootfs. This implements
that functionality for sparc32; the code is identical to sparc64 minus
the openprom support for obtaining nfsroot options.
Signed-off-by: H. Peter Anvin <hpa at zytor.com>
---
commit fc8c0c09f9dd5139dd8d797eaf9fe33962b6cd2c
tree
2006 Jun 26
0
[klibc 16/43] sparc64: transmit arch-specific options to kinit via /arch.cmd
Sparc64 has support for a bunch of architecture-specific options
taken from the PROM. Convert them to kernel command line form and
write the file /arch.cmd in the rootfs, which can be recovered by
kinit and processed. The kinit support has already been committed.
Signed-off-by: H. Peter Anvin <hpa at zytor.com>
---
commit c6e5c5a77681f5bf6f9fea55d031115e9f58ada6
tree
2010 Mar 20
2
[PATCH 4/4] btrfs-convert: split into convert/.
No material changes are made.
---
Makefile | 10 +-
convert.c => convert/convert.c | 803 +---------------------------------------
convert/convert.h | 76 ++++
convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++
4 files changed, 873 insertions(+), 807 deletions(-)
rename convert.c => convert/convert.c (74%)
create mode
2010 Sep 19
2
can't get write_sectors to work...
Hi,
Hopefully you someone can tell me what I'm doing wrong. First, the code. I
placed this at the bottom of the main loop in com32/modules/disk.c as a
simple test of writing to the disk:
printf(" Host bus: %s, Interface type: %s\n\n",
d->edd_params.host_bus_type, d->edd_params.interface_type);
zero_buf = calloc(1, d->edd_params.bytes_per_sector);
for(int
2006 Jun 26
0
[klibc 08/43] klibc: default initramfs content stored in usr/initramfs.default
Harcoding default content of initramfs in the gen_initramfs_list.sh
script seems ackward. Move it to a file named:
usr/initramfs.default
This also fixes a small bug when no arguments was passed to
CONFIG_INITRAMFS_SOURCE (-d was passed twice to the script)
Idea and bug report from: "H. Peter Anvin" <hpa at zytor.com>
Signed-off-by: Sam Ravnborg <sam at ravnborg.org>
2007 Aug 09
0
[PATCH] linux/x86: retrieve VESA capabilities in dom0
Subject: Obtain VESA capabilities and attributes of VESA mode
Also, move some more common code to dom0_init_screen_info().
This was tested on 2.6.22.1, and only made apply to 2.6.18 without
further testing.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-08-07/arch/i386/kernel/setup-xen.c
===================================================================
---
2014 Jun 24
0
[PATCH 1/2] x86, ia64: Move EFI_FB vga_default_device() initialization to pci_vga_fixup()
On Mon, 02 June 2014 Bruno Pr?mont <bonbons at linux-vserver.org> wrote:
> With commit b4aa0163056b ("efifb: Implement vga_default_device() (v2)")
> Matthew Garrett introduced a efifb vga_default_device() so that EFI
> systems that do not load shadow VBIOS or setup VGA get proper value for
> boot_vga PCI sysfs attribute on the corresponding PCI device.
>
> Xorg
2010 May 16
0
[PATCH v3 1/3] fbdev: allow passing more than one aperture for handoff
It removes a hack from nouveau code which had to detect which
region to pass to kick vesafb/efifb.
Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com>
Cc: Eric Anholt <eric at anholt.net>
Cc: Ben Skeggs <bskeggs at redhat.com>
Cc: Thomas Hellstrom <thellstrom at vmware.com>
Cc: Dave Airlie <airlied at redhat.com>
Cc: Peter Jones <pjones at redhat.com>
2010 Apr 12
1
[PATCHv2 1/2] fbdev: allow passing more than one aperture for handoff
It simplifies nouveau code by removal of detection which
region to pass to kick vesafb/efifb.
Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com>
Cc: Eric Anholt <eric at anholt.net>
Cc: Ben Skeggs <bskeggs at redhat.com>
Cc: Thomas Hellstrom <thellstrom at vmware.com>
Cc: Dave Airlie <airlied at redhat.com>
Cc: Peter Jones <pjones at redhat.com>
Cc:
2010 Jun 07
1
Building Nouveau DRM for a recent kernel (linux-2.6.35-rc1)
Hello.
I had some trouble building nouveau drm for linux-2.6.35-rc1.
I investigated a bit why it failed and noticed that the fb_info-structure
had changed slightly.
Since I do not have any previous knowledge of how the driver works, I'm not
certain if this is a proper fix, but it seems to work.
I'm curious if there's a better solution, or if my solution breaks in all
other cases.
2013 Aug 02
3
[PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
For "include/uapi/*", excluding "linux/" sub-directory, let all files'
macro prefix match the standard format, and give related stand comments
for their macro suffix.
The related standard format is:
"_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
Signed-off-by: Chen Gang
2013 Aug 02
3
[PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
For "include/uapi/*", excluding "linux/" sub-directory, let all files'
macro prefix match the standard format, and give related stand comments
for their macro suffix.
The related standard format is:
"_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
Signed-off-by: Chen Gang
2013 Aug 02
3
[PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
For "include/uapi/*", excluding "linux/" sub-directory, let all files'
macro prefix match the standard format, and give related stand comments
for their macro suffix.
The related standard format is:
"_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
Signed-off-by: Chen Gang
2015 Aug 13
3
[syslinux:master] efi/pxe: Reuse handle
Hi all,
I'm terribly sorry that I cannot follow emails in my gmail inbox,
since gmail is blocked by China govement, as many of you may have
already known.
I'm a HP employee in China and we are going through the splitting
process, so the blade server I was using were packed up and should be
moved into a new room.
I will try the latest source if possible.
Thank you very much for your works.
2013 Sep 26
0
Resource map sanity check fails after GRUB "keeps" the gfx mode
Hello!
I have spent some time on the issue. I'm not sure it's a nouveau bug.
I have a fix that changes arch/x86/kernel/sysfb_simplefb.c only.
GRUB actually uses graphic mode on my card. That mode is supported by
simplefb. However, the resource conflict happens regardless of whether
simplefb is enabled. It's sysfb_simplefb that causes it, a completely
different driver.
If GRUB