+-
> drivers/video/intelfb/intelfbdrv.c | 5 ++-
> drivers/video/vga16fb.c|2 +-
Acked-by: Antonino A. Daplas <[EMAIL PROTECTED]>
with respect to the drivers/video portion.
Tony
-
To unsubscribe from this list: send the line "unsubscribe
/vga16fb.c|2 +-
Acked-by: Antonino A. Daplas [EMAIL PROTECTED]
with respect to the drivers/video portion.
Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
> I could solve this issue in two ways:
> - boot with VGA=791 parameter (initial boot was without VGA= parameter)
> - compile kernel without FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set (I also
> unset FB_VIRTUAL, but without its boot param that
On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
> While running a test with current Linus' git tree, I ran into the following
> issue. The issue is also present in stable 2.6.23.
>
> System x86_64; Pentium D; Intel 82945G/GZ on-board graphics
>
> After initial boot messages all output to
On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
While running a test with current Linus' git tree, I ran into the following
issue. The issue is also present in stable 2.6.23.
System x86_64; Pentium D; Intel 82945G/GZ on-board graphics
After initial boot messages all output to console
On Sat, 2007-10-13 at 20:13 +0200, Frans Pop wrote:
I could solve this issue in two ways:
- boot with VGA=791 parameter (initial boot was without VGA= parameter)
- compile kernel without FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set (I also
unset FB_VIRTUAL, but without its boot param that should
On Tue, 2007-10-09 at 11:39 -0600, Grant Likely wrote:
> On 10/8/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > On Mon, 2007-10-08 at 22:43 -0600, Grant Likely wrote:
> > > BTW, what path do framebuffer patches take to get into Linus' tree?
> > > Does
On Tue, 2007-10-09 at 11:39 -0600, Grant Likely wrote:
On 10/8/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Mon, 2007-10-08 at 22:43 -0600, Grant Likely wrote:
BTW, what path do framebuffer patches take to get into Linus' tree?
Does he pull your tree directly, or do they go through
On Mon, 2007-10-08 at 22:43 -0600, Grant Likely wrote:
> On 10/2/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > On Mon, 2007-10-01 at 09:57 -0600, Grant Likely wrote:
> > > Assuming there are no major issues, I'd like to get this patch series
> > >
On Tue, 2007-10-09 at 00:05 +0200, Pavel Machek wrote:
> Hi!
>
> I played with powertop a bit, and found a fairly interesting failure
> mode. If I boot init=/bin/bash vga=1, I get ~2 wakeups a second, nice.
>
> When I boot init=/bin/bash vga=791 (vesa framebuffer), most wakeups
> are caused by
On Tue, 2007-10-09 at 01:31 +0200, Jan Engelhardt wrote:
> On Oct 9 2007 07:12, Antonino A. Daplas wrote:
> >>
> >> References: http://lkml.org/lkml/2007/4/1/162
> >>http://lkml.org/lkml/2007/10/5/199
> >
> >This is quite a long thread :-)
>
&
On Sat, 2007-10-06 at 22:09 +0200, Jan Engelhardt wrote:
> Colored kernel message output (1/2)
>
> This patch makes it possible to give kernel messages a selectable
> color. It can be chosen at compile time, overridden at boot time,
> and changed at run time.
>
> References:
On Sat, 2007-10-06 at 22:09 +0200, Jan Engelhardt wrote:
Colored kernel message output (1/2)
This patch makes it possible to give kernel messages a selectable
color. It can be chosen at compile time, overridden at boot time,
and changed at run time.
References:
On Tue, 2007-10-09 at 01:31 +0200, Jan Engelhardt wrote:
On Oct 9 2007 07:12, Antonino A. Daplas wrote:
References: http://lkml.org/lkml/2007/4/1/162
http://lkml.org/lkml/2007/10/5/199
This is quite a long thread :-)
It was a patch series after all. But as Greg puts
On Tue, 2007-10-09 at 00:05 +0200, Pavel Machek wrote:
Hi!
I played with powertop a bit, and found a fairly interesting failure
mode. If I boot init=/bin/bash vga=1, I get ~2 wakeups a second, nice.
When I boot init=/bin/bash vga=791 (vesa framebuffer), most wakeups
are caused by cursor
On Mon, 2007-10-08 at 22:43 -0600, Grant Likely wrote:
On 10/2/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Mon, 2007-10-01 at 09:57 -0600, Grant Likely wrote:
Assuming there are no major issues, I'd like to get this patch series
queued up for inclusion in 2.6.24.
Okay.
Tony
On Mon, 2007-10-01 at 09:57 -0600, Grant Likely wrote:
> (resend due to mailer issues. Apologies to anyone receiving this twice)
>
> This patch series reworks the Xilinx framebuffer driver and then adds
> an of_platform bus binding. The of_platform bus binding is needed to use
> the driver in
On Mon, 2007-10-01 at 09:57 -0600, Grant Likely wrote:
(resend due to mailer issues. Apologies to anyone receiving this twice)
This patch series reworks the Xilinx framebuffer driver and then adds
an of_platform bus binding. The of_platform bus binding is needed to use
the driver in
On Sat, 2007-09-29 at 10:36 +0200, Jan Engelhardt wrote:
> Make the vt return to the system default when it is reset.
> Also make UTF-8 the system default.
It's about time we do, so this is fine with me.
Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Sat, 2007-09-29 at 10:36 +0200, Jan Engelhardt wrote:
Make the vt return to the system default when it is reset.
Also make UTF-8 the system default.
It's about time we do, so this is fine with me.
Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On Fri, 2007-09-28 at 22:03 +0200, Santiago Garcia Mantinan wrote:
> Hi!
>
> I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
> and I came out with a not working (almost black) vga text console.
>
> This is what I'm getting on my logs:
>
> Console: colour dummy
On Mon, 2007-09-24 at 23:25 -0700, Randy Dunlap wrote:
> Is there some reason that we don't put all video gfx config in one
> place? Is the split just historical, based on subdirectory locations,
> or is there a bigger reason for it?
Just historical, based on subdirectory locations. Someone did
On Wed, 2007-09-26 at 11:43 +0800, Bryan Wu wrote:
> From: Michael Hennerich <[EMAIL PROTECTED]>
> Date: Wed, 26 Sep 2007 11:33:01 +0800
> Subject: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device
> driver for a SHARP LQ043T1DG01 TFT LCD
>
> Signed-off-by: Michael Hennerich
On Wed, 2007-09-26 at 11:43 +0800, Bryan Wu wrote:
From: Michael Hennerich [EMAIL PROTECTED]
Date: Wed, 26 Sep 2007 11:33:01 +0800
Subject: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device
driver for a SHARP LQ043T1DG01 TFT LCD
Signed-off-by: Michael Hennerich [EMAIL
On Mon, 2007-09-24 at 23:25 -0700, Randy Dunlap wrote:
Is there some reason that we don't put all video gfx config in one
place? Is the split just historical, based on subdirectory locations,
or is there a bigger reason for it?
Just historical, based on subdirectory locations. Someone did
On Fri, 2007-09-28 at 22:03 +0200, Santiago Garcia Mantinan wrote:
Hi!
I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
and I came out with a not working (almost black) vga text console.
This is what I'm getting on my logs:
Console: colour dummy device 80x25
On Thu, 2007-09-20 at 02:26 -0400, ben soo wrote:
> Antonino A. Daplas wrote:
> > On Tue, 2007-09-18 at 03:26 -0400, ben soo wrote:
> >> i've 2 servers with old PCI VGA cards, one using X86_64 kernel
> >> version 2.6.23-rc5 and one with i386 kernel version
On Thu, 2007-09-20 at 02:26 -0400, ben soo wrote:
Antonino A. Daplas wrote:
On Tue, 2007-09-18 at 03:26 -0400, ben soo wrote:
i've 2 servers with old PCI VGA cards, one using X86_64 kernel
version 2.6.23-rc5 and one with i386 kernel version 2.6.23-rc6,
both wired into the same CRT via
On Tue, 2007-09-18 at 03:26 -0400, ben soo wrote:
> i've 2 servers with old PCI VGA cards, one using X86_64 kernel
> version 2.6.23-rc5 and one with i386 kernel version 2.6.23-rc6,
> both wired into the same CRT via a KVM switch.
Is this new? If yes, what's the version of the last working
On Tue, 2007-09-18 at 03:26 -0400, ben soo wrote:
i've 2 servers with old PCI VGA cards, one using X86_64 kernel
version 2.6.23-rc5 and one with i386 kernel version 2.6.23-rc6,
both wired into the same CRT via a KVM switch.
Is this new? If yes, what's the version of the last working kernel?
On Sun, 2007-08-26 at 21:09 +0200, Michal Januszewski wrote:
> On Wed, Jul 18, 2007 at 11:18:15PM +0800, Antonino A. Daplas wrote:
>
> How about modifying it so that it looks for a mode with the highest
> refresh rate if either a non-generic modedb is used or
> info.monspecs.{vf
On Sun, 2007-08-26 at 21:09 +0200, Michal Januszewski wrote:
On Wed, Jul 18, 2007 at 11:18:15PM +0800, Antonino A. Daplas wrote:
How about modifying 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
On Mon, 2007-08-13 at 12:07 -0700, Joe Perches wrote:
>
> INTEL FRAMEBUFFER DRIVER (excluding 810 and 815)
> P:Sylvain Meyer
> M:[EMAIL PROTECTED]
>
Maybe Dave?
> IMS TWINTURBO FRAMEBUFFER DRIVER
> P:Paul Mundt
> M:[EMAIL PROTECTED]
That's not Paul's current email.
Tony
-
On Mon, 2007-08-13 at 12:07 -0700, Joe Perches wrote:
INTEL FRAMEBUFFER DRIVER (excluding 810 and 815)
P:Sylvain Meyer
M:[EMAIL PROTECTED]
Maybe Dave?
IMS TWINTURBO FRAMEBUFFER DRIVER
P:Paul Mundt
M:[EMAIL PROTECTED]
That's not Paul's current email.
Tony
-
To
On Sun, 2007-08-05 at 20:11 +0800, Jeff Chua wrote:
> On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> > Also, please submit your .config and kernel command line.
>
> # cat /proc/cmdline
>
> BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
>
>
Can you try with
On Sun, 2007-08-05 at 20:11 +0800, Jeff Chua wrote:
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Also, please submit your .config and kernel command line.
# cat /proc/cmdline
BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
Can you try with the boot
On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
> Linus Torvalds wrote:
> >
> > On Sat, 4 Aug 2007, Jeff Chua wrote:
> >> On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
> After resume from s2ram or switching to console from X, my console is
> messed up on rc1 and rc2. Is there
On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
Linus Torvalds wrote:
On Sat, 4 Aug 2007, Jeff Chua wrote:
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
On Thu, 2007-08-02 at 22:33 -0400, Daniel Drake wrote:
> Antonino A. Daplas wrote:
> > How about this patch?
> >
> > Tony
> > ---
> >
> > Subject: video setup: Fix VBE DDC reading
> >
> > Add memory operand constraint and write-only modifi
H. Peter Anvin wrote:
> Antonino A. Daplas wrote:
>> On Wed, 2007-08-01 at 09:54 +0800, Antonino A. Daplas wrote:
>>> On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
>>>> Zwane Mwaikambo wrote:
>>>>> Sorry if this has been hashed out before, bu
H. Peter Anvin wrote:
Antonino A. Daplas wrote:
On Wed, 2007-08-01 at 09:54 +0800, Antonino A. Daplas wrote:
On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
Zwane Mwaikambo wrote:
Sorry if this has been hashed out before, but could you point me
towards the gentoo bugzilla entry? I'm
On Thu, 2007-08-02 at 22:33 -0400, Daniel Drake wrote:
Antonino A. Daplas wrote:
How about this patch?
Tony
---
Subject: video setup: Fix VBE DDC reading
Add memory operand constraint and write-only modifier to the inline
assembly to effect the writing of the EDID block
On Wed, 2007-08-01 at 09:54 +0800, Antonino A. Daplas wrote:
> On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
> > Zwane Mwaikambo wrote:
> > > Sorry if this has been hashed out before, but could you point me towards
> > > the gentoo bugzilla entry? I'm trying t
On Wed, 2007-08-01 at 09:54 +0800, Antonino A. Daplas wrote:
On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
Zwane Mwaikambo wrote:
Sorry if this has been hashed out before, but could you point me towards
the gentoo bugzilla entry? I'm trying to understand how your setup broke
On Tue, 2007-07-31 at 11:13 +0800, Huang, Ying wrote:
> +
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +
> +#include
> +
I don't see any
On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
> Zwane Mwaikambo wrote:
> > Sorry if this has been hashed out before, but could you point me towards
> > the gentoo bugzilla entry? I'm trying to understand how your setup broke.
> > Which version VBE does your system have?
>
> Here's the
On Tue, 2007-07-31 at 19:58 -0400, Daniel Drake wrote:
> Hi,
>
> H. Peter Anvin wrote:
> >> So, 2.6.22-rc6-mm1 should work fine with CONFIG_FIRMWARE_EDID=y, or are
> >> further patches needed?
> >>
> >
> > It should, yes.
>
> It didn't work, and the bug still exists in 2.6.23-rc1: the
On Tue, 2007-07-31 at 19:58 -0400, Daniel Drake wrote:
Hi,
H. Peter Anvin wrote:
So, 2.6.22-rc6-mm1 should work fine with CONFIG_FIRMWARE_EDID=y, or are
further patches needed?
It should, yes.
It didn't work, and the bug still exists in 2.6.23-rc1: the resolution
is wrong by 6
On Tue, 2007-07-31 at 21:17 -0400, Daniel Drake wrote:
Zwane Mwaikambo wrote:
Sorry if this has been hashed out before, but could you point me towards
the gentoo bugzilla entry? I'm trying to understand how your setup broke.
Which version VBE does your system have?
Here's the bug:
On Tue, 2007-07-31 at 11:13 +0800, Huang, Ying wrote:
+
+#include linux/delay.h
+#include linux/errno.h
+#include linux/fb.h
+#include linux/kernel.h
+#include linux/init.h
+#include linux/ioport.h
+#include linux/mm.h
+#include linux/module.h
+#include linux/platform_device.h
On Tue, 2007-07-31 at 04:48 +0900, Paul Mundt wrote:
> On Sun, Jul 29, 2007 at 01:39:51AM +0100, Adrian McMenamin wrote:
> This looks fine to me in any event. I can either wrap this up in my tree
> or Tony can include it with his next set of updates if he has any other
> concerns. Thanks, Adrian.
On Tue, 2007-07-31 at 04:48 +0900, Paul Mundt wrote:
On Sun, Jul 29, 2007 at 01:39:51AM +0100, Adrian McMenamin wrote:
This looks fine to me in any event. I can either wrap this up in my tree
or Tony can include it with his next set of updates if he has any other
concerns. Thanks, Adrian.
On Sat, 2007-07-28 at 10:14 +0800, Antonino A. Daplas wrote:
> On Sat, 2007-07-28 at 02:06 +0100, Adrian McMenamin wrote:
> > On 28/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> >
> > >
> tmp = transp << var->transp.offset | red << var-
On Sat, 2007-07-28 at 02:06 +0100, Adrian McMenamin wrote:
> On 28/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
>
> >
> But certainly better at 16bpp
>
> Can mess about with it later to see if I can get the colours right I suppose.
>
You c
On Sat, 2007-07-28 at 01:32 +0100, Adrian McMenamin wrote:
> On 28/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-07-27 at 23:25 +0100, Adrian McMenamin wrote:
> > > On 27/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > > >
On Fri, 2007-07-27 at 23:25 +0100, Adrian McMenamin wrote:
> On 27/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote:
> > > On 27/07/07, Adrian McMenamin <[EMAIL PROTECTED]> wrote:
> > >
&g
On Fri, 2007-07-27 at 20:47 +0100, Adrian McMenamin wrote:
> On 26/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
>
> >
> > I'm also confused. Can you change the color depth to 32 bpp ('fbset
> > -depth 32')? I'm thinking of a possible pseudo_palette over
On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote:
> On 27/07/07, Adrian McMenamin <[EMAIL PROTECTED]> wrote:
>
> > With the patch reverted and 24bpp, it oopses before freezing (with two
> > odd looking boot logos on the screen):
> >
> Tested this further and it fails on:
>
> rev =
On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote:
On 27/07/07, Adrian McMenamin [EMAIL PROTECTED] wrote:
With the patch reverted and 24bpp, it oopses before freezing (with two
odd looking boot logos on the screen):
Tested this further and it fails on:
rev =
On Fri, 2007-07-27 at 20:47 +0100, Adrian McMenamin wrote:
On 26/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
I'm also confused. Can you change the color depth to 32 bpp ('fbset
-depth 32')? I'm thinking of a possible pseudo_palette overrun.
The code behaves in exactly
On Fri, 2007-07-27 at 23:25 +0100, Adrian McMenamin wrote:
On 27/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote:
On 27/07/07, Adrian McMenamin [EMAIL PROTECTED] wrote:
With the patch reverted and 24bpp, it oopses before
On Sat, 2007-07-28 at 01:32 +0100, Adrian McMenamin wrote:
On 28/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Fri, 2007-07-27 at 23:25 +0100, Adrian McMenamin wrote:
On 27/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin
On Sat, 2007-07-28 at 02:06 +0100, Adrian McMenamin wrote:
On 28/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
But certainly better at 16bpp
Can mess about with it later to see if I can get the colours right I suppose.
You can start with pvr2fb_setcolreg() and pvr2fb_set_pal_entry
On Sat, 2007-07-28 at 10:14 +0800, Antonino A. Daplas wrote:
On Sat, 2007-07-28 at 02:06 +0100, Adrian McMenamin wrote:
On 28/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
tmp = transp var-transp.offset | red var-red.offset |
green var-green.offset | blue var
On Tue, 2007-07-24 at 22:45 +0100, Adrian McMenamin wrote:
> On 23/07/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> > On Sun, 2007-07-22 at 19:41 +0100, Adrian McMenamin wrote:
> > > I ma having problems with the pvr2 fb on the Dreamcast in 2.6.22-git17
> >
On Tue, 2007-07-24 at 22:45 +0100, Adrian McMenamin wrote:
On 23/07/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
On Sun, 2007-07-22 at 19:41 +0100, Adrian McMenamin wrote:
I ma having problems with the pvr2 fb on the Dreamcast in 2.6.22-git17
- when the code is executed it appears
On Mon, 2007-07-23 at 14:07 +0200, Gabriel C wrote:
> Antonino A. Daplas wrote:
> > On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
> >> Hi,
> >>
> >> I got this warning on current git:
> >>
> >> ...
> >>
> >
On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
> Hi,
>
> I got this warning on current git:
>
> ...
>
> drivers/video/console/fbcon.c:130: warning: 'map_override' defined but not
> used
>
> ...
>
> Signed-off-by: Gabriel Craciunescu <[EMAIL PROTECTED]>
>
> ---
>
> diff --git
On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
Hi,
I got this warning on current git:
...
drivers/video/console/fbcon.c:130: warning: 'map_override' defined but not
used
...
Signed-off-by: Gabriel Craciunescu [EMAIL PROTECTED]
---
diff --git
On Mon, 2007-07-23 at 14:07 +0200, Gabriel C wrote:
Antonino A. Daplas wrote:
On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
Hi,
I got this warning on current git:
...
drivers/video/console/fbcon.c:130: warning: 'map_override' defined but not
used
...
Signed-off
On Sun, 2007-07-22 at 19:41 +0100, Adrian McMenamin wrote:
> I ma having problems with the pvr2 fb on the Dreamcast in 2.6.22-git17
> - when the code is executed it appears to lock the Dreamcast up.
>
> The problem seems to be:
>
> fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, );
>
> In
On Sun, 2007-07-22 at 12:20 +0200, Geert Uytterhoeven wrote:
> On Sat, 21 Jul 2007, Antonino A. Daplas wrote:
> > On Fri, 2007-07-20 at 23:27 +0200, Sam Ravnborg wrote:
> > > Fix following section mismatch warning:
> > > WARNING: vmlinux.o(.text+0x121e62):
On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
> Hi,
>
> I got this warning on current git:
>
> ...
>
> drivers/video/console/fbcon.c:130: warning: 'map_override' defined but not
> used
>
> ...
>
> Signed-off-by: Gabriel Craciunescu <[EMAIL PROTEC
On Sun, 2007-07-22 at 12:20 +0200, Geert Uytterhoeven wrote:
On Sat, 21 Jul 2007, Antonino A. Daplas wrote:
On Fri, 2007-07-20 at 23:27 +0200, Sam Ravnborg wrote:
Fix following section mismatch warning:
WARNING: vmlinux.o(.text+0x121e62): Section mismatch: reference to
.init.text
On Sun, 2007-07-22 at 18:23 +0200, Gabriel C wrote:
Hi,
I got this warning on current git:
...
drivers/video/console/fbcon.c:130: warning: 'map_override' defined but not
used
...
Signed-off-by: Gabriel Craciunescu [EMAIL PROTECTED]
Acked-by: Antonino Daplas [EMAIL PROTECTED
On Sun, 2007-07-22 at 19:41 +0100, Adrian McMenamin wrote:
I ma having problems with the pvr2 fb on the Dreamcast in 2.6.22-git17
- when the code is executed it appears to lock the Dreamcast up.
The problem seems to be:
fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, event);
In
e code it seems that vgacon_scrollback_startup() is only
> called during the init phase so the reference to the .init.text
> section is OK.
> Teach modpost not to warn using ___init_refok.
>
> Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
Acked-by: Antonino Daplas <[EMAIL PROTECTED]>
T
that vgacon_scrollback_startup() is only
called during the init phase so the reference to the .init.text
section is OK.
Teach modpost not to warn using ___init_refok.
Signed-off-by: Sam Ravnborg [EMAIL PROTECTED]
Acked-by: Antonino Daplas [EMAIL PROTECTED]
Tony
-
To unsubscribe from this list: send the line
On Wed, 2007-07-18 at 10:38 -0700, H. Peter Anvin wrote:
> Antonino A. Daplas wrote:
> >
> >> What about the VBE 3.0 arbitrary vertical refresh rate thing?
> >
> > This is not implemented by the video-vesa.c because it will require
> > complex calculatio
On Wed, 2007-07-18 at 19:59 +0300, Matan Ziv-Av wrote:
> On Wed, 18 Jul 2007, Antonino A. Daplas wrote:
>
> > So, one cannot just set any mode, unless that mode is already defined in
> > the BIOS mode table. In VBE 3.0, you might be able to choose an
> > arbitra
On Wed, 2007-07-18 at 16:38 +0200, Ondrej Zajicek wrote:
> On Wed, Jul 18, 2007 at 10:41:02AM +0200, Michal Januszewski wrote:
> > 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
On Wed, 2007-07-18 at 17:52 +0300, Al Boldi wrote:
> Antonino A. Daplas wrote:
> > On Wed, 2007-07-18 at 16:45 +0300, Al Boldi wrote:
> > > Antonino A. Daplas wrote:
> > > > On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
> > > > > Geert Uytterhoeven
On Wed, 2007-07-18 at 16:45 +0300, Al Boldi wrote:
> Antonino A. Daplas wrote:
> > On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
> > > Geert Uytterhoeven wrote:
> > > > On Wed, 18 Jul 2007, Sasa Ostrouska wrote:
> > >
> > > Is there any techni
On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
> Geert Uytterhoeven wrote:
> > On Wed, 18 Jul 2007, Sasa Ostrouska wrote:
> Is there any technical reason why vesafb shouldn't support non-BIOS modes?
>
vesafb can only use modes included by the vendor in the card's BIOS. The
mode table
On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
Geert Uytterhoeven wrote:
On Wed, 18 Jul 2007, Sasa Ostrouska wrote:
Is there any technical reason why vesafb shouldn't support non-BIOS modes?
vesafb can only use modes included by the vendor in the card's BIOS. The
mode table contains
On Wed, 2007-07-18 at 16:45 +0300, Al Boldi wrote:
Antonino A. Daplas wrote:
On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
Geert Uytterhoeven wrote:
On Wed, 18 Jul 2007, Sasa Ostrouska wrote:
Is there any technical reason why vesafb shouldn't support non-BIOS
modes
On Wed, 2007-07-18 at 17:52 +0300, Al Boldi wrote:
Antonino A. Daplas wrote:
On Wed, 2007-07-18 at 16:45 +0300, Al Boldi wrote:
Antonino A. Daplas wrote:
On Wed, 2007-07-18 at 13:42 +0300, Al Boldi wrote:
Geert Uytterhoeven wrote:
On Wed, 18 Jul 2007, Sasa Ostrouska wrote
On Wed, 2007-07-18 at 16:38 +0200, Ondrej Zajicek wrote:
On Wed, Jul 18, 2007 at 10:41:02AM +0200, Michal Januszewski wrote:
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
On Wed, 2007-07-18 at 19:59 +0300, Matan Ziv-Av wrote:
On Wed, 18 Jul 2007, Antonino A. Daplas wrote:
So, one cannot just set any mode, unless that mode is already defined in
the BIOS mode table. In VBE 3.0, you might be able to choose an
arbitrary vertical refresh rate, but that's
On Wed, 2007-07-18 at 10:38 -0700, H. Peter Anvin wrote:
Antonino A. Daplas wrote:
What about the VBE 3.0 arbitrary vertical refresh rate thing?
This is not implemented by the video-vesa.c because it will require
complex calculations of mode timings (such as with GTF) to be done
On Tue, 2007-07-17 at 16:13 +0200, Sasa Ostrouska wrote:
> Hi ,
>
> I want to ask one question about a custom resolution in the console.
> I have a Sony Vaio Laptop VGN-SZ2VP/X, the screen resolution is
> 1280x800, now I'm using the vga=773 which is an 1024x768 but this is
> ugly as I get a
On Tue, 2007-07-17 at 16:13 +0200, Sasa Ostrouska wrote:
Hi ,
I want to ask one question about a custom resolution in the console.
I have a Sony Vaio Laptop VGN-SZ2VP/X, the screen resolution is
1280x800, now I'm using the vga=773 which is an 1024x768 but this is
ugly as I get a border of
On Sat, 2007-07-14 at 17:05 -0400, Andrew Paprocki wrote:
> Tony,
>
> Do you have the patch working already? I'd love to try this out in the
> meantime on the LX system I am developing with at the moment. I'm
> assuming you worked this into the existing Arcom framework (gxfb) and
> pulled the
On Sat, 2007-07-14 at 15:01 -0400, Andrew Paprocki wrote:
> Is there any reason why the GPL framebuffer driver for the GX/GX1/LX
> directly from AMD is not integrated into the kernel and only a custom
> driver for only the GX/GX1 written by Arcom exists?
> (drivers/video/geode/*)
>
> If you have
On Sat, 2007-07-14 at 15:01 -0400, Andrew Paprocki wrote:
Is there any reason why the GPL framebuffer driver for the GX/GX1/LX
directly from AMD is not integrated into the kernel and only a custom
driver for only the GX/GX1 written by Arcom exists?
(drivers/video/geode/*)
If you have an LX,
On Sat, 2007-07-14 at 17:05 -0400, Andrew Paprocki wrote:
Tony,
Do you have the patch working already? I'd love to try this out in the
meantime on the LX system I am developing with at the moment. I'm
assuming you worked this into the existing Arcom framework (gxfb) and
pulled the necessary
On Fri, 2007-07-13 at 08:58 +0200, Geert Uytterhoeven wrote:
> On Fri, 13 Jul 2007, Antonino A. Daplas wrote:
> > On Tue, 2007-07-10 at 14:27 +0200, Geert Uytterhoeven wrote:
> > > --- a/include/linux/linux_logo.h
> > > +++ b/include/linux/linux_logo.h
> > >
On Fri, 2007-07-13 at 08:56 +0200, Geert Uytterhoeven wrote:
> On Fri, 13 Jul 2007, Antonino A. Daplas wrote:
> > On Tue, 2007-07-10 at 14:27 +0200, Geert Uytterhoeven wrote:
> > > --- a/drivers/video/fbmem.c
> > > +++ b/drivers/video/fbmem.c
> > > @@ -318,
On Fri, 2007-07-13 at 08:58 +0200, Geert Uytterhoeven wrote:
On Fri, 13 Jul 2007, Antonino A. Daplas wrote:
On Tue, 2007-07-10 at 14:27 +0200, Geert Uytterhoeven wrote:
--- a/include/linux/linux_logo.h
+++ b/include/linux/linux_logo.h
@@ -33,5 +33,13 @@ struct linux_logo
On Fri, 2007-07-13 at 08:56 +0200, Geert Uytterhoeven wrote:
On Fri, 13 Jul 2007, Antonino A. Daplas wrote:
On Tue, 2007-07-10 at 14:27 +0200, Geert Uytterhoeven wrote:
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
@@ -318,6 +318,13 @@ static struct logo_data {
const
1 - 100 of 478 matches
Mail list logo
