Displaying 20 results from an estimated 69 matches for "devrs".
Did you mean:
devfs
2017 Dec 12
1
[PATCHv2] virtio_mmio: fix devm cleanup
On Tue, Dec 12, 2017 at 10:26:24PM +0800, weiping zhang wrote:
> 2017-12-12 21:45 GMT+08:00 Mark Rutland <mark.rutland at arm.com>:
> Hi Mark,
Hi,
> thanks your patch, I dig into these three devm_xxx funciton,
> all of them represented by a struct devres as following,
>
> struct devres_node {
> struct list_head entry;
> dr_release_t
2017 Dec 12
1
[PATCHv2] virtio_mmio: fix devm cleanup
On Tue, Dec 12, 2017 at 10:26:24PM +0800, weiping zhang wrote:
> 2017-12-12 21:45 GMT+08:00 Mark Rutland <mark.rutland at arm.com>:
> Hi Mark,
Hi,
> thanks your patch, I dig into these three devm_xxx funciton,
> all of them represented by a struct devres as following,
>
> struct devres_node {
> struct list_head entry;
> dr_release_t
2009 Aug 19
4
Confidence interval on parameters from optim function
Hi everyone,
I have two questions:
I would like to get confidence intervals on the coefficients derived
from the optim() function.
I apply optim() to a given function f
> res <-
optim(c(0.08,0.04,1.),f,NULL,method="L-BFGS-B",lower=c(0.,0.,0.))
And I would like to get the p-value and confidence intervals associated
with
> res$par
My second question deals with error message. I
2020 Nov 06
0
[PATCH 2/3] drm/nouveau: manage nouveau_drm lifetime with devres
Make use of the devm_drm_dev_alloc() API to bind the lifetime of
nouveau_drm structure to the drm_device. This is important because a
reference to nouveau_drm is accessible from drm_device, which is
provided to a number of DRM layer callbacks that can run after the
deallocation of nouveau_drm currently occurs.
Signed-off-by: Jeremy Cline <jcline at redhat.com>
---
2017 Dec 12
4
[PATCHv2] virtio_mmio: fix devm cleanup
Recent rework of the virtio_mmio probe/remove paths balanced a
devm_ioremap() with an iounmap() rather than its devm variant. This ends
up corrupting the devm datastructures, and results in the following
boot-time splat on arm64 under QEMU 2.9.0:
[ 3.450397] ------------[ cut here ]------------
[ 3.453822] Trying to vfree() nonexistent vm area (00000000c05b4844)
[ 3.460534] WARNING: CPU:
2017 Dec 12
4
[PATCHv2] virtio_mmio: fix devm cleanup
Recent rework of the virtio_mmio probe/remove paths balanced a
devm_ioremap() with an iounmap() rather than its devm variant. This ends
up corrupting the devm datastructures, and results in the following
boot-time splat on arm64 under QEMU 2.9.0:
[ 3.450397] ------------[ cut here ]------------
[ 3.453822] Trying to vfree() nonexistent vm area (00000000c05b4844)
[ 3.460534] WARNING: CPU:
2008 Jan 18
2
[PATCH 2/3] Make IRQ handlers typesafe.
This patch lets interrupt handler functions have their natural type
(ie. exactly match the data pointer type); for transition it allows
the old irq_handler_t type as well.
To do this it uses a gcc extension, cast-to-union, which allows a type
to be cast to any type within the union. When used in a wrapper
macro, it's a simple way of allowing one of several types.
(Some drivers now need to
2008 Jan 18
2
[PATCH 2/3] Make IRQ handlers typesafe.
This patch lets interrupt handler functions have their natural type
(ie. exactly match the data pointer type); for transition it allows
the old irq_handler_t type as well.
To do this it uses a gcc extension, cast-to-union, which allows a type
to be cast to any type within the union. When used in a wrapper
macro, it's a simple way of allowing one of several types.
(Some drivers now need to
2024 Jul 28
1
[PATCH v2 02/37] drm/nouveau: handle pci/tegra drm_dev_{alloc, register} from common code
On Sun, Jul 28, 2024 at 11:34:14PM +0200, Danilo Krummrich wrote:
> On Sun, Jul 28, 2024 at 03:13:08PM -0300, Jason Gunthorpe wrote:
> I think we're on the same page with all that. As clarified in [1], that's not a
> big concern, I was referring to the changes required to integrate the auxbus
> stuff.
Well, I see this thread having the realization that things are not
setup
2008 Mar 13
2
Plot contour over filled contour
Dear R-users,
I haven't found a way in the searchable archive to overplot a contour
(lines) over a surface.
I have a (n,m) matrix that represents sea surface temperature that I
have plotted using image.plot(), filled.contour() or image(). I would
like to overplot this image with some contour lines of mixed layer depth
values(same size matrix). How can I do this?
Any help is appreciated,
2024 Jul 28
1
[PATCH v2 02/37] drm/nouveau: handle pci/tegra drm_dev_{alloc, register} from common code
On Sun, Jul 28, 2024 at 03:13:08PM -0300, Jason Gunthorpe wrote:
> On Fri, Jul 26, 2024 at 11:07:19PM +1000, Ben Skeggs wrote:
>
> > > Right, I think I took that too literally.
> > >
> > > The lifetime of the DRM device (or more precisely one of its references) is
> > > bound to the binding between the parent device and its corresponding driver.
>
2005 Mar 22
2
Speex hardware requirements?
...mode that resembles "bytecode" (a 32-bit instruction
is executed using a 16-bit instruction). I got a feeling that the GBA
would need a FPU.
For more information on the GBA visit this info page:
http://www.cs.rit.edu/~tjh8300/CowBite/CowBiteSpec.htm
and this development page: http://www.devrs.com/gba/
Best Regards
P?r
> Hi,
>
> Decoding Speex is really cheap (about 10x faster than encoding). I
> expect most PDAs (no FPU) will be able to decode Speex at 16 kHz in
> real-time. I have no idea what CPU the Gameboy advance uses, so I can't
> say.
>
> Jean-...
2019 Jun 13
2
dev_pagemap related cleanups
On 2019-06-13 12:27 p.m., Dan Williams wrote:
> On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig <hch at lst.de> wrote:
>>
>> Hi Dan, Jérôme and Jason,
>>
>> below is a series that cleans up the dev_pagemap interface so that
>> it is more easily usable, which removes the need to wrap it in hmm
>> and thus allowing to kill a lot of code
>>
2020 Nov 06
2
[PATCH 2/3] drm/nouveau: manage nouveau_drm lifetime with devres
On Fri, Nov 6, 2020 at 3:17 AM Jeremy Cline <jcline at redhat.com> wrote:
>
> Make use of the devm_drm_dev_alloc() API to bind the lifetime of
> nouveau_drm structure to the drm_device. This is important because a
> reference to nouveau_drm is accessible from drm_device, which is
> provided to a number of DRM layer callbacks that can run after the
> deallocation of
2023 Jul 03
0
[PATCH] virtio-mmio: don't break lifecycle of vm_dev
On Thu, 29 Jun 2023 14:05:26 +0200, Wolfram Sang <wsa+renesas at sang-engineering.com> wrote:
> vm_dev has a separate lifecycle because it has a 'struct device'
> embedded. Thus, having a release callback for it is correct.
>
> Allocating the vm_dev struct with devres totally breaks this protection,
device? or driver?
And why?
> though. Instead of waiting for the
2024 Jun 07
1
[RFC PATCH 7/8] rust: add firmware abstractions
On Fri, Jun 07, 2024 at 02:36:50PM +0200, Greg KH wrote:
> Anyway, that's all hand-wavy right now, sorry, to get back to the point
> here, again, let's take this, which will allow the firmware bindings to
> be resubmitted and hopefully accepted, and we can move forward from
> there to "real" things like a USB or PCI or even platform device and
> driver binding
2016 Nov 25
1
[PATCH] virtio_mmio: Set dev.release() to avoid warning
I think not. In virtio_pci_common, vp_dev is allocated by kzalloc so a
kfree is needed. Here vm_dev is allocated by devm_kmalloc which is
"automatically freed on driver detach" from the comment
(drivers/base/devres.c:769).
On Thu, Nov 24, 2016 at 6:37 PM, Jason Wang <jasowang at redhat.com> wrote:
>
>
> On 2016?11?24? 08:31, Yuan Liu wrote:
>
>> From: Yuan Liu
2016 Nov 25
1
[PATCH] virtio_mmio: Set dev.release() to avoid warning
I think not. In virtio_pci_common, vp_dev is allocated by kzalloc so a
kfree is needed. Here vm_dev is allocated by devm_kmalloc which is
"automatically freed on driver detach" from the comment
(drivers/base/devres.c:769).
On Thu, Nov 24, 2016 at 6:37 PM, Jason Wang <jasowang at redhat.com> wrote:
>
>
> On 2016?11?24? 08:31, Yuan Liu wrote:
>
>> From: Yuan Liu
2024 Jun 09
0
[RFC PATCH 3/8] rust: drm: Add Device and Driver abstractions
Hi Lina,
Welcome back!
On Sun, Jun 09, 2024 at 02:15:57PM +0900, Asahi Lina wrote:
>
>
> On 5/22/24 6:23 AM, Rob Herring wrote:
> > On Mon, May 20, 2024 at 07:20:50PM +0200, Danilo Krummrich wrote:
> >> From: Asahi Lina <lina at asahilina.net>
> > This is missing an entry for DRIVER_GEM_GPUVA. And some others perhaps.
> > I suppose some are legacy
2020 Feb 07
1
[PATCH 2/6] drm: Add drm_simple_encoder_{init,create}()
Den 07.02.2020 09.41, skrev Thomas Zimmermann:
> The simple-encoder helpers initialize an encoder with an empty
> implementation. This covers the requirements of most of the existing
> DRM drivers. A call to drm_simple_encoder_create() allocates and
> initializes an encoder instance, a call to drm_simple_encoder_init()
> initializes a pre-allocated instance.
>
>