search for: uvesafb

...From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really express dependencies that only their > (current instances of) corresponding userspace components need? > Something seems wrong about that. uvesafb will always need X86_IOPORT. It's kind of implicit in the design. I'm not suggesting that fbdev should select X86_IOPORT but in the uvesafb case at least it's completely useless to have one and not the other. > IO_BITMAP_LONGS already gets defined to (0/sizeof(long)). And as far as...

...From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really express dependencies that only their > (current instances of) corresponding userspace components need? > Something seems wrong about that. uvesafb will always need X86_IOPORT. It's kind of implicit in the design. I'm not suggesting that fbdev should select X86_IOPORT but in the uvesafb case at least it's completely useless to have one and not the other. > IO_BITMAP_LONGS already gets defined to (0/sizeof(long)). And as far as...

https://bugs.freedesktop.org/show_bug.cgi?id=101447 Bug ID: 101447 Summary: Nouveau on GP106 can't work with another framebuffer drivers (possibly uvesafb) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

...ric (bsg) driver version 0.4 loaded (major 243) > io scheduler mq-deadline registered > io scheduler kyber registered > io scheduler bfq registered > hgafb: HGA card not detected. > hgafb: probe of hgafb.0 failed with error -22 > usbcore: registered new interface driver udlfb > uvesafb: failed to execute /sbin/v86d > uvesafb: make sure that the v86d helper is installed and executable > uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2) > uvesafb: vbe_init() failed with -22 > uvesafb: probe of uvesafb.0 failed with error -22 > vga16fb: mapped to 0x000000008...

...lsmod Module Size Used by nouveau 147136 1 drm 175696 2 nouveau snd_rtctimer 4240 0 fbcon 41264 76 font 4544 1 fbcon bitblit 5952 1 fbcon softcursor 2624 1 bitblit uvesafb 31096 1 fb 52368 4 fbcon,bitblit,softcursor,uvesafb cfbcopyarea 4096 1 uvesafb cn 9272 2 uvesafb cfbimgblt 3136 1 uvesafb cfbfillrect 4480 1 uvesafb nfs 266136 2 nfsd...

Hi, I''m trying to port AMD VGA passthru patch to the latest XEN and vanila kernel and I got SIGSEGV in static void ati_hw_out(uint16_t hport, uint32_t data) { ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1); asm volatile ("out %1, %0"::"Nd"(hport),"a"(data)); ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0); } I tried old 2.6.32

...it may these days be the only mainstream one that needs the select >>> adding. >> >> Should kernel drivers really express dependencies that only their >> (current instances of) corresponding userspace components need? >> Something seems wrong about that. > > uvesafb will always need X86_IOPORT. It's kind of implicit in the design. > I'm not suggesting that fbdev should select X86_IOPORT but in the uvesafb > case at least it's completely useless to have one and not the other. Are there any users of uvesafb at all? Last time I changed that dr...

...ric (bsg) driver version 0.4 loaded (major 243) > io scheduler mq-deadline registered > io scheduler kyber registered > io scheduler bfq registered > hgafb: HGA card not detected. > hgafb: probe of hgafb.0 failed with error -22 > usbcore: registered new interface driver udlfb > uvesafb: failed to execute /sbin/v86d > uvesafb: make sure that the v86d helper is installed and executable > uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2) > uvesafb: vbe_init() failed with -22 > uvesafb: probe of uvesafb.0 failed with error -22 > vga16fb: mapped to 0x00000000a...

...ric (bsg) driver version 0.4 loaded (major 243) > io scheduler mq-deadline registered > io scheduler kyber registered > io scheduler bfq registered > hgafb: HGA card not detected. > hgafb: probe of hgafb.0 failed with error -22 > usbcore: registered new interface driver udlfb > uvesafb: failed to execute /sbin/v86d > uvesafb: make sure that the v86d helper is installed and executable > uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2) > uvesafb: vbe_init() failed with -22 > uvesafb: probe of uvesafb.0 failed with error -22 > vga16fb: mapped to 0x00000000a...

...these days be the only mainstream one that needs the select > > > adding. > > > > Should kernel drivers really express dependencies that only their > > (current instances of) corresponding userspace components need? > > Something seems wrong about that. > > uvesafb will always need X86_IOPORT. It's kind of implicit in the design. > I'm not suggesting that fbdev should select X86_IOPORT but in the uvesafb > case at least it's completely useless to have one and not the other. OK, fair enough. Do you want the patch series respun to add that s...

On Sun, 2 Nov 2014 09:33:01 -0800 Josh Triplett <josh at joshtriplett.org> wrote: > On the vast majority of modern systems, no processes will use the > userspsace IO syscalls, iopl and ioperm. Add a new config option, > CONFIG_X86_IOPORT, to support configuring them out of the kernel > entirely. Most current systems do not run programs using these > syscalls, so X86_IOPORT

On Sun, 2 Nov 2014 09:33:01 -0800 Josh Triplett <josh at joshtriplett.org> wrote: > On the vast majority of modern systems, no processes will use the > userspsace IO syscalls, iopl and ioperm. Add a new config option, > CONFIG_X86_IOPORT, to support configuring them out of the kernel > entirely. Most current systems do not run programs using these > syscalls, so X86_IOPORT

http://bugs.freedesktop.org/show_bug.cgi?id=22765 Summary: Nouveau KMS makes framebuffer consoles unusable on 9800M Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

...6 +++--- include/uapi/sound/hdspm.h | 6 +++--- include/uapi/sound/sb16_csp.h | 6 +++--- include/uapi/sound/sfnt_info.h | 6 +++--- include/uapi/video/edid.h | 6 +++--- include/uapi/video/sisfb.h | 6 +++--- include/uapi/video/uvesafb.h | 6 +++--- include/uapi/xen/evtchn.h | 6 +++--- include/uapi/xen/privcmd.h | 6 +++--- 80 files changed, 244 insertions(+), 237 deletions(-) diff --git a/include/uapi/asm-generic/auxvec.h b/include/uapi/asm-generic/auxvec.h index b99573b..c4b445a 100...

...6 +++--- include/uapi/sound/hdspm.h | 6 +++--- include/uapi/sound/sb16_csp.h | 6 +++--- include/uapi/sound/sfnt_info.h | 6 +++--- include/uapi/video/edid.h | 6 +++--- include/uapi/video/sisfb.h | 6 +++--- include/uapi/video/uvesafb.h | 6 +++--- include/uapi/xen/evtchn.h | 6 +++--- include/uapi/xen/privcmd.h | 6 +++--- 80 files changed, 244 insertions(+), 237 deletions(-) diff --git a/include/uapi/asm-generic/auxvec.h b/include/uapi/asm-generic/auxvec.h index b99573b..c4b445a 100...

...6 +++--- include/uapi/sound/hdspm.h | 6 +++--- include/uapi/sound/sb16_csp.h | 6 +++--- include/uapi/sound/sfnt_info.h | 6 +++--- include/uapi/video/edid.h | 6 +++--- include/uapi/video/sisfb.h | 6 +++--- include/uapi/video/uvesafb.h | 6 +++--- include/uapi/xen/evtchn.h | 6 +++--- include/uapi/xen/privcmd.h | 6 +++--- 80 files changed, 244 insertions(+), 237 deletions(-) diff --git a/include/uapi/asm-generic/auxvec.h b/include/uapi/asm-generic/auxvec.h index b99573b..c4b445a 100...

...CD (kernel 2.6.32-41). Here is my (V4.04) syslinux.cfg: PROMPT 0 DISPLAY splash.lpg TIMEOUT 0 DEFAULT linux CONSOLE 0 LABEL linux kernel vmlinuz append boot=balird initrd=initrd.gz rolayer=LABEL=Cd_rom:/filesystem.squashfs ro_mpoint=/cdrom ro_mpoint_opts=rw quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap Every thing is ok : splash screen is displayed. But after a few second, and before seeing plymouth screen, i've got a grey screen with cursor on top left. What have i to do to don't have this grey screen? Thanks, Daniel.

I've been trying to compile klibc on my system, so that I can have high resolution consoles via uvesafb, without conflicting with the NVidia drivers I need to use to handle hi-def video. I have tried versions 1.5.20, 2.0.1 and 2.0.2 all without success. My system is Slackware64-14.0 running kernel 3.6.3 on an AMD quad core motherboard. GCC version is 4.7.1. My initial problem was that the compil...

Greetings! I have installed xen-4.0 with kernel 2.6.32 on a gentoo box. Everything works perfectly, except one tiny detail. I do not have X installed on the machine, so I configured the (old, non-xen) kernel to use a framebuffer, so that I don''t have to cope with the ugly 80x25 resolution, especially on a 19" display. Unfortunately, with the xen kernel, dom0 now uses the 80x25 mode

Greetings, I got the below dmesg and the first bad commit is commit cf39c8e5352b4fb9efedfe7e9acb566a85ed847c Merge: 3398d25 23b7eaf Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Wed Sep 4 17:45:39 2013 -0700 Merge tag ''stable/for-linus-3.12-rc0-tag'' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull Xen updates from Konrad