linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Dan Malek <dan@embeddededge.com>
Cc: Joakim Tjernlund <joakim.tjernlund@lumentis.se>,
	Tom Rini <trini@kernel.crashing.org>, Wolfgang Denk <wd@denx.de>,
	Kumar Gala <kumar.gala@motorola.com>,
	Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] Driver for FECs on motorola DUET (87x/88x)
Date: Mon, 24 May 2004 16:40:18 +0300	[thread overview]
Message-ID: <40B1FB42.1040306@intracom.gr> (raw)
In-Reply-To: <F8A7B640-A5F0-11D8-9559-003065F9B7DC@embeddededge.com>


Dan Malek wrote:

>
> On May 14, 2004, at 8:49 AM, Pantelis Antoniou wrote:
>
>> Any mm hackers over there have any idea?
>
>
> I have some ideas.  There are some "generic" functions
> doing some lazy processing that isn't likely to be valid
> on the 8xx, in particular the way demand zero pages
> are handled.  Anyway, that's as far as I've traced it.
> Sometimes it appears to work, but it could be that what
> is happening still isn't correct, it just doesn't crash/hang.
> There are few other things that caught my attention where
> we used to execute generic PPC MM code without any
> ill side effects, but when these were ported to 2.6 we
> are now doing the wrong things on the 8xx.  We just have
> to work our way though it with some applications and
> testing.

I have made some progress...

I have ported the CPM UART driver by Kumar Gala to the 8xx.

It works correctly but still the same problem persists...

It correctly mounts the NFS root, and after the first write
by init it hangs.

By breaking in using my BDI2000 I see it stuck at default_idle.

Networking & interrupts appear OK, since I can still ping.

It seems that for some reason no user space scheduling takes place.

Apparently the scheduling is controlled by the _TIF_NEED_RESCHED
flag which is no where to be found in head_8xx.S.

Before I submerge into the assembly of head_8xx.S does anyone have any
ideas?

>
>     -- Dan
>
>
Regards

Pantelis


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

  reply	other threads:[~2004-05-24 13:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 14:42 [PATCH] Driver for FECs on motorola DUET (87x/88x) Pantelis Antoniou
     [not found] ` <40A4C04A.8060508@intracom.gr>
2004-05-14 14:22   ` Joakim Tjernlund
2004-05-14 14:14     ` Pantelis Antoniou
2004-05-14 14:48   ` Pantelis Antoniou
2004-05-14 15:23     ` Joakim Tjernlund
2004-05-14 15:18       ` Pantelis Antoniou
2004-05-14 15:32       ` Tom Rini
2004-05-14 21:52   ` Dan Malek
2004-05-24 13:40     ` Pantelis Antoniou [this message]
2004-05-24 17:18       ` Dan Malek
2004-05-24 19:11         ` Joakim Tjernlund
2004-05-25  1:10         ` Paul Mackerras
2004-05-25  9:49           ` Joakim Tjernlund
2004-05-25 10:24             ` Paul Mackerras
     [not found]         ` <40B327EF.2090903@intracom.gr>
2004-05-25 14:01           ` 2.6 on 8xx (was [PATCH] Driver for FECs on motorola DUET (87x/88x)) Robert P. J. Day
2004-05-25 14:08             ` Pantelis Antoniou
2004-05-25 15:06               ` Robert P. J. Day
     [not found] <D50B7204-AE3C-11D8-B485-003065F9B7DC@embeddededge.com>
2004-05-25 12:29 ` [PATCH] Driver for FECs on motorola DUET (87x/88x) Joakim Tjernlund

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=40B1FB42.1040306@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dan@embeddededge.com \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    --cc=wd@denx.de \
    /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).