[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Fwd: Draft for extensible multiboot header]
From: |
Gregg C Levine |
Subject: |
RE: [Fwd: Draft for extensible multiboot header] |
Date: |
Fri, 17 Oct 2003 23:57:02 -0400 |
Hello from Gregg C Levine
Sorry to hear that it went unnoticed on the other list. It looks good
to me. Have you had a chance to test this idea, on a kernel? Here's a
suggestion. If you have the resources that is. Compile a kernel, one
of the latest 2.4.x ones, and apply that collection of statements to
it. There's a method for convincing a Linux kernel to become multiboot
header amendable, but I don't remember it.
-------------------
Gregg C Levine address@hidden
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
> -----Original Message-----
> From: address@hidden
[mailto:bug-
> address@hidden On Behalf Of
Barry
> deFreese
> Sent: Friday, October 17, 2003 11:42 PM
> To: address@hidden
> Subject: [Fwd: Draft for extensible multiboot header]
>
> Well I sent this to pupa-devel and didn't hear much. Does anyone
here
> have an opinion??
>
> Thanks!
>
> -------- Original Message --------
> Subject: Draft for extensible multiboot header
> Date: Wed, 15 Oct 2003 17:41:32 -0400
> From: <address@hidden>
> Reply-To: address@hidden
> To: address@hidden
>
>
>
> Hello,
>
> I have started on trying to create a more extensible boot header.
Here is what I have
> so far:
>
> struct mbv2_header
> {
> unsigned magic;
> unsigned header_addr;
> unsigned load_addr;
> unsigned load_end_addr;
> unsigned bss_end_addr;
> unsigned entry_addr;
> mbv2_flag_t flags;
> };
>
> struct mbv2_flag
> {
> mbv2_flag_t type;
> size_t length;
> char data[0];
> };
>
> typedef mbv2_flag mbv2_flag_t;
>
> Flag is probably not the appropriate term at this point. But it
begs the question. Are
> any flags "required" that could not be replaced with this structure?
Obviously I am
> missing the enum for the mbv2_flag_type_t also.
>
> Any thoughts? As I have said before, I am a n00b so please don't be
too harsh on
> me!! :-)
>
> Thanks,
>
> Barry deFreese
> H4XX0r Wannabe
>
>
>
> _______________________________________________
> Pupa-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/pupa-devel
>
>
>
> --
> Barry deFreese
> Debian 3.0r1 "Woody"
> GNU/Hurd
> Registered Linux "Newbie" #302256 - Hurd H4XX0r wannabe
>
> "Programming today is a race between software engineers striving
> to build bigger and better idiot-proof programs, and the Universe
> trying to produce bigger and better idiots. So far, the Universe is
> winning." Rich Cook.
>
>
>
>
>
>
> _______________________________________________
> Bug-grub mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-grub