search for: screensize

Displaying 11 results from an estimated 11 matches for "screensize".

Did you mean: screen_size
2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
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. This doesn't happen if I only request a single screensize. Is this a limitation of the driver? -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop...
2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
...5, 2020 at 3:41 AM Michael T. Kloos <br> <michael@michaelkloos.com> wrote: <br> > <br> > Does NOUVEAU support mmaping a double-sized Framebuffer? <br> > When attempting to run, where fd refers to "/dev/fb0": <br> > <br> > mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); <br> > <br> > I get back an invalid argument error. This doesn't happen if I only <br> > request a single screensize. Is this a limitation of the driver? <br> > <br> > _______________________________...
2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
...t;> >> 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. This doesn't happen if I only >>> request a single screensize. Is this a limitation of the driver? >>> >>> ______________________________________________...
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. This doesn't happen if I only > request a single screensize. Is this a limitation of the driver? > > _______________________________________________ > Nouveau mailing list > Nouveau...
2020 Jul 05
0
Framebuffer double buffering (via FBIOPAN_DISPLAY)
...ion 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. This doesn't happen if I only > > request a single screensize. Is this a limitation of the driver? > > > > _______________________________________________ > > Nou...
2020 Jul 05
1
Framebuffer double buffering (via FBIOPAN_DISPLAY)
...: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. This doesn't happen if I only >>>>> request a single screensize. Is this a limitation of the driver? >>>>> >>>>> ______...
2020 Jul 05
0
Framebuffer double buffering (via FBIOPAN_DISPLAY)
...ul 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. This doesn't happen if I only > >>> request a single screensize. Is this a limitation of the driver? > >>> > >>> _____________________...
2008 Aug 16
1
Minimal COM32 Root Module
...l.o sys/cfarcall.o sys/zeroregs.o \ sys/argv.o \ sys/ftell.o \ sys/isatty.o sys/fstat.o LIBGCC_OBJS = \ libgcc/__ashldi3.o \ libgcc/__negdi2.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o \ libgcc/__muldi3.o \ libgcc/__divdi3.o libgcc/__moddi3.o LIBCONSOLE_OBJS = \ sys/colortable.o sys/screensize.o \ \ sys/rawcon_write.o \ sys/null_read.o sys/null_write.o sys/serial_write.o \ \ sys/xserial_write.o \ \ sys/ansi.o \ \ sys/ansicon_write.o sys/ansiserial_write.o \ \ syslinux/serial.o LIBOTHER_OBJS = \ abort.o atexit.o atoi.o atol.o atoll.o calloc.o creat.o \ ct...
2012 Nov 27
0
Syslinux-5.00-pre11
...releases Revert "menu: Make "menu clear" the default" ldlinux: Reset the console whenever we execute a module Merge branch 'xfs-for-hpa' of git://zytor.com/users/pcacjr/syslinux into merge/elflink/xfs hdt-cli: Correct malloc() size argument screensize: Dereference pointers when checking cols/rows pxe: Don't leak inode on timeout module: Fix memory leak in spawn_load() module: Fix off-by-one error in findpath() core/elflink: Fix off-by-one error Merge branch 'coverity' into elflink Paulo Alcantara (46):...
2015 Sep 24
0
[PATCH] com32/disk: add UEFI support
...-prototypes -Winline -CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) +CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) $(FWFLAGS) ifndef EFI_BUILD CFLAGS += -mregparm=3 -DREGPARM=3 endif VPATH = $(SRC) + +LIBSYS_OBJS = \ + sys/line_input.o \ + sys/colortable.o sys/screensize.o \ + \ + sys/stdcon_read.o sys/stdcon_write.o sys/rawcon_read.o \ + sys/rawcon_write.o \ + sys/null_read.o sys/null_write.o sys/serial_write.o \ + \ + sys/xserial_write.o \ + \ + sys/ansi.o \ + \ + sys/ansicon_write.o sys/ansiserial_write.o \ + \ + sys/x86_init_fpu.o math/pow.o...
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