lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 9 Aug 2008 23:32:09 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	<JosephChan@....com.tw>
Cc:	akpm@...ux-foundation.org,
	<linux-fbdev-devel@...ts.sourceforge.net>,
	<linux-kernel@...r.kernel.org>, geert@...ux-m68k.org
Subject: Re: [Linux-fbdev-devel] [PATCH 0/13 v2] viafb: VIA Frame Buffer
 Device Driver

On Fri, 08 August 2008 <JosephChan@....com.tw> wrote:
> Here comes the 13 updated patchs for VIA Frame Buffer Device Driver.
> This driver could be used on VIA UniChrome (Pro) and Chrome9 family
> chips. All the patches are based on linux kernel 2.6.27-rc2

Seems to work for me when compiled into kernel on Commell LE365D (Via
CX700) though I get two unwanted effects:
- boot logo does not show up, where it should appear I just get a
  square of colored pixels (2 colors: background and foreground grid)
- when blanking console colored text remains visible (e.g. green '*'
  characters emitted during Gentoo boot)
  Ideally the output/monitor should got into standby when console is
  blanking


The boot logo issue exists when patch is applied to 2.6.26.2 and
2.6.27-rc2-git4, for the console blanking it's only tested on 2.6.26.2
as 2.6.27-rc2-git4 panics while probing hard drives.

Framebuffer related kernel commandline options:
  video=viafb:viafb_mode=1280x1024,viafb_bpp=32,viafb_refresh=60


Suspend to RAM (S3) works with BIOS configured to reinitialize the
graphics at resume time, I have not yet checked without this option
being enabled in BIOS (though it probably won't work as there is no
suspend/resume callback in the patch-set).
Have not checked yet if DRI has support for CX700 and can do the
suspend/resume handling as the intel DRI can do.


As Krzysztof Helt I'm in favor of merging and ironing out remaining
issues with incremental patches

Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ