search for: match_data

I want to upload a file. And what I am confused about is...should I upload it using a separate table or just as another file in the form. If as a separate table then I am not able to save it on the system/ Or/ If not that, then how can i check for the extensions? Do reply. Thanks. -- Posted via http://www.ruby-forum.com/.

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

...oop to nvme_cq_notifier, and having it call nvme_process_sq, might fix the weird 1-minute delay. Paolo > void memory_region_add_eventfd(MemoryRegion *mr, > hwaddr addr, > unsigned size, > bool match_data, > uint64_t data, > EventNotifier *e) > > Could you help to explain what "match_data" and "data" mean? If match_data is true, the eventfd is only signalled if "data" is being written to memory....

...965610] clocksource: Switched to clocksource tsc [ 2.377965] random: dd urandom read with 19 bits of entropy available void memory_region_add_eventfd(MemoryRegion *mr, hwaddr addr, unsigned size, bool match_data, uint64_t data, EventNotifier *e) Could you help to explain what "match_data" and "data" mean? I use a real NVMe device as backend. -drive file=/dev/nvme0n1,format=raw,if=none,id=D22 \ -device nvme,drive=D22,serial...

Here are a few patches adding some missing functions in NvPlatformProbe, which iirc is being used as of xserver 1.13 First patch adds a nouveau_kernel_mode_enabled helper, similar to xf86-video-radeon Second and third use the function in Nv{Pci,Platform}Probe And last one ensures we can still use ZaphodHead and relative head positioning via xorg.conf The coding style may be a bit off, despite my

..., MODULEVENDORSTRING) == 0; + if (!ok) + xf86DrvMsg(-1, X_ERROR, + "NOUVEAU: glx module comes from incompatible vendor: \"%s\"\n", + d->vers->vendor); + + return ok; +} + static Bool NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, intptr_t match_data) @@ -209,6 +241,9 @@ NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, int chipset, ret; char *busid; + if (!glxIsCompatible()) + return FALSE; + if (!xf86LoaderCheckSymbol("DRICreatePCIBusID")) { xf86DrvMsg(-1, X_ERROR, "[drm] No DRICreatePCIBusID sym...

...BAR type. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- OK I added old_mmio (BTW: would be nice if ops were checked when region is inited) and now things work in userspace. However, when I add ioeventfd=on I get an assert: qemu/kvm-all.c:747: kvm_mem_ioeventfd_add: Assertion `match_data && section->size == 4' failed. How to reproduce: 1. apply patch 2. create virtio device with flags mmio=on,ioeventfd=on hw/virtio-pci.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++- hw/virtio-pci.h | 5 ++++ 2 files changed, 71 insertions(+), 2 deletions(-) d...

...BAR type. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- OK I added old_mmio (BTW: would be nice if ops were checked when region is inited) and now things work in userspace. However, when I add ioeventfd=on I get an assert: qemu/kvm-all.c:747: kvm_mem_ioeventfd_add: Assertion `match_data && section->size == 4' failed. How to reproduce: 1. apply patch 2. create virtio device with flags mmio=on,ioeventfd=on hw/virtio-pci.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++- hw/virtio-pci.h | 5 ++++ 2 files changed, 71 insertions(+), 2 deletions(-) d...

...include "dri2.h" #endif +#ifdef XORG_WAYLAND +#include <xf86Priv.h> +#include <xwayland.h> +#endif /* * Forward definitions for the functions that make up the driver. @@ -73,6 +77,28 @@ static Bool NVPciProbe ( DriverPtr drv, struct pci_device *dev, intptr_t match_data ); + +static Bool nouveau_driver_func(ScrnInfoPtr pScrn, + xorgDriverFuncOp op, + pointer ptr) +{ + xorgHWFlags *flag; + + switch (op) { + case GET_REQUIRED_HW_INTERFACES: + flag = (CARD32*)ptr; + (*flag) = 0; +#ifdef XORG_WAYLAND + if (xorgWayland) + (*flag) = HW_SKIP_CONSOLE; +#endif...

http://bugs.freedesktop.org/show_bug.cgi?id=16165 Summary: Multi-gpu Quadro NVS 400 (NV17a x2) fails to initialise xserver Product: xorg Version: 7.3 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

...unc); + + if (xmir_get_drm_fd(busid) < 0) { + xf86DrvMsg(-1, X_ERROR, "[XMir] GPU %s not handled by Mir\n", busid); + free(busid); + return FALSE; + } + free(busid); + return TRUE; +} + +static Bool NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, intptr_t match_data) { @@ -343,6 +362,9 @@ NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, }; ScrnInfoPtr pScrn = NULL; + if (xorgMir && !NVHasMirSupport(pci_dev)) + return FALSE; + if (!NVHasKMS(pci_dev)) return FALSE; @@ -367,6 +389,9 @@ NVPlatformProbe(DriverPtr driver,...

...;= 6 dri2.SwapLimitValidate = nouveau_dri2_swap_limit_validate; #endif diff --git a/src/nv_driver.c b/src/nv_driver.c index beef789..fb29ce5 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -72,6 +72,26 @@ static Bool NVPciProbe ( DriverPtr drv, struct pci_device *dev, intptr_t match_data ); + +static Bool nouveau_driver_func(ScrnInfoPtr pScrn, + xorgDriverFuncOp op, + pointer ptr) +{ + xorgHWFlags *flag; + + switch (op) { + case GET_REQUIRED_HW_INTERFACES: + flag = (CARD32*)ptr; + (*flag) = 0; + if (xorgWayland) + (*flag) = HW_SKIP_CONSOLE; + return TRUE; + default: +...