* RE: 8xx-2.6 | Prolog
2004-05-27 15:44 ` Dan Malek
@ 2004-05-27 16:39 ` Joakim Tjernlund
2004-05-27 22:34 ` Tom Rini
2004-05-28 6:40 ` Pantelis Antoniou
2 siblings, 0 replies; 11+ messages in thread
From: Joakim Tjernlund @ 2004-05-27 16:39 UTC (permalink / raw)
To: Dan Malek, Pantelis Antoniou; +Cc: Tom Rini, Kumar Gala, Linuxppc-Embedded
> In patch 4, get rid of that #if 0 around the machine check exception.
> If the code works, just check it in.
The machine check part has already been checked in by Paul.
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: 8xx-2.6 | Prolog
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
2 siblings, 1 reply; 11+ messages in thread
From: Tom Rini @ 2004-05-27 22:34 UTC (permalink / raw)
To: Dan Malek; +Cc: Pantelis Antoniou, Kumar Gala, Linuxppc-Embedded
On Thu, May 27, 2004 at 11:44:21AM -0400, Dan Malek wrote:
>
> On May 26, 2004, at 8:05 AM, Pantelis Antoniou wrote:
>
> >Awaiting comments.
[snip]
> ... 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.
Are you certain? This is something in 2.4, and while I am having weird
problems locally (that I can't rule out as being hw issues), adding that
change in is what gets me a working init=/bin/bash.
> 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 :-)
I'm going to be checking this all in momentarily. On my system right
now, I can get both of my rpxlite's to init=/bin/bash, mostly working,
if and only if I use the new uart driver and if I configure it for SMC1
AND SCC1 (which seems wrong).
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: 8xx-2.6 | Prolog
2004-05-27 22:34 ` Tom Rini
@ 2004-05-31 9:31 ` Pantelis Antoniou
0 siblings, 0 replies; 11+ messages in thread
From: Pantelis Antoniou @ 2004-05-31 9:31 UTC (permalink / raw)
To: Tom Rini; +Cc: Dan Malek, Kumar Gala, Linuxppc-Embedded
Tom Rini wrote:
>On Thu, May 27, 2004 at 11:44:21AM -0400, Dan Malek wrote:
>
>
>
>>On May 26, 2004, at 8:05 AM, Pantelis Antoniou wrote:
>>
>>
>>
>>>Awaiting comments.
>>>
>>>
>[snip]
>
>
>>... 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.
>>
>>
>
>Are you certain? This is something in 2.4, and while I am having weird
>problems locally (that I can't rule out as being hw issues), adding that
>change in is what gets me a working init=/bin/bash.
>
>
>
>>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 :-)
>>
>>
>
>I'm going to be checking this all in momentarily. On my system right
>now, I can get both of my rpxlite's to init=/bin/bash, mostly working,
>if and only if I use the new uart driver and if I configure it for SMC1
>AND SCC1 (which seems wrong).
>
>
>
Problem persists.
While it no longer crashes it is unbearably slow.
I suspect that it does not update properly the page
tables on a data/instruction access fault.
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: 8xx-2.6 | Prolog
2004-05-27 15:44 ` Dan Malek
2004-05-27 16:39 ` Joakim Tjernlund
2004-05-27 22:34 ` Tom Rini
@ 2004-05-28 6:40 ` Pantelis Antoniou
2004-05-31 1:59 ` Song Sam
2 siblings, 1 reply; 11+ messages in thread
From: Pantelis Antoniou @ 2004-05-28 6:40 UTC (permalink / raw)
To: Dan Malek; +Cc: Tom Rini, Kumar Gala, Linuxppc-Embedded
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: 8xx-2.6 | Prolog
2004-05-28 6:40 ` Pantelis Antoniou
@ 2004-05-31 1:59 ` Song Sam
0 siblings, 0 replies; 11+ messages in thread
From: Song Sam @ 2004-05-31 1:59 UTC (permalink / raw)
To: Pantelis Antoniou, Dan Malek; +Cc: Tom Rini, Kumar Gala, Linuxppc-Embedded
Pantelis Antoniou <panto@intracom.gr> wrote:
> > Dan Malek wrote:
> > 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.
I tested External Interrupt of 823e with
request_8xxirq on IRQ1-IRQ7 in 2.4.18(MVL3.0-rpxlite
BSP) last night.It did work.But I failed many times to
make PCMCIA IP_B7 interrupt work,which should be
treated as External Interrupt--registered fine but
without any response to IP_B7 change.
I wonder whether "interrupt stuff" as you metioned had
any relation with my case.
Sorry for disturbing you all! :-)
Sam
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 11+ messages in thread