search for: frambuffers

wwp wrote: > > On Fri, 4 Aug 2017 13:24:08 +0200 Andreas Benzler <andreas at benzlerweb.de> > wrote: > >> Ok you in Grub press tab and then add ?3? after the initrd entry ?. >> quiet?? >> >> yum remove xorg-x11-drv-nouveau >> >> And see if X11 come up with standard frambuffer? >> >> Disable nouveau complete from kernel if the upper

When I turn on the "Framebuffer console support" in compiling kernel, after system startup, the console doesn''t work properly and the kernel parameter( for example: vga=719) doesn''t do any effect on kernel. who can help me ? thanks in advance! Andrew Liu _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com

Ok you in Grub press tab and then add ?3? after the initrd entry ?. quiet?? yum remove xorg-x11-drv-nouveau And see if X11 come up with standard frambuffer? Disable nouveau complete from kernel if the upper not helps. nano /etc/modprobe.d/blacklist-nouveau.conf blacklist nouveau > Am 04.08.2017 um 12:52 schrieb wwp <subscript at free.fr>: > > Hello, > > > On Thu,

Some question. Can I install Xen-3.2.1 with 2.6.18-xen kernel... to my Dom0 and without HVM, starting a debian(DomU) with kernel 2.6.25 from kernel src and compiled with all XEN port / features ? or i need to use the vmlinuz-2.6.18-xen to all my DomU ?? Thanks Crazy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I have been scouring this list''s archives and have consumed any and all how-to guides I could find but am still unsure. All discussion in this list on this issue is around hvm/vti DomU''s. Has anyone been able to attach a vnc client to a vanilla (non-hvm) DomU using the VNC console setting? On an FC5 (2.6.16-1.2080_FC5xen0) kernel deployed on vanilla (non-hvm) hardware,

...upport. Current generic fbdev emulation -expects the framebuffer in system memory (or system-like memory). +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation +expected the framebuffer in system memory or system-like memory. By employing +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported +as well. Contact: Maintainer of the driver you plan to convert @@ -446,6 +448,24 @@ Contact: Ville Syrj?l?, Daniel Vetter Level: Intermediate +Use struct dma_buf_map throughout codebase +------------------------------------------ + +Pointers to shared devic...

If you wanne use the opensource version from nvidia can test my private driver stack [cms4all-kernel] name=cms4all-kernel baseurl=http://centos.cms4all.org/repo/7/kernel/ #baseurl=file:///srv/repo/centos/7/kernel gpgcheck=0 enabled=1 Same as ml + some AMD flags and [cms4all-drivers] name=cms4all-drivers baseurl=http://centos.cms4all.org/repo/7/drivers/ #baseurl=file:///srv/repo/centos/7/drivers

Hi, thanks for the feedback. Am 29.04.19 um 21:58 schrieb Sam Ravnborg: > Hi Thomas. > > Some minor things and some bikeshedding too. > > One general^Wbikeshedding thing - unint32_t is used in many places. > And then s64 in one place. > Seems like two concepts are mixed. > Maybe be consistent and use u32, s32 everywhere? The DRM API already has a mixture of such types

Hello, On Fri, 4 Aug 2017 13:24:08 +0200 Andreas Benzler <andreas at benzlerweb.de> wrote: > Ok you in Grub press tab and then add ?3? after the initrd entry ?. quiet?? > > yum remove xorg-x11-drv-nouveau > > And see if X11 come up with standard frambuffer? > > Disable nouveau complete from kernel if the upper not helps. > > nano

...ric fbdev emulation > -expects the framebuffer in system memory (or system-like memory). > +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation > +expected the framebuffer in system memory or system-like memory. By employing > +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported > +as well. > > Contact: Maintainer of the driver you plan to convert > > Level: Intermediate > > +Reimplement functions in drm_fbdev_fb_ops without fbdev > +------------------------------------------------------- > + > +A number...

...ric fbdev emulation > -expects the framebuffer in system memory (or system-like memory). > +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation > +expected the framebuffer in system memory or system-like memory. By employing > +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported > +as well. > > Contact: Maintainer of the driver you plan to convert > > Level: Intermediate > > +Reimplement functions in drm_fbdev_fb_ops without fbdev > +------------------------------------------------------- > + > +A number...

...ric fbdev emulation > -expects the framebuffer in system memory (or system-like memory). > +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation > +expected the framebuffer in system memory or system-like memory. By employing > +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported > +as well. > > Contact: Maintainer of the driver you plan to convert > > Level: Intermediate > > +Reimplement functions in drm_fbdev_fb_ops without fbdev > +------------------------------------------------------- > + > +A number...

...ric fbdev emulation > -expects the framebuffer in system memory (or system-like memory). > +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation > +expected the framebuffer in system memory or system-like memory. By employing > +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported > +as well. > > Contact: Maintainer of the driver you plan to convert > > Level: Intermediate > > +Reimplement functions in drm_fbdev_fb_ops without fbdev > +------------------------------------------------------- > + > +A number...

Hi Thomas. Some minor things and some bikeshedding too. One general^Wbikeshedding thing - unint32_t is used in many places. And then s64 in one place. Seems like two concepts are mixed. Maybe be consistent and use u32, s32 everywhere? I did not read the code carefully enough to understand it. I cannot give a r-b or a-b - as I feel I need to understand it to do so. Sam On Mon, Apr 29, 2019 at

Hi Thomas. Some minor things and some bikeshedding too. One general^Wbikeshedding thing - unint32_t is used in many places. And then s64 in one place. Seems like two concepts are mixed. Maybe be consistent and use u32, s32 everywhere? I did not read the code carefully enough to understand it. I cannot give a r-b or a-b - as I feel I need to understand it to do so. Sam On Mon, Apr 29, 2019 at

...upport. Current generic fbdev emulation -expects the framebuffer in system memory (or system-like memory). +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation +expected the framebuffer in system memory or system-like memory. By employing +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported +as well. Contact: Maintainer of the driver you plan to convert Level: Intermediate +Reimplement functions in drm_fbdev_fb_ops without fbdev +------------------------------------------------------- + +A number of callback functions in drm_fbdev_fb_ops could be...

...upport. Current generic fbdev emulation -expects the framebuffer in system memory (or system-like memory). +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation +expected the framebuffer in system memory or system-like memory. By employing +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported +as well. Contact: Maintainer of the driver you plan to convert Level: Intermediate +Reimplement functions in drm_fbdev_fb_ops without fbdev +------------------------------------------------------- + +A number of callback functions in drm_fbdev_fb_ops could be...

...upport. Current generic fbdev emulation -expects the framebuffer in system memory (or system-like memory). +atomic modesetting and GEM vmap support. Historically, generic fbdev emulation +expected the framebuffer in system memory or system-like memory. By employing +struct dma_buf_map, drivers with frambuffers in I/O memory can be supported +as well. Contact: Maintainer of the driver you plan to convert Level: Intermediate +Reimplement functions in drm_fbdev_fb_ops without fbdev +------------------------------------------------------- + +A number of callback functions in drm_fbdev_fb_ops could be...

On August 2, 2017 3:18:29 AM CDT, wwp <subscript at free.fr> wrote: >Hello Johnny, > > >On Fri, 28 Jul 2017 13:47:14 -0500 Johnny Hughes <johnny at centos.org> >wrote: > >> On 07/28/2017 11:32 AM, wwp wrote: >> > Hello Johnny, >> > >> > >> > On Fri, 28 Jul 2017 10:33:15 -0500 Johnny Hughes ><johnny at centos.org>

...> > -expects the framebuffer in system memory (or system-like memory). > > +atomic modesetting and GEM vmap support. Historically, generic fbdev > > emulation +expected the framebuffer in system memory or system-like > > memory. By employing +struct dma_buf_map, drivers with frambuffers in I/O > > memory can be supported +as well. > > > > Contact: Maintainer of the driver you plan to convert > > > > Level: Intermediate > > > > +Reimplement functions in drm_fbdev_fb_ops without fbdev > > +--------------------------------------...