Displaying 8 results from an estimated 8 matches for "firmware_info".
2014 Feb 05
2
[PATCH] nouveau/video: make sure that firmware is present when checking caps
...screen.h
index 7f15d10..51e24fa 100644
--- a/src/gallium/drivers/nouveau/nouveau_screen.h
+++ b/src/gallium/drivers/nouveau/nouveau_screen.h
@@ -49,6 +49,11 @@ struct nouveau_screen {
boolean hint_buf_keep_sysmem_copy;
+ struct {
+ unsigned profiles_checked;
+ unsigned profiles_present;
+ } firmware_info;
+
#ifdef NOUVEAU_ENABLE_DRIVER_STATISTICS
union {
uint64_t v[29];
diff --git a/src/gallium/drivers/nouveau/nouveau_vp3_video.c b/src/gallium/drivers/nouveau/nouveau_vp3_video.c
index ff00b37..660a3d0 100644
--- a/src/gallium/drivers/nouveau/nouveau_vp3_video.c
+++ b/src/gallium/drivers...
2012 Sep 11
4
[PATCH] x86: retrieve keyboard shift status flags from BIOS
...6 +29,7 @@
#include <asm/edd.h>
#include <asm/mtrr.h>
#include <asm/io_apic.h>
+#include <asm/setup.h>
#include "cpu/mtrr/mtrr.h"
#include <xsm/xsm.h>
@@ -319,6 +320,18 @@ ret_t do_platform_op(XEN_GUEST_HANDLE(xe
u.firmware_info.u.efi_info) )
ret = -EFAULT;
break;
+ case XEN_FW_KBD_SHIFT_FLAGS:
+ ret = -ESRCH;
+ if ( op->u.firmware_info.index != 0 )
+ break;
+
+ op->u.firmware_info.u.kbd_shift_flags = bootsym(kbd_shift_flags);
+
+...
2011 Sep 14
1
[PATCH] xen/xsm: Compile error due to naming clash between XSM and EFI runtime
...if ( ret )
break;
diff -r 0312575dc35e xen/include/xsm/xsm.h
--- a/xen/include/xsm/xsm.h Thu Sep 08 15:13:06 2011 +0100
+++ b/xen/include/xsm/xsm.h Wed Sep 14 09:48:25 2011 -0400
@@ -132,7 +132,7 @@
int (*physinfo) (void);
int (*platform_quirk) (uint32_t);
int (*firmware_info) (void);
- int (*efi_runtime_call) (void);
+ int (*efi_call) (void);
int (*acpi_sleep) (void);
int (*change_freq) (void);
int (*getidletime) (void);
@@ -554,9 +554,9 @@
return xsm_call(firmware_info());
}
-static inline int xsm_efi_runtime_call (void)
+static inline int...
2007 Aug 30
0
[PATCH][Retry 1] 1/4: cpufreq/PowerNow! in Xen: Xen timer changes
...enpf_change_freq_t;
+DEFINE_XEN_GUEST_HANDLE(xenpf_change_freq_t);
+
struct xen_platform_op {
uint32_t cmd;
uint32_t interface_version; /* XENPF_INTERFACE_VERSION */
@@ -176,6 +187,7 @@ struct xen_platform_op {
struct xenpf_platform_quirk platform_quirk;
struct xenpf_firmware_info firmware_info;
struct xenpf_enter_acpi_sleep enter_acpi_sleep;
+ struct xenpf_change_freq change_freq;
uint8_t pad[128];
} u;
};
diff -r 256160ff19b7 xen/include/xen/sched.h
--- a/xen/include/xen/sched.h Thu Aug 16 13:27:59 2007 +0100...
2007 Dec 19
23
3.1.x and 3.2.x releases
Folks,
A new release candidate for 3.2.0 has just been checked into the
xen-unstable tree. It''s available from staging and will be in the main tree
when it has passed internal regression tests.
Meanwhile, in preparation for 3.1.3, please let me know if there are any
further patches from xen-unstable that should be backported into the 3.1
branch. You can pull the xen-3.1-testing.hg
2010 Nov 11
10
[PATCH 0/3] Xen Microcode update driver for 2.6.38
From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Hi all,
This series adds a new microcode driver for Xen. The Xen hypervisor
can deal with all the low-level details of doing a microcode update
(Intel vs AMD, doing all the physical CPUs present on the system,
current and future, etc), so all the driver has to do is make a
hypercall to upload the microcode into Xen.
This only
2007 Aug 29
39
[PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
...eturn 0;
+}
+
+core_initcall(cpufreq_time_setup);
#endif
/*
diff -r 05c22f282023 include/xen/interface/platform.h
--- a/include/xen/interface/platform.h Tue Aug 14 16:20:55 2007 +0100
+++ b/include/xen/interface/platform.h Tue Aug 28 14:55:24 2007 -0500
@@ -153,6 +153,17 @@ typedef struct xenpf_firmware_info xenpf
typedef struct xenpf_firmware_info xenpf_firmware_info_t;
DEFINE_XEN_GUEST_HANDLE(xenpf_firmware_info_t);
+#define XENPF_change_freq 52
+struct xenpf_change_freq {
+ /* IN variables */
+ struct vcpu_time_info *info; /* vcpu time info for changing vcpu */
+ uint32_t old; /*...
2008 Nov 13
69
[PATCH 00 of 38] xen: add more Xen dom0 support
Hi Ingo,
Here''s the chunk of patches to add Xen Dom0 support (it''s probably
worth creating a new xen/dom0 topic branch for it).
A dom0 Xen domain is basically the same as a normal domU domain, but
it has extra privileges to directly access hardware. There are two
issues to deal with:
- translating to and from the domain''s pseudo-physical addresses and
real machine