similar to: Framebuffer double buffering (via FBIOPAN_DISPLAY)

Displaying 20 results from an estimated 500 matches similar to: "Framebuffer double buffering (via FBIOPAN_DISPLAY)"

2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
<div dir='auto'>I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this guide, "http://betteros.org/tut/graphics1.php#doublebuffer", I attempted to set the mmap allocation size to double, but it caused the mmap to fail. I no longer believe that it is a driver issue, though, because I just
2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Well...it's been a bit of a mixed bag.? Setting drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to 2160 as opposed to 1080 (My monitor vertical resolution)? This fixed the mmap() problem.? However, it only worked on my main workstation.? My laptop running Intel graphics wasn't affected by the change in kernel cmdline.? My workstation is a custom build from a few
2020 Jul 05
1
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Oops, the FBIOPAN_DISPLAY ioctl error was a stupid mistake on mistake on my part.? Thanks for the info on where the validation code was.? Comparing against that made it easy to find the mistake.? It's working now, well...where I have been able to get over-allocation working!? Thanks for the help.? If I can't get the over-allocation to work on my other systems, I'll take it up in
2020 Jul 05
0
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Check fb_pan_display in drivers/video/fbdev/core/fbmem.c for the argument validation of the FBIOPAN_DISPLAY ioctl. CONFIG_FB_NVIDIA is a dedicated fbdev driver, not compatible with nouveau (it takes over the relevant PCI device). It also won't support your Pascal GPU, I believe -- I think it MIGHT support the Tesla generation (i.e. G80..GT21x) but definitely not anything newer. Most likely it
2020 Jul 05
0
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Try booting with drm_kms_helper.drm_fbdev_overalloc=200 and see if it works with that. (There's also CONFIG_DRM_FBDEV_OVERALLOC which sets the default.) Cheers, -ilia On Sun, Jul 5, 2020 at 3:41 PM <michael at michaelkloos.com> wrote: > > I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this
2020 Jul 05
0
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Are you setting the overallocation to 200? On Sun, Jul 5, 2020 at 3:41 AM Michael T. Kloos <michael at michaelkloos.com> wrote: > > Does NOUVEAU support mmaping a double-sized Framebuffer? > When attempting to run, where fd refers to "/dev/fb0": > > mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); > > I get back an invalid argument error.
2017 Mar 01
2
[lld] We call SymbolBody::getVA redundantly a lot...
On Tue, Feb 28, 2017 at 11:39 PM, Rui Ueyama <ruiu at google.com> wrote: > I also did a quick profiling a few months ago and noticed just like you > that scanRelocations consumes a fairly large percentage of overall > execution time. That caught my attention because at the time I was looking > for a place that I can parallelize. > > scanRelocations is not parallelizable
2014 Apr 17
2
[Bug 77586] New: [NV98] On recent Linux kernel (3.13 and 3.14), the GPU locks up around the time an X server starts
https://bugs.freedesktop.org/show_bug.cgi?id=77586 Priority: medium Bug ID: 77586 Assignee: nouveau at lists.freedesktop.org Summary: [NV98] On recent Linux kernel (3.13 and 3.14), the GPU locks up around the time an X server starts QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified
2008 Aug 16
1
Minimal COM32 Root Module
Greetings! As I have presented in the announcement about the ELF dynamic linker preview earlier this week, one of my tasks now is to reduce the size of the root COM32 module to a minimum, and make the rest of the klibc available as dynamic loadable content. After I studied the linker map output and saw what are the minimal requirements of the dynamic linker itself from the C library (the object
2012 Nov 27
0
Syslinux-5.00-pre11
Hi guys, Here's another 5.00 prerelease. This one includes fixes for most of the bugs reported in the last round of feedback. The XFS filesystem code from Paulo also got merged this time and there were a bunch of fixes from a Coverity report. This won't be the last prerelease, but we are nearing the end of the 5.00 release cycle, so please do test. Shortlog append below. --- Chen
2017 Mar 01
2
[lld] We call SymbolBody::getVA redundantly a lot...
On Tue, Feb 28, 2017 at 12:10 PM, Rui Ueyama <ruiu at google.com> wrote: > I don't think getVA is particularly expensive, and if it is not expensive > I wouldn't cache its result. Did you experiment to cache getVA results? I > think you can do that fairly easily by adding a std::atomic_uint64_t to > SymbolBody and use it as a cache for getVA. > You're right,
2015 Sep 24
0
[PATCH] com32/disk: add UEFI support
Rework disk library to work on a firmware independent way. Each specific implementation goes through subdirs like "bios/" and "efi/" respectively. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/include/syslinux/disk.h | 50 +++- com32/lib/Makefile | 2 + com32/lib/syslinux/disk.c | 583
2009 Jan 13
4
Out of memory
Sorry for previous post with incorrect referrals/thread. For large mailboxes (64k + messages) using maildir I got random "out of memory" errors. [mail addresses hidden] dovecot: Dec 05 18:25:27 Error: IMAP(****@****): block_alloc(): Out of memory dovecot: Dec 05 18:25:27 Error: child 14142 (imap) returned error 83 (Out of memory) dovecot: Dec 05 18:27:29 Error: IMAP(****@****):
2005 Dec 27
9
2.6.14 - HTB/SFQ QoS broken?
Hello, First of all, I already contacted Martin Devera, the developer of HTB, and he told me to search for help on this mailinglist, thus I am describing my problems here now... I am kind of seriously annoyed by QoS as I have been trying for over 3 years to get it working properly - first I did not understand how it works, then it seemed not to work, then it was working perfectly for half a
2005 Jun 16
9
Re: dom0 bootstrap for xenstore
On Thu, 2005-06-16 at 06:17 +0100, Keir Fraser wrote: > > I suggested that we simply mmap /dev/kmem for the xenstored to access > > the domain0 page for the moment. That doesn''t work: we''ll do something > > else. > > Just use xc_map_foreign_range(), as you would for mapping any other > domain''s xenstore page. So here''s my patch
2009 Dec 27
3
[PATCH 1/2] drm/nv50: align size of buffer object to the right boundaries.
- Depth and stencil buffers are supposed to be large enough in general. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_bo.c | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c b/drivers/gpu/drm/nouveau/nouveau_bo.c index e342a41..9fc4bd6 100644 ---
2016 Nov 17
3
UB in MemoryBufferMMapFile
In MemoryBuffer::init, we have an assert that reads the memory at `BufEnd`, which is one past the end of some memory region: from lib/Support/MemoryBuffer.cpp:45: > void MemoryBuffer::init(const char *BufStart, const char *BufEnd, > bool RequiresNullTerminator) { > assert((!RequiresNullTerminator || BufEnd[0] == 0) && > "Buffer is not
2005 May 19
1
mke2fs options for very large filesystems
>Yes, if you are creating larger files. By default e2fsck assumes the average >file size is 8kB and allocates a corresponding number of inodes there. If, >for example, you are storing lots of larger files there (digital photos, MP3s, >etc) that are in the MB range you can use "-t largefile" or "-t largefile4" >to specify an average file size of 1MB or 4MB
2011 Mar 07
7
Winetricks gfw under root vs under user
Code: sh winetricks gfw does not work under regular user; only under root ( Code: sudo sh winetricks gfw ). What have i tried: * wiping ~/.wine preffix directory * creating new user in the system with clean ~/ home directory * applying winetricks volnum and winetricks sandbox * different versions of wine; from 1.2 to 1.3.15 * switching from 64-hybrid system to 32-vanilla one * switching from
2012 Mar 23
19
[PATCH 00/19][elflink] Improve compatibility with 4.x
From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse