From: Philippe Gerum <rpm@xenomai.org>
To: Wolfgang Grandegger <wolfgang.grandegger@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: [Adeos-main] Re: Patch/Code maintanance
Date: Thu, 03 Jun 2004 10:31:47 +0200 [thread overview]
Message-ID: <1086251506.682.28.camel@domain.hid> (raw)
In-Reply-To: <40BF7732.801@domain.hid>
On Thu, 2004-06-03 at 21:08, Wolfgang Grandegger wrote:
> Hi Philippe,
>
> I started porting ADEOS to PowerPC with "2.4r11c1" and now I want to
> catch up with "24r13c2" before I release it. I realized that there are
> quite some differences and I wonder how you maintain the ADEOS code,
> especially how do you get or handle the files in "linux" and "patches".
>
There are two major trees, one for 2.4, the other for 2.6, respectively
available under linux/v2.4 and linux/v2.6.
For each supported kernel version, I simply create some "shadow tree"
under linux/v2.x/<kernel-ver>-<arch>, only containing the kernel files
modified by Adeos.
The generic Adeos support which is the same for any version of the host
kernel in a given major branch is stored under linux/v2.x/adeos-core.
Basically, merging a kernel-specific tree with the Adeos generic support
gives you all the files applicable to a genuine kernel tree in order to
Adeos-enable it. This way, for working on Adeos, you just need to untar
the vanilla kernel tree of interest, and replace the set of affected
files by symlinks to the corresponding files in the CVS tree.
When a development milestone has been reached for a given kernel release
/ Adeos revision, I simply build a patch against the corresponding
vanilla tree, and feed patches/ with it. The same patch is then copied
to the download area on GNA, and a news is published there.
> Thanks.
>
> Wolfgang.
--
Philippe.
next prev parent reply other threads:[~2004-06-03 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 19:08 [Adeos-main] Patch/Code maintanance Wolfgang Grandegger
2004-06-03 8:31 ` Philippe Gerum [this message]
2004-06-04 8:57 ` [Adeos-main] " Wolfgang Grandegger
2004-06-03 9:09 ` Philippe Gerum
2004-06-04 15:54 ` Wolfgang Denk
2004-06-07 8:40 ` Wolfgang Grandegger
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=1086251506.682.28.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=wolfgang.grandegger@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.