similar to: VGABIOS patches

I ran into this when I was reviewing what was outstanding to get NetWare to run fully virtualized. The BIOS emulator code has the segment and offset backward in the returned buffer for the int 13h, fn 48h BIOS call. BTW: This is fixed in current Bochs emulator upstream code. Signed-off-by: Bruce Rogers <brogers@novell.com> diff -r 59b8768d0d0d tools/firmware/rombios/rombios.c ---

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround

Hi, (This is a recend, as the original post was refused by the CentOS moderators due to the size of the X-log file) I''ve just installed the CentOS 4.0 RC1 for x86_64 -set on my new Nforce4-based system with a PCIe GF6600-card. When installing, the screen becomes garbled as the system enters X mode, but installing with ''linux text'' works, until the system reboots and

This patches add support for dynamic sectors to GPT MBR code. First 3 patches are trick and optimizations to gain some space for the forth patch. I have a modified version of SeaBIOS, some code and some script o test it I'll send on a different mail.

From: Frediano Ziglio <frediano.ziglio@citrix.com> Split coverage informations extracted from xencov utility. This script accept coverage blob either as file or from input and extract into files compatible with gcc format (gcda). Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com> --- tools/misc/Makefile | 2 +- tools/misc/xencov_split | 191

Check if some pointers are not NULL due to read errors or other problems Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- core/fs/ext2/ext2.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/core/fs/ext2/ext2.c b/core/fs/ext2/ext2.c index bddde8d..8f0f2a4 100644 --- a/core/fs/ext2/ext2.c +++ b/core/fs/ext2/ext2.c @@ -139,6 +139,8 @@

These patch update Windows generation ID support on ACPI. First patch mainly update to new specifications while second one introduce again the device in ACPI table. Frediano Ziglio (2): genid: Update Windows generation ID genid: Introduce again Windows generation ID device docs/misc/xenstore-paths.markdown | 6 ++++ tools/firmware/hvmloader/acpi/build.c | 49

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- com32/mboot/mboot.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index 35450e0..10e6701 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -198,7 +198,7 @@ int main(int argc, char *argv[]) } if (init_map()) - return 1; /* Failed to

Hi, time ago I started doing support for 4k sector disk for syslinux. Patches worked for my cases (ext) and did not introduced regression problems with normal disks. Now I would like to update these patches and upstream them. It's not clear however which is the branch I should use to rebase these patches. Previous patches was against syslinux-4.06 but now there is syslinux-5.01 (elflink)

On 12/16/2013 05:18 AM, Frediano Ziglio wrote: > > Surely should apply to 4.xx where they was developed but I think I send > them for 5.xx. mbr part of patches was merged time ago. > Unfortunately I had no time to update other patches. If I remember there > was a problem on the way ADV was implemented (using the same sector). > > Unfortunately my company business required to

I noted a possible problem restoring a machine. In xc_domain_restore (xc_domain_restore.c) if it''s not the last checkpoint we set O_NONBLOCK flag (search for fcntl) that we can call pagebuf_get or just load other pages (see following "goto loadpages;" line). Now we could ending up calling xc_tmem_restore/xc_tmem_restore_extra (xc_tmem.c) which call read_extract (xc_private.c)

Hi, I'm trying to get syslinux (extlinux actually) work with 4kb disks. I got a bios with 4kb support but seems that extlinux does not work at all. In extlinux/main.c SECTOR_SIZE and SECTOR_SHIFT are constants to 512 bytes and also there are a lot of checks in different places (like in syslinux_check_bootsect). Currently I'm trying it to work using GPT and an ext3 partition. Anybody

qxl has two modes: "native" (used by the drm driver) and "vga" (vga compatibility mode, typically used for boot display and firmware framebuffers). Accessing any vga ioport will switch the qxl device into vga mode. The qxl driver never does that, but other drivers accessing vga ports can trigger that too and therefore disturb qxl operation. So aquire the legacy vga ioports

Hi all! It's my first message on this ML. I just installed Fedora Core and I had a small problem... kernel + initrd do not fit in a 1.44 disks... I looked at documentation and at code (kernel.inc) and I saw that syslinux - load kernel - load initrd - boot kernel So perhaps a small workaround for above problem should be to add a configuration to initrd (ie initrd=@initrd.img) to just ask to

Updated set of patches for coverage. Changes: - change copyright lines - use gcov: instead of cover: in commit comment - use #ifdef in xen/common/sysctl.c instead of dummy inline function - added base documentation in docs/misc - added -h option to xencov

Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >> used in a driver. >> > As far as I can see by your second patch QXL is just using exported > (that is not internal) functions. > Not that the idea of making them internal is bad but this comment is > a wrong statement. See the history of

Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >> used in a driver. >> > As far as I can see by your second patch QXL is just using exported > (that is not internal) functions. > Not that the idea of making them internal is bad but this comment is > a wrong statement. See the history of

> > On 05.09.19 15:34, Jaak Ristioja wrote: > > On 05.09.19 10:14, Gerd Hoffmann wrote: > >> On Tue, Aug 06, 2019 at 09:00:10PM +0300, Jaak Ristioja wrote: > >>> Hello! > >>> > >>> I'm writing to report a crash in the QXL / DRM code in the Linux kernel. > >>> I originally filed the issue on LaunchPad and more details can be

Am 30.09.19 um 11:51 schrieb Frediano Ziglio: >> Am 27.09.19 um 18:31 schrieb Frediano Ziglio: >>>> The ttm_mem_io_* functions are actually internal to TTM and shouldn't be >>>> used in a driver. >>>> >>> As far as I can see by your second patch QXL is just using exported >>> (that is not internal) functions. >>> Not that the