search for: totevent

On Thu, Feb 16, 2023 at 01:03:02PM +0100, Thomas Zimmermann wrote: > Hi, > > thanks for taking a look at the patches. > > Am 16.02.23 um 12:33 schrieb Gerd Hoffmann: > > On Wed, Feb 15, 2023 at 05:15:17PM +0100, Thomas Zimmermann wrote: > >> Set the VGA bit for unblanking with macro constants instead of magic > >> values. No functional changes. > >

Hi Am 27.02.23 um 19:15 schrieb Rob Clark: > On Mon, Feb 27, 2023 at 9:57 AM Dmitry Osipenko > <dmitry.osipenko at collabora.com> wrote: >> >> On 2/27/23 20:38, Rob Clark wrote: >> ... >>> + if (IS_ENABLED(CONFIG_DRM_VIRTIO_GPU_KMS)) { >>> + /* get display info */ >>> + virtio_cread_le(vgdev->vdev, struct

Hi, thanks for taking a look at the patches. Am 16.02.23 um 12:33 schrieb Gerd Hoffmann: > On Wed, Feb 15, 2023 at 05:15:17PM +0100, Thomas Zimmermann wrote: >> Set the VGA bit for unblanking with macro constants instead of magic >> values. No functional changes. > > blank/unblank should work simliar to bochs (see commit 250e743915d4), > that is maybe a nice thing to add

Hi Am 16.02.23 um 13:52 schrieb Ville Syrj?l?: > On Thu, Feb 16, 2023 at 01:03:02PM +0100, Thomas Zimmermann wrote: >> Hi, >> >> thanks for taking a look at the patches. >> >> Am 16.02.23 um 12:33 schrieb Gerd Hoffmann: >>> On Wed, Feb 15, 2023 at 05:15:17PM +0100, Thomas Zimmermann wrote: >>>> Set the VGA bit for unblanking with macro

Hi Am 13.01.25 um 04:53 schrieb Andy Yan: [...] >> Thanks for taking a look. That NV-related code at [0] is a 'somewhat >> non-idiomatic use' of the UAPI. The dumb-buffer interface really just >> supports a single plane. The fix would be a new ioctl that takes a DRM >> 4cc constant and returns a buffer handle/pitch/size for each plane. But >> that's

...terestingly, my problem seems to be solved by writing a FORTRAN wrapper for the Fortran code! (As long as the check doesn't get smarter...). This is the relevant part of my Fortran code: ----------------------------------------------------------- subroutine gmlfun(what, & totevent, totrs, ns, & antrs, antevents, size, & totsize, eventset, riskset, & nn, antcov, covar, offset, & beta, gamma, & loglik, h1, h2, h11, h21, h22, & score) ...... call gmlfun1(what, & totevent, t...

Hi, On 16/01/2025 10:09, Thomas Zimmermann wrote: > Hi > > > Am 15.01.25 um 15:20 schrieb Tomi Valkeinen: > [...] >> >> My point is that we have the current UAPI, and we have userspace using >> it, but we don't have clear rules what the ioctl does with specific >> parameters, and we don't document how it has to be used. >> >> Perhaps

Hi Am 12.08.24 um 12:18 schrieb Daniel Vetter: > On Mon, Aug 12, 2024 at 11:23:44AM +0200, Daniel Vetter wrote: >> On Mon, Aug 12, 2024 at 10:28:22AM +0200, Thomas Zimmermann wrote: >>> Amdgpu and nouveau call vga_switcheroo_process_delayed_switch() from >>> their lastclose callbacks. Call it from drm_lastclose(), so that the >>> driver functions can finally be

On Mon, Aug 12, 2024 at 12:41:39PM +0200, Thomas Zimmermann wrote: > Hi > > Am 12.08.24 um 12:18 schrieb Daniel Vetter: > > On Mon, Aug 12, 2024 at 11:23:44AM +0200, Daniel Vetter wrote: > > > On Mon, Aug 12, 2024 at 10:28:22AM +0200, Thomas Zimmermann wrote: > > > > Amdgpu and nouveau call vga_switcheroo_process_delayed_switch() from > > > > their

Hello Thomas, On 1/10/23 13:35, Thomas Zimmermann wrote: > Commit 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") > converted nouveau to generic fbdev emulation. The driver's internal > implementation later got accidentally restored during a merge commit. > Remove the file from the driver. No functional changes. > > v2: > * point Fixes tag to

On Wed, Feb 15, 2023 at 05:15:17PM +0100, Thomas Zimmermann wrote: > Set the VGA bit for unblanking with macro constants instead of magic > values. No functional changes. blank/unblank should work simliar to bochs (see commit 250e743915d4), that is maybe a nice thing to add of you modernize the driver anyway. take care, Gerd

I forgot this change. Am 08.01.23 um 22:04 schrieb Dmitry Osipenko: > Add unlocked variants of drm_gem_un/pin() functions. These new helpers > will take care of GEM dma-reservation locking for DRM drivers. > > VirtIO-GPU driver will use these helpers to pin shmem framebuffers, > preventing them from eviction during scanout. > > Signed-off-by: Dmitry Osipenko

Hi Am 17.03.23 um 13:39 schrieb Javier Martinez Canillas: > Thomas Zimmermann <tzimmermann at suse.de> writes: > >> Consolidate all handling of CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM by >> making the module parameter optional in drm_fb_helper.c. >> >> Without the config option, modules can set smem_start in struct >> fb_info for internal usage, but not export

Hi, On Linux, glibc is using a 32bit time_t for wtmp and similar structs even on a 64bit system: https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/ https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/ Since the glibc developers stated that they don't plan to solve the problem in glibc, but think that this interfaces are legacy and should be removed from glibc (like musl libc, which does not

On 8/12/24 10:28 AM, Thomas Zimmermann wrote: > Replace the call to drm_fb_helper_output_poll_changed() with a call > to drm_client_dev_hotplug(). It is equivalent in functionality, but > uses the DRM client infrastructure. > > v2: > - fix commit description > > Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> > Reviewed-by: Daniel Vetter

Hi Am 12.08.24 um 14:17 schrieb Danilo Krummrich: > On 8/12/24 10:28 AM, Thomas Zimmermann wrote: >> Replace the call to drm_fb_helper_output_poll_changed() with a call >> to drm_client_dev_hotplug(). It is equivalent in functionality, but >> uses the DRM client infrastructure. >> >> v2: >> - fix commit description >> >> Signed-off-by: Thomas

On Mon, Sep 9, 2024 at 7:37?AM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Call drm_client_setup() to run the kernel's default client setup > for DRM. Set fbdev_probe in struct drm_driver, so that the client > setup can start the common fbdev client. > > Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> > Cc: Zack Rusin <zack.rusin at

Hi Am 16.01.25 um 11:03 schrieb Tomi Valkeinen: [...] > Aligning video= and dumb buffers almost sounds like going backwards. > video= parameter is bad, Who told you that? Video= is still the way to specify an initial display mode to the kernel and it will remain so. Of course, it is better to auto-detect settings, but that's for a different use case. Best regards Thomas >

Hi, On 20/01/2025 09:49, Thomas Zimmermann wrote: > Hi > > > Am 16.01.25 um 11:03 schrieb Tomi Valkeinen: > [...] >> Aligning video= and dumb buffers almost sounds like going backwards. >> video= parameter is bad, > > Who told you that? Video= is still the way to specify an initial display > mode to the kernel and it will remain so. You did =). "It

On Mon, Feb 27, 2023 at 9:57 AM Dmitry Osipenko <dmitry.osipenko at collabora.com> wrote: > > On 2/27/23 20:38, Rob Clark wrote: > ... > > + if (IS_ENABLED(CONFIG_DRM_VIRTIO_GPU_KMS)) { > > + /* get display info */ > > + virtio_cread_le(vgdev->vdev, struct virtio_gpu_config, > > + num_scanouts,