All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Dan Malek <dan@embeddededge.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Kumar Gala <kumar.gala@motorola.com>,
	Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx-2.6 | Prolog
Date: Fri, 28 May 2004 09:40:08 +0300	[thread overview]
Message-ID: <40B6DEC8.2070605@intracom.gr> (raw)
In-Reply-To: <B89F9AE2-AFF4-11D8-89B7-003065F9B7DC@embeddededge.com>


Dan Malek wrote:

>
> On May 26, 2004, at 8:05 AM, Pantelis Antoniou wrote:
>
>> Awaiting comments.
>
>
> The interrupt stuff in patch 1 was wrong when it was done in 2.4
> and I'm disappointed to see it again in 2.6.  Unfortunately, I
> don't have time to fix it now, but it will get done properly when I
> implement the similar thing for the 8560.

Well, I had to do something. request_8xxirq & friends are unusable.

>
> In patch 4, get rid of that #if 0 around the machine check exception.
> If the code works, just check it in.  We can't define update_mmu_cache
> as a null function.  It performs a necessary function of cache
> management.  We may just be lucky because the caches on the 8xx
> are small, but this is a subtle bug waiting to happen.

OK for the #if 0.
I don't know what update_mmu_cache really does that screws up so bad.
Didn't really had to look into the matter.

>
> Why did you need to include patch 5 and 6?  These should have
> been done and checked into the trees long ago.

For completeness. So that with the patches in it would at least compile.

>
> In patch 8, why is the 8xx FEC driver dependent upon NETTA and
> NETPHONE?  All 8xx boards should use this driver, and it would have
> been nice if you would have done board specific files for all other
> 8xx boards that are supported, even if they couldn't be tested.  The
> price of making such major changes that affect everyone :-)

Well, as I explained to Tom, that was intentional :).

How many of the boards in the kernel are working,
or have someone working on them?

IMHO it's time to clean up the mess a bit.

>
> I did not check these in.  Tom can you do so and make sure other
> 8xx boards will at least compile?  I'll fix up the stuff I don't like
> later :-)
>
> Thanks.
>
>     -- Dan
>
Regards

Pantelis


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

  parent reply	other threads:[~2004-05-28  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 12:05 8xx-2.6 | Prolog Pantelis Antoniou
2004-05-26 15:36 ` Dan Malek
2004-05-26 15:55   ` Tom Rini
2004-05-26 16:39     ` Dan Malek
2004-05-26 17:40 ` Marcelo Tosatti
2004-05-27 15:44 ` Dan Malek
2004-05-27 16:39   ` Joakim Tjernlund
2004-05-27 22:34   ` Tom Rini
2004-05-31  9:31     ` Pantelis Antoniou
2004-05-28  6:40   ` Pantelis Antoniou [this message]
2004-05-31  1:59     ` Song Sam

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=40B6DEC8.2070605@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dan@embeddededge.com \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 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.