From: Michel Lanners <mlan@cpu.lu>
To: panto@intracom.gr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Status of linuxppc_2.5
Date: Wed, 8 Jan 2003 23:15:35 +0100 (CET) [thread overview]
Message-ID: <E18WOU9-00009Z-00@piglet.grunz.lu> (raw)
In-Reply-To: <3E1BECD2.9060909@intracom.gr>
On 8 Jan, this message from Pantelis Antoniou echoed through cyberspace:
> I'm trying to compile linuxppc_2.5
> and the following patch is needed to
> make it compile.
Tried to compile my standard kernel compile a while back, and found the
following things broken (didn't have time to try fixing yet...):
- 53c94 Mac SCSI
- Matroxfb
I also didn't try very hard to compile in face of these problems; there
may be others still.
Sorry I can't provide more info, but maybe this discussion makes ore
people interested in 2.5 status, where I think a number of PPC-related
things need to be seriously looked at, hopefully before it is declared
2.6...
Cheers
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-08 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 9:18 Status of linuxppc_2.5 Pantelis Antoniou
2003-01-08 17:32 ` Boris Bezlaj
2003-01-08 18:18 ` Benjamin Herrenschmidt
2003-01-08 18:22 ` Boris Bezlaj
2003-01-08 18:34 ` Benjamin Herrenschmidt
2003-01-08 19:30 ` Boris Bezlaj
2003-01-09 8:13 ` Pantelis Antoniou
2003-01-09 8:30 ` Brad Boyer
2003-01-08 22:15 ` Michel Lanners [this message]
2003-01-08 21:46 ` Benjamin Herrenschmidt
2003-01-08 23:11 ` Paul Mackerras
2003-01-12 17:14 ` Michel Lanners
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=E18WOU9-00009Z-00@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=panto@intracom.gr \
/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).