As I said here:
http://mail.gnu.org/archive/html/bug-grub/2003-11/msg2.html
video mode switching must be deferred until giving control to a loaded
OS. Otherwise, I cannot merge your patch with the official version.
Okuji
___
Bug-grub mailing lis
: Saturday, January 03, 2004 23:30
Subject: Re: VBE support for multiboot kernels
Hi,
On Sat Jan 03, 2004 at 00:59:07 +0200, Durand Miller wrote:
> For the last few months, I've been using a modified grub version to switch
> into vesa modes as part as my os development hobby. Since g
Hi,
On Sat Jan 03, 2004 at 00:59:07 +0200, Durand Miller wrote:
> For the last few months, I've been using a modified grub version to switch
> into vesa modes as part as my os development hobby. Since getting this kind
> of functionality required some coding and modification of grub, I'm pretty
>
Hi,
Here's a patch which adds partial support for the VBE part of the multiboot
specification:
http://www.djm.co.za/spoon/grub-setvbe.2004-01-02.patch
The patch applies to the CVS tree from today (2004-01-02) and it does the
following:
1. Adds a new command "setvbe" which switches the graphics
Sorry, messed that up.
Attached is the working patch.
Alex
On Wednesday 21 November 2001 18:23, Alexander Thiel wrote:
> Hello,
>
> here is the VBE patch against the current CVS. I did my best to write a
> conforming ChangeLog entry. Let me know if there is something wrong - it's
> the first ti
I wanted it for my own toy kernel, I
> > have added it myself. I could not find any hint about ongoing work for
> > VBE support in the mailing list archive, so I decided to post my patch
> > (against grub-0.90). It moves some existing code around and adds some new
> > chunks. H
At Tue, 13 Nov 2001 19:43:01 +0100,
Alexander Thiel wrote:
> Ok, no problem. Would you prefer a patch against the CVS version?
Yeah.
Okuji
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
, I
> > have added it myself. I could not find any hint about ongoing work for
> > VBE support in the mailing list archive, so I decided to post my patch
> > (against grub-0.90). It moves some existing code around and adds some new
> > chunks. Here is a summary of the change
At Tue, 13 Nov 2001 12:37:29 +0100,
Alexander Thiel wrote:
> as the latest version of GRUB did not support VBE graphics as decribed in the
> multiboot specification, but I wanted it for my own toy kernel, I have added
> it myself. I could not find any hint about ongoing work for VBE s
Hi all,
as the latest version of GRUB did not support VBE graphics as decribed in the
multiboot specification, but I wanted it for my own toy kernel, I have added
it myself. I could not find any hint about ongoing work for VBE support in
the mailing list archive, so I decided to post my patch
From: Vesa Jääskeläinen <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Thu, 23 Nov 2000 22:01:37 +0200 (EET)
> What did you found? Did it work correctly?
I'm sorry, but I have been quite busy these days. So I haven't
tested it yet. However, I've checked in your pat
On Mon, 13 Nov 2000, OKUJI Yoshinori wrote:
> > Probably by wrongly coded bios implementation. But without linear-flag
> > in get mode request you still get correct information needed to work with
> > mode. Only requirement is to use linear-flag in set mode. Usually on mode
> > query you should o
From: Vesa Jääskeläinen <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Sun, 12 Nov 2000 21:56:27 +0200 (EET)
> Probably by wrongly coded bios implementation. But without linear-flag
> in get mode request you still get correct information needed to work with
> mode. Only requir
On Fri, 10 Nov 2000, OKUJI Yoshinori wrote:
> > diff -r1.97 builtins.c
> > 4064c4064
> > < if (get_vbe_mode_info (mode_number | (1 << 14), &mode) != 0x004F
> > ---
> > > if (get_vbe_mode_info (mode_number /*| (1 << 14)*/, &mode) != 0x004F
> > 4306c4306
> > < if (get_vbe_mode_info (*mode
From: Vesa Jääskeläinen <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Thu, 9 Nov 2000 20:17:29 +0200 (EET)
> diff -r1.97 builtins.c
> 4064c4064
> < if (get_vbe_mode_info (mode_number | (1 << 14), &mode) != 0x004F
> ---
> > if (get_vbe_mode_inf
From: Jan Fricke <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Thu, 09 Nov 2000 17:40:05 +0100
> diff -ur grub.org/stage2/asm.S grub/stage2/asm.S
> --- grub.org/stage2/asm.S Mon Nov 6 07:42:26 2000
> +++ grub/stage2/asm.S Thu Nov 9 17:29:17 2000
>
On Wed, 8 Nov 2000, OKUJI Yoshinori wrote:
> > what kinda test "picture" we should see here?
>
> Quite meaningless animation. That's just a test, really.
oh sorry... forgot to post new report after mods...
I also included /proc/pci info here...
Graphics card: Maxigamer Phoenix (Voodoo Bansh
On Wed, 8 Nov 2000, OKUJI Yoshinori wrote:
> > what kinda test "picture" we should see here?
>
> Quite meaningless animation. That's just a test, really.
I needed Jan Fricke's setmode fix and my own fix to get it
working... and now I got "scrolling" color sycle...
here is attached cvs diff gr
Hallo!
I applied the following patch (...to the current cvs version):
diff -ur grub.org/stage2/asm.S grub/stage2/asm.S
--- grub.org/stage2/asm.S Mon Nov 6 07:42:26 2000
+++ grub/stage2/asm.S Thu Nov 9 17:29:17 2000
@@ -1679,7 +1679,7 @@
/* Save the mode number in %bx */
From: Jan Fricke <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Wed, 08 Nov 2000 12:12:05 +0100
> lighted). I'm not shure, but I think the last working version was
> 0.5.95. Is there any opportunity to trace the versions in little steps,
> so that the problem can be ca
Hallo!
> > Sorry, forgot to test "testvbe".
>
> Please do.
Gives some kind of color cycling (for all 9 modes) and after pressing a
key it returns to a 40x25 text mode.
> Don't hesitate to send a bug report. Are you sure that your problem
> is the same as a known bug? Otherwise, please tell u
From: Vesa Jääskeläinen <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Wed, 8 Nov 2000 01:47:10 +0200 (EET)
> what kinda test "picture" we should see here?
Quite meaningless animation. That's just a test, really.
Okuji
On Sun, 5 Nov 2000, OKUJI Yoshinori wrote:
> 2. Run the command "testvbe" with a VBE mode number. This will switch
> to the mode you specify. The command restores the original text mode,
> when you hit any key.
what kinda test "picture" we should see here? ... after lil mods to code I
did get ev
From: Jan Fricke <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Tue, 07 Nov 2000 08:56:59 +0100
> Using Matrox G400 I got the following output:
Thanks for your report!
> Sorry, forgot to test "testvbe".
Please do.
> Couldn't test this with an older
> Try using the very latest grub from CVS. It fixed the problem for me.
> I have used snapshot from Nov 2nd...
>
I used the one from Nov 6th...
Best wishesJan
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/
On Tue, Nov 07 2000, Jan Fricke wrote:
> Hallo!
> Using Matrox G400 I got the following output:
>
> grub> vbeprobe
> VBE version 2.0
> 0x100: Packed pixel, 640x400x8
> 0x101: Packed pixel, 640x480x8
> 0x103: Packed pixel, 800x600x8
> 0x110: Direct Color, 640x480x16
> 0x111: Direct Col
Hallo!
Using Matrox G400 I got the following output:
grub> vbeprobe
VBE version 2.0
0x100: Packed pixel, 640x400x8
0x101: Packed pixel, 640x480x8
0x103: Packed pixel, 800x600x8
0x110: Direct Color, 640x480x16
0x111: Direct Color, 640x480x16
0x112: Direct Color, 640x480x32
0x113: Di
On Sun, 5 Nov 2000, OKUJI Yoshinori wrote:
> 1. Run the command "vbeprobe" with no argument. This will show the
> version number of your VBE card, and the list of VBE modes supported
> by your card.
nice...
--- clip ---
grub> vbeprobe
VBE version 3.0
grub>
--- clip ---
with my own test progr
On Mon, 6 Nov 2000, OKUJI Yoshinori wrote:
> > when you want to set specific video mode then you must search it and
> > not just say I want mode 0x103 (in vbe 1.2 that was 800x600x256).
> > in vbe 2.0+ mode numbers in different video cards doesn't have to
> > be same.
>
> What are you talking
From: Vesa Jääskeläinen <[EMAIL PROTECTED]>
Subject: Re: VBE support
Date: Sun, 5 Nov 2000 22:32:58 +0200 (EET)
> I didn't test it yet but some comments about code...
Any comments are welcome, but I strongly recommend trying it first,
because it tends to be misleading that you
On Sun, 5 Nov 2000, OKUJI Yoshinori wrote:
> I've added VBE support right now. This is not enough for real use
> yet, but I checked it in, because it is necessary to test the code in
> various environments. I tested it only for ELSA ERAZOR X2 which
> supports VBE 3.0.
I didn&
On Sun, 5 Nov 2000, Christoph Plattner wrote:
> Sorry for the silly question, but what is VBE ?
As okuji pointed out url for more specs about it, in basics
it is "standard" programming interface for developer to support
different graphics cards in different video modes with same code.
in exampl
From: Christoph Plattner <[EMAIL PROTECTED]>
Subject: Re: VBE support - what is it ?
Date: Sun, 05 Nov 2000 10:15:08 +0100
> Sorry for the silly question, but what is VBE ?
Don't mind. Ignorance is not a bad thing. VBE is the acronym of VESA
BIOS EXTENSION. See <http://ww
Sorry for the silly question, but what is VBE ?
With friendly regards
Christoph
OKUJI Yoshinori wrote:
>
> I've added VBE support right now. This is not enough for real use
> yet, but I checked it in, because it is necessary to test the code in
> various environm
I've added VBE support right now. This is not enough for real use
yet, but I checked it in, because it is necessary to test the code in
various environments. I tested it only for ELSA ERAZOR X2 which
supports VBE 3.0.
If you are willing to test it, follow this instruction:
1. Ru
35 matches
Mail list logo
