similar to: [PATCH] drm/nouveau: fix oops in display destructor with headless cards

Having the two modules separated causes various unneeded complications, including having to export symbols accessed between the modules. Make things simpler by compiling platform device support into nouveau.ko. Platform device support remains optional and is only compiled on Tegra. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- Vince, with this you won't have to export

Hi everyone I was using spline to interpolate single or two consecutive missing data points in time series. However, when it comes to longer gaps in the data the spline function generate new data for both my known and unknown data (see below). Aside from not understanding why this happens, I thought thought I might try function "aspline" in library (akima). However, I cannot install or

Add a platform driver for Nouveau devices declared using the device tree or platform data. This driver currently supports GK20A on Tegra platforms and is only compiled for these platforms if Nouveau is enabled. Nouveau will probe the chip type itself using the BOOT0 register, so all this driver really needs to do is to make sure the module is powered and its clocks active before calling

Hi there, I have searched what seems like everywhere and was unable to find a .NET wrapper so that I can use speex in VB. I did find a speex.NET.dll but this didn't seem to work on what I needed. I therefore decided I could just use DllImport within VB .NET and create my own unmanaged links to libspeex.dll. With the help of this partial c# code

This series adds support for probing platform devices on Nouveau, as well as the DT bindings for GK20A. It doesn't enable the GPU yet on Tegra boards since a few extra things need to be supported before that. This version is mostly identical to v2 but fixes an important issue: the drvdata must be set to the drm_device for sysfs to work, so the platform device structure now includes the

This series adds support for probing platform devices on Nouveau, as well as the DT bindings for GK20A. It doesn't enable the GPU yet on Tegra boards since a few extra things need to be supported before that. Thanks to the input received for v1, this version is more self-contained and shares less stuff between nouveau_drm and nouveau_platform. The major change is that nouveau_platform is now

While I had thought I'd tested this before, it looks like this one issue slipped by my original CRC patches. Basically, there seem to be a few rules we need to follow when sending CRC commands to the display controller: * CRCs cannot be both disabled and enabled for a single head in the same flush * If a head with CRC reporting enabled switches from one OR to another, there must be a

op 26-06-14 07:33, Alexandre Courbot schreef: > Add a platform driver for Nouveau devices declared using the device tree > or platform data. This driver currently supports GK20A on Tegra > platforms and is only compiled for these platforms if Nouveau is > enabled. > > Nouveau will probe the chip type itself using the BOOT0 register, so all > this driver really needs to do is

This patch series is the final (?) step towards the initial support of GK20A, allowing it to be probed and used (currently at a very slow speed, and for offscreen rendering only) on the Jetson TK1 and Venice 2 boards. The main piece if the first patch which adds platform devices probing support to Nouveau. There are probably lots of things that need to be discussed about it, e.g.: * The way the

Add a nouveau_drm_platform_probe() function that probes a Nouveau platform device and registers it using drm_platform_init(). Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drivers/gpu/drm/nouveau/core/engine/device/base.c | 34 ++++++++++++++++++++++ .../gpu/drm/nouveau/core/include/engine/device.h | 10 +++++++ drivers/gpu/drm/nouveau/nouveau_drm.c | 19

On Thu, Jan 15, 2015 at 4:29 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > Having the two modules separated causes various unneeded complications, > including having to export symbols accessed between the modules. Make > things simpler by compiling platform device support into nouveau.ko. > Platform device support remains optional and is only compiled on Tegra. >

Upcoming mobile Kepler GPUs (such as GK20A) use the platform bus instead of PCI to which Nouveau is tightly dependent. This patch allows Nouveau to handle platform devices by: - abstracting PCI-dependent functions that were typically used for resource querying and page mapping, - introducing a nv_device_is_pci() function that allows to make PCI-dependent code conditional, - providing a

Hi, I am running the latest kernel from Linus. Once yesterday and once today, I got a freeze of my machine. The first time, I could reboot with sysrq, but not the second one (completely unresponsive). The first time,, there was nothng in the logs, but today, I got some traces which I attach to this email. I can provide more details if needed ; the card is GeForce 9600 GT and the OS Debian Sid.

https://bugs.freedesktop.org/show_bug.cgi?id=79971 Priority: medium Bug ID: 79971 Assignee: nouveau at lists.freedesktop.org Summary: 3.15.0-11819-gc1fdb2d: oops QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: arekm at maven.pl Hardware: Other

Add a flag NVOBJ_FLAG_CREAT_EXCL, which will make sure that only 1 engctx will be created. This removes the need of having multiple Fixes the following lockdep splat: ============================================= [ INFO: possible recursive locking detected ] 3.8.0-rc6-ninja+ #1 Not tainted --------------------------------------------- modprobe/585 is trying to acquire lock:

On Mon, Feb 10, 2014 at 02:53:00PM +0900, Alexandre Courbot wrote: [...] > diff --git a/drivers/gpu/drm/nouveau/core/engine/device/base.c b/drivers/gpu/drm/nouveau/core/engine/device/base.c [...] > +resource_size_t > +nv_device_resource_start(struct nouveau_device *device, unsigned int bar) > +{ > + if (nv_device_is_pci(device)) { > + return pci_resource_start(device->pdev,

Hi Is there a way of finding out when or whether the wx object referenced in ruby is still alive? Here''s my problem # register that +wx_control+ should update on application events of type +event_type+ def add_subscriber(wx_control, app_event_type) @subscriptions[app_event_type].push(wx_control) end # later def broadcast(app_event) @subscriptions[app_event.type].each { |

Hi, After getting a bug report in Debian [1] about kde-window-decorator crashing in some destructors, I found several other similar reports in Ubuntu [2], KDE [3] (marked as invalid) and also on this mailing list several months ago [4] without any interesting reply. The backtrace is available in all these bugs, especially in [1]. I was about to open a bug at bugzilla.freedesktop.org but first: *

I have come across the issue where repeatedly creating and deleting an interpreter can cause incorrect external functions to be called. The issue had to do with the ManagedStatic map Functions in ExecutionEngine/Interpreter/ExternalFunctions.cpp. I was able to fix this by calling llvm_shutdown() when I delete the interpreter. Is it necessary to delete all ManagedStatic objects to delete

On Jul 1, 2009, at 8:28 AM, David Bertouille wrote: > Would it not be better to clear the Functions > map in the Interpreter desctructor since it data in it may no longer > be > valid? Probably. Patches welcome! --Owen -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2620 bytes Desc: not