On Tuesday 20 September 2005 01:11 am, Vesa Jääskeläinen wrote:
> Perhaps you mixed this with vbeinfo code itself? Because in
> grub_vbe_probe (in video/i386/pc/vbe.c) there has been grub_memcpy to
> copy this information from scratch to local static variable
> (controller_info) and then if caller
Yoshinori K. Okuji wrote:
> On Sunday 18 September 2005 11:03 pm, Vesa Jääskeläinen wrote:
>> Sorry it took a bit longer to check those out, but after returning from
>> my vacation it took some time to get back to normal day life.
>
> Presumably you didn't sleep enough in your airplain...
For the
On Sunday 18 September 2005 11:03 pm, Vesa Jääskeläinen wrote:
> Sorry it took a bit longer to check those out, but after returning from
> my vacation it took some time to get back to normal day life.
Presumably you didn't sleep enough in your airplain...
> I would like to know why did you add ch
Yoshinori K. Okuji wrote:
> On Sunday 14 August 2005 16:48, Yoshinori K. Okuji wrote:
>> On Sunday 14 August 2005 13:52, Vesa Jääskeläinen wrote:
>>> I have attached patch here that adds simple terminal that uses VESA BIOS
>>> Extension 2.0+ for rendering terminal. It is not meant to be included as
On Sunday 14 August 2005 16:48, Yoshinori K. Okuji wrote:
> On Sunday 14 August 2005 13:52, Vesa Jääskeläinen wrote:
> > I have attached patch here that adds simple terminal that uses VESA BIOS
> > Extension 2.0+ for rendering terminal. It is not meant to be included as
> > is in GRUB 2, but I woul
Marco Gerards wrote:
>> Just a note until admins fix those commit messages, first version of vbe
>> terminal support is now committed. It still needs more work, but it is a
>> starting point.
>
> Cool! If you do receive the commit messages, can you forward them so
> we could see them as well?
I
Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
> Marco Gerards wrote:
>> Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
>>
There are some long lines, can you please make them shorter so
the maximal line length is 78 characters?
>>> Hmm... I made another scan for those. Still I left some o
Vincent Pelletier <[EMAIL PROTECTED]> writes:
> On the IEEE1275 point of view, I saw framebuffer graphic primitives in
> the standard, so it *should* be easy too. And on my sun, there is a
> mouse device in the OB tree.
Right, same for EFI.
> Marco Gerards wrote:
>> Right, but it would be the be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Gerards wrote:
> Perhaps we can get help and suggestions from designers instead of
> programmers. Perhaps we can contact Ubuntu, they have designers.
> Perhaps a KDE or gnome team?
Gnoppix has a really nice - Grub legacy - graphic menu, so I th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yoshinori K. Okuji wrote:
> A pluggable menu might sound good, but it's not so easy to maintain multiple
> menu interfaces.
I think we should only maintain some kind of API interface with an
example module, and let the community develop on it if it f
Yoshinori K. Okuji wrote:
> Anyway, I expect that we will not have to wait too long to see what we want
> to
> do with a fancy menu, since Vesa is very fast to implement the code.
> Hopefully, we will see the first working version in this month or next month.
> Once it starts working, the disc
Marco Gerards wrote:
> Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
>
>>> There are some long lines, can you please make them shorter so
>>> the maximal line length is 78 characters?
>> Hmm... I made another scan for those. Still I left some of those there
>> because in my opinion it is much more
Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
>> There are some long lines, can you please make them shorter so
>> the maximal line length is 78 characters?
>
> Hmm... I made another scan for those. Still I left some of those there
> because in my opinion it is much more readable in that way. But
Marco Gerards wrote:
> Some comments on the patch:
>
>> 2005-08-14 Vesa Jaaskelainen <[EMAIL PROTECTED]>
>>
>> +* DISTLIST: Added term/i386/pc/vesafb.c
>> +* term/i386/pc/vesafb: New file.
>
> Can you please split this up to the generic framebuffer terminal? The
> terminal for frame
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Monday 15 August 2005 19:41, Marco Gerards wrote:
>> It would be nice if GUI's can be distributed as plugins...
>
> Maybe. This kind of change is easy to make later, so I'd like to stick to a
> hardcoded menu interface for now. First of all, I
On Monday 15 August 2005 19:41, Marco Gerards wrote:
> It would be nice if GUI's can be distributed as plugins...
Maybe. This kind of change is easy to make later, so I'd like to stick to a
hardcoded menu interface for now. First of all, I must make it perfectly
working with internationalized te
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Monday 15 August 2005 18:06, Vladimir Serbinenko wrote:
>> We don't need to make the whole thing absolutely skinnable (just the
>> basic skins)
>> if we make like I proposed (menus like terminals, in modules) because if
>> someone wants to
>> c
On Monday 15 August 2005 18:06, Vladimir Serbinenko wrote:
> We don't need to make the whole thing absolutely skinnable (just the
> basic skins)
> if we make like I proposed (menus like terminals, in modules) because if
> someone wants to
> change completely the look he can just write a new menu mo
Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
Hi Vesa,
> I have attached patch here that adds simple terminal that uses VESA BIOS
> Extension 2.0+ for rendering terminal. It is not meant to be included as
> is in GRUB 2, but I would hope that people would test it, so I could try
> to improve it f
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Sunday 14 August 2005 18:47, Vladimir Serbinenko wrote:
>> But we need to let the room for the future growth. One of far-looking
>> plans is
>> "eye-candy" menu interface and we don't know yet what we will put there.
>
> Good point. Just to giv
Vladimir Serbinenko <[EMAIL PROTECTED]> writes:
>> -mouse handling (??)
>>
> It must not be difficult: we can just port mouse.com from FreeDos or use
> any other
> mouse implementation. But here we also need the general interface because
> there are different mouse types: PS/2, USB, serial (old PC
On Monday 15 August 2005 17:52, Vesa Jääskeläinen wrote:
> Now only problem is what is the best location for vbe.c that would
> contain helper functions for modules that needs VBE. Currently I have it
> in term/i386/pc/vbe.c but is there better location for this?
It would be better to create a new
Vincent Pelletier wrote:
> Yoshinori K. Okuji wrote:
>
> >Just to give you some ideas,
>
>
> Same here :) (from simple to ambitious) :
> -Pictures corresponding to entries (set a background/in front
> of/near/instead of)
> -customisable positions for menu entries (ubuntu could out them in
> circle
>I see four options here:
>
>1) design graphics drivers interface and register it when loading
>module. Pros is that it is easy to write new graphics drivers. Cons is
>that we need to have then virtual screen support (not hard to make).
>
>
>
Perhaps the best way
>2) improve terminal interface.
Yoshinori K. Okuji wrote:
> On Sunday 14 August 2005 23:48, Vesa Jääskeläinen wrote:
>> As far I know, GRUB 2 doesn't support dynamic loading of function entry
>> points, instead there are only two predefined entry points that can be
>> called from modules so there has to be some interface for thos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yoshinori K. Okuji wrote:
> Just to give you some ideas,
Same here :) (from simple to ambitious) :
- -Pictures corresponding to entries (set a background/in front
of/near/instead of)
- -customisable positions for menu entries (ubuntu could out them in
On Sunday 14 August 2005 23:48, Vesa Jääskeläinen wrote:
> As far I know, GRUB 2 doesn't support dynamic loading of function entry
> points, instead there are only two predefined entry points that can be
> called from modules so there has to be some interface for those if they
> are not implemented
Vladimir Serbinenko wrote:
> Vesa Jääskeläinen wrote:
>
>> I can try to draft out features that I think is needed and then we can
>> see what is still missing and when it is good enough then implement it.
>>
> But we need to let the room for the future growth. One of far-looking
> plans is
> "eye-
On Sunday 14 August 2005 18:47, Vladimir Serbinenko wrote:
> But we need to let the room for the future growth. One of far-looking
> plans is
> "eye-candy" menu interface and we don't know yet what we will put there.
Good point. Just to give you some ideas, I attach an imaginary screenshot of a
f
Vesa Jääskeläinen wrote:
>I can try to draft out features that I think is needed and then we can
>
>
>see what is still missing and when it is good enough then implement it.
>
>
>
But we need to let the room for the future growth. One of far-looking
plans is
"eye-candy" menu interface and we d
Yoshinori K. Okuji wrote:
>> First one is that there should be common virtual terminal for all arch's
>> and then separate graphics drivers that will do the actual drawing. In
>> this patch this is all implemented in one module and it is not as pretty
>> as it could be.
>
> Another way is to emula
On Sunday 14 August 2005 13:52, Vesa Jääskeläinen wrote:
> I have attached patch here that adds simple terminal that uses VESA BIOS
> Extension 2.0+ for rendering terminal. It is not meant to be included as
> is in GRUB 2, but I would hope that people would test it, so I could try
> to improve it f
Hi,
I have attached patch here that adds simple terminal that uses VESA BIOS
Extension 2.0+ for rendering terminal. It is not meant to be included as
is in GRUB 2, but I would hope that people would test it, so I could try
to improve it for greater compatibility (even though I have tried to
follow
33 matches
Mail list logo
