linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: the door is closing for 2.4
Date: Thu, 04 Dec 2003 08:55:44 -0500	[thread overview]
Message-ID: <3FCF3CE0.4020008@embeddededge.com> (raw)
In-Reply-To: 3FCEFB59.80300@intracom.gr


Pantelis Antoniou wrote:

> However I don't think that 2.6 works for 8xx at all.

It doesn't.

> What is the status of 2.6 for 8xx?

It's a f'ing mess.

> Does someone intent to do it, or should I try to give it a shot?

I intended to do it, but I'm so busy with non-PPC stuff I never
finshed much of anything.

Right now, it won't even compile because all of the drivers need
updates, then we need the usual processor dependent porting stuff
done.  I have a pretty good idea what needs to be done, it's just
more work than the few weekends I thought it would take.

If someone wants to get the drivers to compile, I'll continue working
on the processor specific parts and maybe we can get it done soon.

Thanks.



	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-12-04 13:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  0:34 the door is closing for 2.4 Paul Mackerras
2003-12-04  9:16 ` Pantelis Antoniou
2003-12-04 13:55   ` Dan Malek [this message]
2003-12-04 15:06     ` Pantelis Antoniou
2003-12-04 15:34       ` Dan Malek
2003-12-05  7:24         ` Pantelis Antoniou
2003-12-05 18:54           ` Dan Malek
2003-12-04  9:47 ` Stefan Roese
2003-12-05  0:08 ` Kumar Gala
2004-01-12  5:30   ` Paul Mackerras
2003-12-10 15:38 ` Hubert Figuiere
2003-12-10 16:55   ` Tom Rini
2003-12-10 16:57     ` Hubert Figuiere
2003-12-10 19:19       ` Tom Rini

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=3FCF3CE0.4020008@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=panto@intracom.gr \
    --cc=paulus@samba.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).