From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] getting started (Part 2)
Date: Mon, 19 Feb 2007 12:18:12 +0100 [thread overview]
Message-ID: <45D98774.7070400@domain.hid> (raw)
In-Reply-To: <17880.36271.503322.588359@domain.hid>
Hi
I have followed the directives of Richard and Gilles (thanks) and now
have a rough idea of what the steps should be to install Xenomai. I
still have some questions before I start.
I apologize in advance for amount of text surrounding the not so many
questions. I have tried to be a clear as possible.
A
The first part of the installation is preparing the kernel
I have 2.6.16 kernel so I have downloaded the
adeos-ipipe-2.6.16-i386-1.5-02.patch.
I have no idea what architecture I have but i386 sounds familiar. :)
How can I test what architecture I have?
Is this the correct patch?
Calling prepare-kernel.sh with its arguments seems straight-forward
after that.
B
Compiling the kernel. My biggest worry here is the configuration.
Knowing nothing of such configurations I would like to avoid having to
make uneducated guesses in this stage. Is it possible to get hold of the
current kernel configuration and load that in the
make menuconfig
stage?
If yes, how?
C
Subsequently calling
make
then
make modules_install install
What happens in this install step? What files/directories are installed
and where? Reason I ask is because I am running from liveUSB and booting
with syslinux so I will have to write the kernel image (vmlinuz on my
system) to /dev/sda1 (via where ever it is mounted of course) and not to
/boot/ on that same drive.
Another question in this regard is that my current kernel image is
called vmlinuz not bzImage the documentation talks about all the time.
What is the difference? Can I rename the bzImage to vmlinuz. Take note
of the fact that the USB has a FAT filesystem. Thus symbolic links do
not work and I instead have to make copies instead.
Then captain's universe mutters about creating the initial RAM-disk (if
I need one). How do I know whether I need one? I know that running from
a liveUSB I do need what is called initrd.gz in the boot process, but is
this what the documentation is talking about?
How do I finally set up the new kernel to be booted. Is it sufficient to
write it (vmlinuz) to the position where the current kernel image is
located? (safely renaming the current kernel image to "vmlinuz-old" of
course :))
Sorry again for so many newbie questions.
RR
Gilles Chanteperdrix wrote:
> Roland Tollenaar wrote:
> > Could anyone direct me to somewhat more
> > "my-first-xenomai&kernel-experience" instructions?
>
> Hi Roland,
>
> You will find detailed information on how to build a kernel there:
> http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
>
> Once you have read that, the instructions in Xenomai README.INSTALL
> should be enough to learn the rest.
>
> If you have some problem during the build process, do not hesitate to
> ask questions here.
>
next prev parent reply other threads:[~2007-02-19 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 17:07 [Xenomai-help] getting started Roland Tollenaar
2007-02-18 11:18 ` karre
2007-02-18 17:32 ` Gilles Chanteperdrix
2007-02-19 11:18 ` Roland Tollenaar [this message]
2007-02-19 22:16 ` [Xenomai-help] getting started (Part 2) Gilles Chanteperdrix
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=45D98774.7070400@domain.hid \
--to=rwatollenaar@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=rolandtollenaar@domain.hid \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.