[PATCH] fbdev: make the best-fit section of fb_find_mode return the closest matching mode

From: Michal Januszewski <[EMAIL PROTECTED]> Currently, if a perfect match in terms of resolution is not found, fb_find_mode() only looks for a best-fit mode among modes with a higher resolution than the one requested. Thus, if the user requests a resolution higher than the largest support

[PATCH] fbdev: make the best-fit section of fb_find_mode return the closest matching mode

From: Michal Januszewski [EMAIL PROTECTED] Currently, if a perfect match in terms of resolution is not found, fb_find_mode() only looks for a best-fit mode among modes with a higher resolution than the one requested. Thus, if the user requests a resolution higher than the largest supported one

[PATCH] uvesafb: don't treat valid modes returned by fb_find_mode() as errors

From: Michal Januszewski <[EMAIL PROTECTED]> Don't treat valid modes returned by fb_find_mode() (best-fit modes, default modes or the first valid mode) as errors. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uve

[PATCH] fbdev: make the best-fit section of fb_find_mode return the closest matching mode

From: Michal Januszewski <[EMAIL PROTECTED]> Currently, if a perfect match in terms of resolution is not found, fb_find_mode() only looks for a best-fit mode among modes with a higher resolution than the one requested. Thus, if the user requests a resolution higher than the largest support

[PATCH] fbdev: make the best-fit section of fb_find_mode return the closest matching mode

From: Michal Januszewski [EMAIL PROTECTED] Currently, if a perfect match in terms of resolution is not found, fb_find_mode() only looks for a best-fit mode among modes with a higher resolution than the one requested. Thus, if the user requests a resolution higher than the largest supported one

[PATCH] uvesafb: don't treat valid modes returned by fb_find_mode() as errors

From: Michal Januszewski [EMAIL PROTECTED] Don't treat valid modes returned by fb_find_mode() (best-fit modes, default modes or the first valid mode) as errors. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index a14ef89

[PATCH] Fix a spurious kfree_skb() call

Remove a spurious call to kfree_skb() in the connector rx_skb handler. This fixes a regression introduced by the '[NET]: make netlink user -> kernel interface synchronious' patch (cd40b7d3983c708aabe3d3008ec64ffce56d33b0) Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- d

[PATCH] Fix a spurious kfree_skb() call

Remove a spurious call to kfree_skb() in the connector rx_skb handler. This fixes a regression introduced by the '[NET]: make netlink user - kernel interface synchronious' patch (cd40b7d3983c708aabe3d3008ec64ffce56d33b0) Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git

[PATCH -mm] uvesafb: Don't access VGA registers directly when running on non-x86

of it on non-x86. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 853323e..b983d26 100644 --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -19,8 +19,10 @@ #include #include #include -#include #i

[PATCH -mm] uvesafb: Don't access VGA registers directly when running on non-x86

of it on non-x86. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 853323e..b983d26 100644 --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -19,8 +19,10 @@ #include linux/io.h #include linux/mutex.h #include

[PATCH -mm] uvesafb: Don't access VGA registers directly when running on non-x86

of it on non-x86. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 853323e..74fa7c7 100644 --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -935,6 +935,7 @@ static int uvesafb_setpalette(struct uvesafb_pal

Re: [PATCH -mm] video: uvesafb: Add X86 dependency.

non-x86, which is a bug and for which a patch will follow) and support or lack thereof for a specific arch should be dependent on v86d only. That being said, I think that having a kernel dependency tracking the development status of userspace code is generally a bad idea. Best regards, -- Michal Janus

Re: [PATCH -mm] video: uvesafb: Add X86 dependency.

thereof for a specific arch should be dependent on v86d only. That being said, I think that having a kernel dependency tracking the development status of userspace code is generally a bad idea. Best regards, -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux

[PATCH -mm] uvesafb: Don't access VGA registers directly when running on non-x86

of it on non-x86. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 853323e..74fa7c7 100644 --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -935,6 +935,7 @@ static int uvesafb_setpalette(struct uvesafb_pal_entry

[PATCH] fbdev: find mode with the highest/safest refresh rate in fb_find_mode()

database and the monitor limits, and a mode with the safe 60 Hz refresh rate otherwise. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3741ad7..9598c46 100644 --- a/drivers/video/modedb.c +++ b/drivers/video/mo

[PATCH] fbdev: find mode with the highest/safest refresh rate in fb_find_mode()

database and the monitor limits, and a mode with the safe 60 Hz refresh rate otherwise. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3741ad7..9598c46 100644 --- a/drivers/video/modedb.c +++ b/drivers/video/modedb.c

Re: [Linux-fbdev-devel] [PATCH] fbdev: find mode with highest refresh rate in fb_find_mode()

closest to 60 Hz otherwise? I'm sorry for the delayed reply. Best regards. -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux Developerhttp://people.gentoo.org/spock - To unsubscribe from this list: send the line "unsubscribe linux-ke

Re: [Linux-fbdev-devel] [PATCH] uvesafb: select connector in Kconfig

On Sat, Aug 25, 2007 at 08:23:41AM -0700, Randy Dunlap wrote: > There are 2 problems with this. > > a. CONNECTOR depends on NET, but select won't enable NET, so if > NET is not enabled otherwise, CONNECTOR still won't build. > This is a longstanding select/kconfig issue. > > b. CONNECTOR

Re: [Linux-fbdev-devel] [PATCH] uvesafb: select connector in Kconfig

On Sat, Aug 25, 2007 at 08:23:41AM -0700, Randy Dunlap wrote: There are 2 problems with this. a. CONNECTOR depends on NET, but select won't enable NET, so if NET is not enabled otherwise, CONNECTOR still won't build. This is a longstanding select/kconfig issue. b. CONNECTOR depends on

Re: [Linux-fbdev-devel] [PATCH] fbdev: find mode with highest refresh rate in fb_find_mode()

it so that it looks for a mode with the highest refresh rate if either a non-generic modedb is used or info.monspecs.{vfmin,vfmax,hfmin,hfmax,dclkmax} are all non-zero, and for a mode with refresh rate closest to 60 Hz otherwise? I'm sorry for the delayed reply. Best regards. -- Michal Januszewski

[PATCH] uvesafb: select connector in Kconfig

Make uvesafb select connector instead of depending on it being already selected. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig index f1cc899..e152eed 100644 --- a/drivers/video/Kconfig +++ b/drivers/video/Kconfig @@

[PATCH] uvesafb: select connector in Kconfig

Make uvesafb select connector instead of depending on it being already selected. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig index f1cc899..e152eed 100644 --- a/drivers/video/Kconfig +++ b/drivers/video/Kconfig @@ -594,7

[PATCH 6/7] uvesafb: use the default refresh rate if the monitor limits are not set

Use the default refresh rate if the monitor limits aren't set (either using data from the EDID block, or explicitly by the user). Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 2f1e5af..2e5f1b5 100644 --- a/d

[PATCH 7/7] uvesafb: try to set mode with default timings if setting it with our own timings failed

Sometimes the BIOS might not perform the mode switch correctly because of the timings that we requested. In case this happens, try to set the video mode with the default timings instead. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/d

[PATCH 5/7] uvesafb: use VISUAL_TRUECOLOR as the default visual

Set uvesafb's default visual to truecolor. This prevents fbcon from being detected as 'mono' when using uvesafb. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index e480670..2f1e5af 100644 --- a/drivers/video/uve

[PATCH 3/7] uvesafb: fix a typo in a warning

Replace "vesafb" with "uvesafb" in a kernel warning message. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -4

[PATCH 4/7] uvesafb: add info about pmipal, yrap and ypan being available only on x86

Features that use the Protected Mode Interface are available on x86 only. Document this in the uvesafb description. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/Documentation/fb/uvesafb.txt b/Documentation/fb/uvesafb.txt index cfc4e55..1a3b65b 100644 --- a/Documen

[PATCH 2/7] uvesafb: always use mutexes when accessing uvfb_tasks

Accesses to the uvfb_tasks array should be always be protected by a mutex to avoid race conditions. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index aa5a9c3..e480670 100644 --- a/drivers/video/uvesafb.c +++ b/d

[PATCH 1/7] uvesafb: set the refresh rate to 60Hz if nocrtc is used

If the nocrtc flag is set, make sure the timings in fb_var are set to 60Hz and thus reflect the default BIOS refresh rate that is being used. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 9c21791..aa5a9c3

[PATCH 0/7] uvesafb: miscellaneous fixes and updates

This set of patches fixes several minor issues with uvesafb. It requires all previous uvesafb patches (currently in -mm). -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux Developerhttp://people.gentoo.org/spock - To unsubscribe from

[PATCH 0/7] uvesafb: miscellaneous fixes and updates

This set of patches fixes several minor issues with uvesafb. It requires all previous uvesafb patches (currently in -mm). -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux Developerhttp://people.gentoo.org/spock - To unsubscribe from

[PATCH 1/7] uvesafb: set the refresh rate to 60Hz if nocrtc is used

If the nocrtc flag is set, make sure the timings in fb_var are set to 60Hz and thus reflect the default BIOS refresh rate that is being used. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 9c21791..aa5a9c3 100644

[PATCH 2/7] uvesafb: always use mutexes when accessing uvfb_tasks

Accesses to the uvfb_tasks array should be always be protected by a mutex to avoid race conditions. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index aa5a9c3..e480670 100644 --- a/drivers/video/uvesafb.c +++ b/drivers

[PATCH 3/7] uvesafb: fix a typo in a warning

Replace vesafb with uvesafb in a kernel warning message. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -408,7 +412,7 @@ static void uvesafb_vbe_state_restore

[PATCH 4/7] uvesafb: add info about pmipal, yrap and ypan being available only on x86

Features that use the Protected Mode Interface are available on x86 only. Document this in the uvesafb description. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/Documentation/fb/uvesafb.txt b/Documentation/fb/uvesafb.txt index cfc4e55..1a3b65b 100644 --- a/Documentation/fb

[PATCH 5/7] uvesafb: use VISUAL_TRUECOLOR as the default visual

Set uvesafb's default visual to truecolor. This prevents fbcon from being detected as 'mono' when using uvesafb. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index e480670..2f1e5af 100644 --- a/drivers/video/uvesafb.c

[PATCH 6/7] uvesafb: use the default refresh rate if the monitor limits are not set

Use the default refresh rate if the monitor limits aren't set (either using data from the EDID block, or explicitly by the user). Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index 2f1e5af..2e5f1b5 100644 --- a/drivers

[PATCH 7/7] uvesafb: try to set mode with default timings if setting it with our own timings failed

Sometimes the BIOS might not perform the mode switch correctly because of the timings that we requested. In case this happens, try to set the video mode with the default timings instead. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff --git a/drivers/video/uvesafb.c b/drivers/video

[PATCH] fbdev: find mode with highest refresh rate in fb_find_mode()

Currently if the refresh rate is not specified fb_find_mode() returns the first known video mode with the requested resoluion, which provides no guarantees wrt the refresh rate. Change this so that the mode with the highest refresh rate is returned instead. Signed-off-by: Michal Januszewski

[PATCH] fbdev: find mode with highest refresh rate in fb_find_mode()

Currently if the refresh rate is not specified fb_find_mode() returns the first known video mode with the requested resoluion, which provides no guarantees wrt the refresh rate. Change this so that the mode with the highest refresh rate is returned instead. Signed-off-by: Michal Januszewski

[PATCH v2 3/5] uvesafb: change connector's max message size

Change the maximum message size to 16k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- This patch increases the limit to 16k since the previous value (4k) proved to be insufficient for the hardware state buffer on some video

Re: [PATCH v2 0/5] uvesafb: a general description

On Thu, Jul 05, 2007 at 01:38:46PM -0400, Ryan Hope wrote: > I applied > > http://dev.gentoo.org/~spock/projects/uvesafb/archive/uvesafb-0.1-rc2-2.6.22-rc6.patchto > 2.6.22-rc6-mm1... everything seems to be working properly. However, in dmesg > I did notice the following message: > >

Re: [PATCH v2 0/5] uvesafb: a general description

On Thu, Jul 05, 2007 at 01:38:46PM -0400, Ryan Hope wrote: I applied http://dev.gentoo.org/~spock/projects/uvesafb/archive/uvesafb-0.1-rc2-2.6.22-rc6.patchto 2.6.22-rc6-mm1... everything seems to be working properly. However, in dmesg I did notice the following message: uvesafb:

[PATCH v2 3/5] uvesafb: change connector's max message size

Change the maximum message size to 16k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- This patch increases the limit to 16k since the previous value (4k) proved to be insufficient for the hardware state buffer on some video cards

Re: [PATCH 0/4] fbdev: uvesafb

On Tue, Jun 26, 2007 at 11:42:41AM +0100, Jonathan McDowell wrote: > Have you considered using libx86[1] in v86d? It looks very similar to > what you have at present and there are plans to extend it to non > x86(_64) archs. It looks like an interesting solution and it is indeed similar to what

[PATCH v2 5/5] uvesafb: documentation

Documentation for the uvesafb driver. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- Documentation/fb/uvesafb.txt | 187 ++ 1 files changed, 187 insertions(+), 0 deletions(-) diff --git a/Documentation/fb/uvesafb.txt b/Documentat

[PATCH v2 3/5] uvesafb: change connector's max message size

Change the maximum message size to 4k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- include/linux/connector.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/connector.h b/include

[PATCH v2 2/5] uvesafb: add connector entries

Add connector idx and val constants for v86d and uvesafb. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- include/linux/connector.h |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/include/linux/connector.h b/include/linux/connector.h index 10eb56b..1

[PATCH v2 1/5] uvesafb: export fb_destroy_modelist

Make fb_destroy_modelist an exported symbol for use in the uvesafb driver. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- drivers/video/modedb.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3

[PATCH v2 0/5] uvesafb: a general description

such as the ones used in [1]. The current implementation of v86d can use either LRMI or x86emu to run the BIOS code and supports both x86 and x86_64. [1] http://dev.gentoo.org/~spock/projects/vesafb-tng/ [2] http://dev.gentoo.org/~spock/projects/uvesafb/ Best regards. -- Michal Januszewski

[PATCH v2 0/5] uvesafb: a general description

such as the ones used in [1]. The current implementation of v86d can use either LRMI or x86emu to run the BIOS code and supports both x86 and x86_64. [1] http://dev.gentoo.org/~spock/projects/vesafb-tng/ [2] http://dev.gentoo.org/~spock/projects/uvesafb/ Best regards. -- Michal Januszewski

[PATCH v2 1/5] uvesafb: export fb_destroy_modelist

Make fb_destroy_modelist an exported symbol for use in the uvesafb driver. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- drivers/video/modedb.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3741ad7

[PATCH v2 2/5] uvesafb: add connector entries

Add connector idx and val constants for v86d and uvesafb. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- include/linux/connector.h |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/include/linux/connector.h b/include/linux/connector.h index 10eb56b..14cecaf

[PATCH v2 3/5] uvesafb: change connector's max message size

Change the maximum message size to 4k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- include/linux/connector.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/connector.h b/include/linux

[PATCH v2 5/5] uvesafb: documentation

Documentation for the uvesafb driver. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- Documentation/fb/uvesafb.txt | 187 ++ 1 files changed, 187 insertions(+), 0 deletions(-) diff --git a/Documentation/fb/uvesafb.txt b/Documentation/fb

Re: [PATCH 0/4] fbdev: uvesafb

On Tue, Jun 26, 2007 at 11:42:41AM +0100, Jonathan McDowell wrote: Have you considered using libx86[1] in v86d? It looks very similar to what you have at present and there are plans to extend it to non x86(_64) archs. It looks like an interesting solution and it is indeed similar to what I'm

Re: [PATCH 3/4] fbdev: uvesafb driver

On Sat, Jun 23, 2007 at 04:36:39PM -0700, Andrew Morton wrote: > On Sun, 24 Jun 2007 01:20:33 +0200 Michal Januszewski <[EMAIL PROTECTED]> > wrote: > > > > > +config FB_UVESA > > > > + tristate "Userspace VESA VGA graphics support

Re: [PATCH 3/4] fbdev: uvesafb driver

On Sat, Jun 23, 2007 at 04:36:39PM -0700, Andrew Morton wrote: On Sun, 24 Jun 2007 01:20:33 +0200 Michal Januszewski [EMAIL PROTECTED] wrote: +config FB_UVESA + tristate Userspace VESA VGA graphics support + depends on FB CONNECTOR These dependencies

Re: [PATCH 3/4] fbdev: uvesafb driver

On Sat, Jun 23, 2007 at 11:35:57AM -0700, Andrew Morton wrote: > On Sat, 23 Jun 2007 12:52:43 +0200 Michal Januszewski <[EMAIL PROTECTED]> > wrote: > > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig > > index 403dac7..5cc03f9 100644 > > --- a/drivers/v

Re: [PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate

On Sat, Jun 23, 2007 at 11:04:24AM -0700, Andrew Morton wrote: > On Sat, 23 Jun 2007 12:50:46 +0200 Michal Januszewski <[EMAIL PROTECTED]> > wrote: > > > + if (!refresh_specified) > > + refresh = 200; > > diff = refresh; > > best

Re: [PATCH 0/4] fbdev: uvesafb

On Sat, Jun 23, 2007 at 02:04:09PM +0200, Arnd Bergmann wrote: > On Saturday 23 June 2007, Michal Januszewski wrote: > >  The current implementation of v86d can use either LRMI or > > x86emu to run the BIOS code and supports both x86 and x86_64. > > Is there a fundamental

[PATCH 3/4] fbdev: uvesafb driver

Add the uvesafb driver, an enhanced version of vesafb that makes use of a userspace helper to run x86 Video BIOS code. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- drivers/video/Kconfig | 18 + drivers/video/Makefile |1 + drivers/video/uvesafb.c

[PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate

-by: Michal Januszewski <[EMAIL PROTECTED]> --- drivers/video/modedb.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3741ad7..98ee77b 100644 --- a/drivers/video/modedb.c +++ b/drivers/video/modedb.c @@ -

[PATCH 4/4] fbdev: uvesafb documentation

Add the documentation for the uvesafb driver. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- Documentation/fb/uvesafb.txt | 181 ++ 1 files changed, 181 insertions(+), 0 deletions(-) diff --git a/Documentation/fb/uvesafb.txt b/Documentat

[PATCH 0/4] fbdev: uvesafb

/vesafb-tng/ [2] http://dev.gentoo.org/~spock/projects/uvesafb/ Best regards. -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux Developerhttp://people.gentoo.org/spock - To unsubscribe from this list: send the line "unsubscribe linux-k

[PATCH 2/4] fbdev: add connector entries for uvesafb

Add connector's idx and val constants for v86d and uvesafb. Also change the maximum message size to 4k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- include/linux/connector.h |7 --- 1 files changed, 4 insertions

[PATCH 3/4] fbdev: uvesafb driver

Add the uvesafb driver, an enhanced version of vesafb that makes use of a userspace helper to run x86 Video BIOS code. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- drivers/video/Kconfig | 18 + drivers/video/Makefile |1 + drivers/video/uvesafb.c | 1902

[PATCH 4/4] fbdev: uvesafb documentation

Add the documentation for the uvesafb driver. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- Documentation/fb/uvesafb.txt | 181 ++ 1 files changed, 181 insertions(+), 0 deletions(-) diff --git a/Documentation/fb/uvesafb.txt b/Documentation/fb

[PATCH 2/4] fbdev: add connector entries for uvesafb

Add connector's idx and val constants for v86d and uvesafb. Also change the maximum message size to 4k to allow transfers of VBE data blocks from userspace. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- include/linux/connector.h |7 --- 1 files changed, 4 insertions(+), 3

[PATCH 0/4] fbdev: uvesafb

/vesafb-tng/ [2] http://dev.gentoo.org/~spock/projects/uvesafb/ Best regards. -- Michal Januszewski JID: [EMAIL PROTECTED] Gentoo Linux Developerhttp://people.gentoo.org/spock - To unsubscribe from this list: send the line unsubscribe linux-kernel

[PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate

-by: Michal Januszewski [EMAIL PROTECTED] --- drivers/video/modedb.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c index 3741ad7..98ee77b 100644 --- a/drivers/video/modedb.c +++ b/drivers/video/modedb.c @@ -606,16

Re: [PATCH 0/4] fbdev: uvesafb

On Sat, Jun 23, 2007 at 02:04:09PM +0200, Arnd Bergmann wrote: On Saturday 23 June 2007, Michal Januszewski wrote:  The current implementation of v86d can use either LRMI or x86emu to run the BIOS code and supports both x86 and x86_64. Is there a fundamental reason why you can't also run

Re: [PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate

On Sat, Jun 23, 2007 at 11:04:24AM -0700, Andrew Morton wrote: On Sat, 23 Jun 2007 12:50:46 +0200 Michal Januszewski [EMAIL PROTECTED] wrote: + if (!refresh_specified) + refresh = 200; diff = refresh; best = -1; for (i = 0; i dbsize; i

Re: [PATCH 3/4] fbdev: uvesafb driver

On Sat, Jun 23, 2007 at 11:35:57AM -0700, Andrew Morton wrote: On Sat, 23 Jun 2007 12:52:43 +0200 Michal Januszewski [EMAIL PROTECTED] wrote: diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig index 403dac7..5cc03f9 100644 --- a/drivers/video/Kconfig +++ b/drivers/video/Kconfig

[PATCH] fbcon: don't draw cursor when it's disabled

From: Michal Januszewski <[EMAIL PROTECTED]> When the cursor and echo are disabled on the current console, pressing a key will cause a black rectangle to be painted in the cursor's position. Fix this by not touching the framebuffer in fbcon_cursor() when the cursor is off. Signed-off-by:

[PATCH resend] vt: fix potential race in VT_WAITACTIVE handler

From: Michal Januszewski <[EMAIL PROTECTED]> On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen() but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the conso

[PATCH resend] vt: fix potential race in VT_WAITACTIVE handler

From: Michal Januszewski [EMAIL PROTECTED] On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen() but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the console sem

[PATCH] fbcon: don't draw cursor when it's disabled

From: Michal Januszewski [EMAIL PROTECTED] When the cursor and echo are disabled on the current console, pressing a key will cause a black rectangle to be painted in the cursor's position. Fix this by not touching the framebuffer in fbcon_cursor() when the cursor is off. Signed-off-by: Michal

[PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen(), but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the console sem held. Signed-off-by: Michal Januszewski

[PATCH] vt: fix a potential race in the VT_WAITACTIVE handler

On a multiprocessor machine the VT_WAITACTIVE ioctl call may return 0 if fg_console has already been updated in redraw_screen(), but the console switch itself hasn't been completed. Fix this by checking fg_console in vt_waitactive() with the console sem held. Signed-off-by: Michal Januszewski

[PATCH] fbdev: Update info->cmap when setting cmap from user-/kernelspace.

e code that is responsible for setting the cmap to fb_set_cmap() and out of fb_set_user_cmap() to avoid code-duplication. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff -Nupr linux-2.6.12-orig/drivers/video/fbcmap.c linux-2.6.12/drivers/video/fbcmap.c --- linux-2.6.12-orig/d

[PATCH][fbcon] Don't repaint the cursor when it is disabled.

this behaviour by avoiding painting anything when the cursor is disabled. Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]> --- diff -Nupr linux-2.6.12-orig/drivers/video/console/fbcon.c linux-2.6.12/drivers/video/console/fbcon.c --- linux-2.6.12-orig/drivers/video/console/fbcon.c 2005-06-17

[PATCH][fbcon] Don't repaint the cursor when it is disabled.

this behaviour by avoiding painting anything when the cursor is disabled. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff -Nupr linux-2.6.12-orig/drivers/video/console/fbcon.c linux-2.6.12/drivers/video/console/fbcon.c --- linux-2.6.12-orig/drivers/video/console/fbcon.c 2005-06-17 21:48

[PATCH] fbdev: Update info-cmap when setting cmap from user-/kernelspace.

that is responsible for setting the cmap to fb_set_cmap() and out of fb_set_user_cmap() to avoid code-duplication. Signed-off-by: Michal Januszewski [EMAIL PROTECTED] --- diff -Nupr linux-2.6.12-orig/drivers/video/fbcmap.c linux-2.6.12/drivers/video/fbcmap.c --- linux-2.6.12-orig/drivers/video

Re: [announce 7/7] fbsplash - documentation

On Wed, Mar 09, 2005 at 04:40:09PM +0100, Arnd Bergmann wrote: > Ok, I now saw that you call call_usermodehelper with wait==1. Why is that > necessary? If you don't wait there, you don't need any hacks around the > console semaphore, because the helper will simply wait for change_console > to

Re: [announce 7/7] fbsplash - documentation

On Wed, Mar 09, 2005 at 04:40:09PM +0100, Arnd Bergmann wrote: Ok, I now saw that you call call_usermodehelper with wait==1. Why is that necessary? If you don't wait there, you don't need any hacks around the console semaphore, because the helper will simply wait for change_console to finish.

Re: [announce 7/7] fbsplash - documentation

On Wed, Mar 09, 2005 at 01:17:11AM +0100, Arnd Bergmann wrote: > You also shouldn't create a class device every time you want to call > kobject_hotplug. Note that every character device already has a class > device associated with it, so you might be able to just use that to > call

Re: [announce 7/7] fbsplash - documentation

On Tue, Mar 08, 2005 at 04:18:07AM +0100, Arnd Bergmann wrote: > It should probably just use its own hotplug agent instead of calling > the helper directly. I've just had a look at it, and it seems possible. From what I have seen in the firmware_class.c code, it would require: - registering a

Re: [announce 7/7] fbsplash - documentation

On Tue, Mar 08, 2005 at 04:18:07AM +0100, Arnd Bergmann wrote: It should probably just use its own hotplug agent instead of calling the helper directly. I've just had a look at it, and it seems possible. From what I have seen in the firmware_class.c code, it would require: - registering a

Re: [announce 7/7] fbsplash - documentation

On Wed, Mar 09, 2005 at 01:17:11AM +0100, Arnd Bergmann wrote: You also shouldn't create a class device every time you want to call kobject_hotplug. Note that every character device already has a class device associated with it, so you might be able to just use that to call kobject_hotplug on

Re: Bootsplash for 2.6.11-rc4

On Sun, Feb 27, 2005 at 01:03:33PM -0800, Greg KH wrote: > Care to create a patch for the silent mode now? That should be simple > enough to get into the kernel, and will be a good place to build off of > for the rest of the things people want (verbose mode, etc.) I've just sent the whole thing

[announce 4/7] fbsplash - fbcon updates

Updates to fbcon.c. Kept as non-intrusive as possible. Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c --- a/drivers/video/console/fbcon.c 2005-03-07 16:50:34 +01:00 +++ b/drivers/video/console/fbcon.c

[announce 7/7] fbsplash - documentation

Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/Documentation/fb/00-INDEX b/Documentation/fb/00-INDEX --- a/Documentation/fb/00-INDEX 2005-03-07 16:50:34 +01:00 +++ b/Documentation/fb/00-INDEX 2005-03-07 16:50:34 +01:00 @@ -19,6 +19,8 @@ - info on the Matrox frame

[announce 6/7] fbsplash - kconfig and makefiles

Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/Kconfig b/drivers/video/Kconfig --- a/drivers/video/Kconfig 2005-03-07 16:50:34 +01:00 +++ b/drivers/video/Kconfig 2005-03-07 16:50:34 +01:00 @@ -1140,5 +1140,15 @@ source

[announce 5/7] fbsplash - fbdev updates

Fbcmap.c updates. Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/fbcmap.c b/drivers/video/fbcmap.c --- a/drivers/video/fbcmap.c2005-03-07 16:50:34 +01:00 +++ b/drivers/video/fbcmap.c2005-03-07 16:50:34 +01:00 @@ -16,6 +16,7 @@ #include #include

[announce 2/7] fbsplash - rendering routines

Fbsplash has its own set of rendering functions. These are unaccelerated but they should work with different framebuffer drivers. All rendering routines are completely separate from fbcon. Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/cfbsplash.c

[announce 3/7] fbsplash - data structures

Fbsplash uses a special iowrapper struct for communication with userspace. That struct, along with some useful #define's is exported to userspace programs in include/linux/fb.h. Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/fbsplash.h

[announce 1/7] fbsplash - the core interface

The core splash interface handles interaction with the userspace helper. All communication is done via ioctls on the fbsplash device, which is a misc character device. Signed-off-by: Michael Januszewski <[EMAIL PROTECTED]> --- diff -Nru a/drivers/video/fbsplash.c b/drivers/video/fbsplash.c ---

[announce 0/7] fbsplash - The Framebuffer Splash

Fbsplash - The Framebuffer Splash - is a feature that allows displaying images in the background of consoles that use fbcon. The project is partially descended from bootsplash. Unlike bootsplash, fbsplash has no in-kernel image decoder. Picture decompression is handled by a userspace helper

[announce 0/7] fbsplash - The Framebuffer Splash

Fbsplash - The Framebuffer Splash - is a feature that allows displaying images in the background of consoles that use fbcon. The project is partially descended from bootsplash. Unlike bootsplash, fbsplash has no in-kernel image decoder. Picture decompression is handled by a userspace helper

  1   2   >