From: Martin Dalecki <dalecki@evision-ventures.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 boot enhancements, boot bean counting 8/11
Date: Wed, 17 Apr 2002 18:18:59 +0200 [thread overview]
Message-ID: <3CBDA073.6010700@evision-ventures.com> (raw)
In-Reply-To: <m1elhegt1c.fsf@frodo.biederman.org>
Eric W. Biederman wrote:
> Linus please apply,
>
> Rework the actual build/link step for kernel images.
> - remove the need for objcopy
> - Kill the ROOT_DEV Makefile variable, the implementation
> was only half correct and there are much better ways
> to specify your root device than modifying the kernel Makefile.
> - Don't loose information when the executable is built
Coudl you please use sufficiently large fields for kdev_t variables?
This way if we once have bigger device id spaces one will not have
to mess with the boot code again.
Thank you.
> +
> +struct boot_params {
> + uint8_t reserved1[0x1f1]; /* 0x000 */
> + uint8_t setup_sects; /* 0x1f1 */
> + uint16_t mount_root_rdonly; /* 0x1f2 */
> + uint16_t syssize; /* 0x1f4 */
> + uint16_t swapdev; /* 0x1f6 */
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
this should be uint32_t
> + uint16_t ramdisk_flags; /* 0x1f8 */
> +#define RAMDISK_IMAGE_START_MASK 0x07FF
> +#define RAMDISK_PROMPT_FLAG 0x8000
> +#define RAMDISK_LOAD_FLAG 0x4000
> + uint16_t vid_mode; /* 0x1fa */
> + uint16_t root_dev; /* 0x1fc */
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
this should be uint32_t
next prev parent reply other threads:[~2002-04-17 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 16:59 [PATCH] x86 boot enhancements, boot bean counting 8/11 Eric W. Biederman
2002-04-17 16:18 ` Martin Dalecki [this message]
2002-04-17 17:37 ` Eric W. Biederman
2002-04-18 7:57 ` Martin Dalecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CBDA073.6010700@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox