From: Martin Costabel <costabel@wanadoo.fr>
To: Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: cvs.on.openprojects.net status?
Date: Tue, 10 Aug 1999 13:01:34 +0200 [thread overview]
Message-ID: <37B0068E.C8853FC3@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.3.96L.990809183523.5833A-100000@unix47.andrew.cmu.edu
Hollis R Blanchard wrote:
>
> What's the deal with the CVS tree? The kernel I compiled from it a week or so
> ago has a very screwed platinumfb driver, but now the cvs server
> cvs.on.openprojects.net does not exist. www.openprojects.net has moved to
> openprojects.nu, but no mention made of CVS anywhere...
>
> Is it just a matter of waiting for it to get set up again, or should I be
> looking elsewhere?
The cvs server is alive again now, and the linux_2_2 branch has moved to
2.2.11 with a great many updates.
The kernel doesn't compile, though. There is a new line
EXPORT_SYMBOL(init_task_union);
in kernel/ksyms.c which conflicts with the same line in
arch/ppc/kernel/ppc_ksyms.c. One of the two has to go.
The kernel compiles then. It doesn't boot, though. On my 6400, it gets
as far as
INIT: version 2.74 booting
and then hangs. The 2.2.10 compiled with the same config options boots
OK.
Seems that not much testing for the PPC is going on for the vger tree.
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-10 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-09 22:37 cvs.on.openprojects.net status? Hollis R Blanchard
1999-08-10 2:51 ` Paul Barrette
1999-08-10 11:01 ` Martin Costabel [this message]
1999-08-10 11:22 ` Geert Uytterhoeven
1999-08-10 15:31 ` Hollis R Blanchard
1999-08-10 15:41 ` Geert Uytterhoeven
1999-08-10 20:29 ` Tom Rini
1999-08-10 22:14 ` Martin Costabel
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=37B0068E.C8853FC3@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=hollis+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).