Implementing commands from TODO list

Implementing commands from TODO list

[Bandan]

First thing's first; I finally realized while getting my daily dose of grub2 
that I had unintentionally tried to post my message in a wrong thread 
here :
http://lists.gnu.org/archive/html/grub-devel/2009-01/msg00157.html 

It was very careless on my part and I sincerely apologize for the noise 
(sorry phcoder and Vesa Jääskeläinen ! ).

Now to my point:

I was looking at the TODO list here http://grub.enbug.org/TodoList into 
the list of missing commands http://grub.enbug.org/CommandList. As I 
see that there is not much talk about  them on the list, I would like to 
track the missing commands and start adding them to Grub2. 
Personally, I would like to start with "uppermem" as I have already 
gone through the relevant code and it will be easier for me to start with 
it.

Any ideas/suggestions would be greatly appreciated.

Thanks,
Bandan
 
-- 
BSD

Re: Implementing commands from TODO list

[phcoder]

Bandan wrote:
> (sorry phcoder and Vesa Jääskeläinen ! ).
NP
> Personally, I would like to start with "uppermem" as I have already 
> gone through the relevant code and it will be easier for me to start with 
> it.
Uppermem is i386-bound. I propose more general format:
meminfo [-l] [-s VAR]
Which outputs total amount of memory.
If launched with -s VAR this value is stored to variable
If launched with -v it outputs complete memory map

Thank
Vladimir 'phcoder' Serbinenko

Re: Implementing commands from TODO list

[Bandan]

Hi!
>
> Uppermem is i386-bound. I propose more general format:
> meminfo [-l] [-s VAR]
Sounds good to me.

> Which outputs total amount of memory.
> If launched with -s VAR this value is stored to variable
> If launched with -v it outputs complete memory map
>
So, would meminfo be the equivalent of displaymem that we had in grub-legacy 
(with a few modifications) ? Is there any reason to change the command name 
from displaymem to meminfo ?

Bandan
 
-- 
BSD

Re: Implementing commands from TODO list

[phcoder]

You might want to have a look at lsmmap function
Vladimir 'phcoder' Serbinenko
Bandan wrote:
> First thing's first; I finally realized while getting my daily dose of grub2 
> that I had unintentionally tried to post my message in a wrong thread 
> here :
> http://lists.gnu.org/archive/html/grub-devel/2009-01/msg00157.html 
> 
> It was very careless on my part and I sincerely apologize for the noise 
> (sorry phcoder and Vesa Jääskeläinen ! ).
> 
> Now to my point:
> 
> I was looking at the TODO list here http://grub.enbug.org/TodoList into 
> the list of missing commands http://grub.enbug.org/CommandList. As I 
> see that there is not much talk about  them on the list, I would like to 
> track the missing commands and start adding them to Grub2. 
> Personally, I would like to start with "uppermem" as I have already 
> gone through the relevant code and it will be easier for me to start with 
> it.
> 
> Any ideas/suggestions would be greatly appreciated.
> 
> Thanks,
> Bandan
>  

Re: Implementing commands from TODO list

[Robert Millan]

On Thu, Jan 29, 2009 at 07:11:11PM -0500, Bandan wrote:
> First thing's first; I finally realized while getting my daily dose of grub2 
> that I had unintentionally tried to post my message in a wrong thread 
> here :
> http://lists.gnu.org/archive/html/grub-devel/2009-01/msg00157.html 

I already sent a reply about this to your other thread.  Please check it out.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."