similar to: RE: [Xen-staging] [xen-unstable] hvm rombios: Fix int15, func 0x86 (udelay).

gk20a_ibus_init_ibus_ring() can be called from gk20a_ibus_intr(), in non-interruptible context. Replace use of usleep_range() with udelay(). Reported-by: Thierry Reding <treding at nvidia.com> Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drm/nouveau/nvkm/subdev/ibus/gk20a.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Not respecting udelay causes problems with any virtual hardware that is passed through to real hardware. This can be noticed by any device that interacts with the real world in real time - like AP startup, which takes real time. Or keyboard LEDs, which should blink in real-time. Or floppy drives, but only when passed through to a real floppy controller on OSes which can't sufficiently

Not respecting udelay causes problems with any virtual hardware that is passed through to real hardware. This can be noticed by any device that interacts with the real world in real time - like AP startup, which takes real time. Or keyboard LEDs, which should blink in real-time. Or floppy drives, but only when passed through to a real floppy controller on OSes which can't sufficiently

Hi, We found a bug that rombios cannot get the correct BDF during rom_scan. This patch fixes rombios to get the BDF for calling INIT function. I''m sorry for the inconvenience. m(__)m Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Signed-off-by: Kouya Shimura <kouya@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________

HI: I try to let guest os to DHA(directly hardware acceess) physical network card, and also want to let rombios (which is not DHA) to initialize networks card''s pnp option Rom(the pnp option rom is DHA). however , I find the init program(offset by 3 from 55aa header signature) within option rom can not run properly ---- it cause stact underflow . and when retf form option rom ,system

A "main" function is defined in Xen-3.1.0-source/tools/firmware/hvmloader/hvmloader.c. In this main function, rombios, vgabios and vmxassist are copied to specified address, with following commands memcpy((void *)ROMBIOS_PHYSICAL_ADDRESS, rombios, rombios_sz); ... memcpy((void *)ETHERBOOT_PHYSICAL_ADDRESS, etherboot, sizeof(etherboot)); .... But after searching the whole

Attached simple patch modifies the rombios and hvmloader Makefiles to default to an 8-way bochs bios for the hvmloader. Is there a reason to not define the mp config table by default for >1 processors (8), in the repository? Seems like using the hvm guest config file can the methodolody to describe a UP guest regardless of the mptables. Defaulting the rombios to MP would allow users to

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

I have set up a RHEL 5.7 PXE server and trying to get a WinPE ISO to work. Currently PXE seems to handle the image properly but the process stops after Loading boot sector... booting... Full list of what is going on. Ramdisk at 0x72b9c00, length 0x0a680000 command line: iso initrd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size

memdisk fails to boot HD image, if the system does not have an HD. Has any seen this? Is there a solution? memdisk output: Disk is hard disk, 9216 K, C/H/S = 9/64/32 Total size needed = 2063 bytes, allocating 3K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d000 INT 13 08: Failure, assuming this is the only driveold: int13 = f000799a int15 = f000f859 new: int13 = 9d000008 int15

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

hi there. I'm trying to boot several OSes floppy images from a cdrom via memdisk. Actually, Linux and FreeBSD boots fine, but, while i'm using the same method, I couldn't get into booting netbsd nor openbsd. The boot process seems to hang up, in those two cases, when the second stage native bootloader try to load the kernel (i'm not absolutely sure about this). The native first

I am getting the following build break on changeset 13662. I am compiling on x86_64 SLES10 with gcc 4.1.0. Is there a fix for this? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA make[1]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware'' make[2]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware/rombios'' gcc -o biossums

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

I need some help with the following: My system hangs while booting from a CD using?SysLinux?(2.08).? I think that the?driver?hooks into the INT13 and INT15 handlers, writing their new handler hook into the Extended BIOS Data Area (EBDA) used by Phoenix BIOS for BIOS data information.? This area is?used and modified during legacy USB SMI's. I think that the hang happens because the new handler

Hi everybody. Hardware: Several computers with Asus P/I-P55t2P4S motherboard, CPU Pentium MMX and K6-2/3, 128 to 384 MB RAM, Award 4.51PG Bios, Hard disks from 8 GB to 123.5 GB Realtek 8139D based NICs with PXE Boot-Proms PXELINUX 2.06 / MEMDISK 2.06: - fails to boot Compaq PC-DOS 3.31 PXELINUX 2.08 - succeeds to boot Compaq PC-DOS 3.31 with 0, 1, 2 and 3 hdds installed in

Hi, just tried memdisk - it works, even with token-ring network cards! I've some problems with dos 6.22 on one machine, though. This one doesn't have a floppy controller (e.g. linux reports that it didn't find any controller). The Dos 6.22 boot disk is loaded, then the boot sector is started and tells me that it can't load the system (German message: 'Kein System oder

I am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000