* Reminder: removal of APUS and Gemini still pending
@ 2005-09-16 16:36 Kumar Gala
2005-09-17 14:09 ` Simon Richter
2005-09-17 19:48 ` Roman Zippel
0 siblings, 2 replies; 6+ messages in thread
From: Kumar Gala @ 2005-09-16 16:36 UTC (permalink / raw)
To: ppc-dev list
This is a reminder email to all those that care that APUS and Gemini
configs are still not building in the kernel. They are still
scheduled to be removed after the release of 2.6.15.
- kumar
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Reminder: removal of APUS and Gemini still pending
2005-09-16 16:36 Reminder: removal of APUS and Gemini still pending Kumar Gala
@ 2005-09-17 14:09 ` Simon Richter
2005-09-18 22:01 ` Paul Mackerras
2005-09-17 19:48 ` Roman Zippel
1 sibling, 1 reply; 6+ messages in thread
From: Simon Richter @ 2005-09-17 14:09 UTC (permalink / raw)
To: Kumar Gala; +Cc: ppc-dev list
Kumar Gala wrote:
> This is a reminder email to all those that care that APUS and Gemini
> configs are still not building in the kernel. They are still scheduled
> to be removed after the release of 2.6.15.
I have a tree that builds an APUS kernel (with Roman Zippel's patches
forwarded to HEAD), however I wanted to hold back with merging it until
the ppc/ppc64 -> powerpc transition is finished; also, I would like to
get proper changesets with attribution instead of a big patch (the plan
is to forward-merge the changes until after the transition, then turn
them back into a diff and apply them step by step).
Simon
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Reminder: removal of APUS and Gemini still pending
2005-09-16 16:36 Reminder: removal of APUS and Gemini still pending Kumar Gala
2005-09-17 14:09 ` Simon Richter
@ 2005-09-17 19:48 ` Roman Zippel
2005-09-18 10:27 ` Simon Richter
1 sibling, 1 reply; 6+ messages in thread
From: Roman Zippel @ 2005-09-17 19:48 UTC (permalink / raw)
To: Kumar Gala; +Cc: ppc-dev list
Hi,
Kumar Gala wrote:
> This is a reminder email to all those that care that APUS and Gemini
> configs are still not building in the kernel. They are still scheduled
> to be removed after the release of 2.6.15.
Regarding APUS: with the current rate of changes I simply don't have the
time to catch up right now. What's the game plan here? If I miss the
deadline, I have to start from scratch?
bye, Roman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Reminder: removal of APUS and Gemini still pending
2005-09-17 19:48 ` Roman Zippel
@ 2005-09-18 10:27 ` Simon Richter
0 siblings, 0 replies; 6+ messages in thread
From: Simon Richter @ 2005-09-18 10:27 UTC (permalink / raw)
To: Roman Zippel; +Cc: ppc-dev list
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
Hi,
Roman Zippel schrieb:
> Regarding APUS: with the current rate of changes I simply don't have the
> time to catch up right now. What's the game plan here? If I miss the
> deadline, I have to start from scratch?
Well, I have a tree that sort of works, but needs to be merged with the
ongoing changes, and possibly the patch should be split as well. Do you
have an archive of patches submitted to you, so they can be applied
separately?
(On a related note, are you going to be at the Oldenburg meeting this
year? I'm planning to catch up on APUS there and have some commit
objects ready at the end of it.)
Simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 374 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Reminder: removal of APUS and Gemini still pending
2005-09-17 14:09 ` Simon Richter
@ 2005-09-18 22:01 ` Paul Mackerras
2005-09-19 9:10 ` Christoph Hellwig
0 siblings, 1 reply; 6+ messages in thread
From: Paul Mackerras @ 2005-09-18 22:01 UTC (permalink / raw)
To: Simon Richter; +Cc: ppc-dev list
Simon Richter writes:
> I have a tree that builds an APUS kernel (with Roman Zippel's patches
> forwarded to HEAD), however I wanted to hold back with merging it until
> the ppc/ppc64 -> powerpc transition is finished; also, I would like to
That sounds like a mistake to me...
> get proper changesets with attribution instead of a big patch (the plan
> is to forward-merge the changes until after the transition, then turn
> them back into a diff and apply them step by step).
One of the things I particularly want to do is to remove the special
cases in the virtual<->physical address translations for APUS.
Perhaps the sparsemem or discontigmem code could be used instead?
Paul.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Reminder: removal of APUS and Gemini still pending
2005-09-18 22:01 ` Paul Mackerras
@ 2005-09-19 9:10 ` Christoph Hellwig
0 siblings, 0 replies; 6+ messages in thread
From: Christoph Hellwig @ 2005-09-19 9:10 UTC (permalink / raw)
To: Paul Mackerras; +Cc: ppc-dev list
On Mon, Sep 19, 2005 at 08:01:44AM +1000, Paul Mackerras wrote:
> That sounds like a mistake to me...
>
> > get proper changesets with attribution instead of a big patch (the plan
> > is to forward-merge the changes until after the transition, then turn
> > them back into a diff and apply them step by step).
>
> One of the things I particularly want to do is to remove the special
> cases in the virtual<->physical address translations for APUS.
> Perhaps the sparsemem or discontigmem code could be used instead?
The apus codedrop Sven put into the Debian Kernel SVN repo has this
removed, see:
http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches-debian/powerpc-apus.patch?op=file&rev=0&sc=0
even if apus folks don't want to merge now all the core touching parts
of that patch should go in as they clanup the ifdef APUS mess quite a
lot.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-09-19 9:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-16 16:36 Reminder: removal of APUS and Gemini still pending Kumar Gala
2005-09-17 14:09 ` Simon Richter
2005-09-18 22:01 ` Paul Mackerras
2005-09-19 9:10 ` Christoph Hellwig
2005-09-17 19:48 ` Roman Zippel
2005-09-18 10:27 ` Simon Richter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).