From: Pantelis Antoniou <panto@intracom•gr>
To: Joakim Tjernlund <joakim.tjernlund@lumentis•se>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Merge 8xx to Linus tree?
Date: Fri, 29 Oct 2004 15:54:00 +0300 [thread overview]
Message-ID: <41823D68.1090100@intracom.gr> (raw)
In-Reply-To: <JPEALJAFNGDDLOPNDIEEEEMOCNAA.joakim.tjernlund@lumentis.se>
Joakim Tjernlund wrote:
>>Joakim Tjernlund wrote:
>>
>>
>>>>On Thu, Oct 14, 2004 at 04:53:49PM +0200, Joakim Tjernlund wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Is it not time to merge 8xx from linuxppc-2.5 into Linus tree?
>>>>>
>>>>>I know the 8xx is not fully functional yet but this isn't done
>>>>>soon I think it won't happen at all. The 8xx arch can be made to
>>>>>depend on BROKEN in Linus tree to make it clear that it isn't
>>>>>working properly yet.
>>>>>
>>>>>
>>>>>
>>>>I've been the hard-ass about holding back on moving 8xx forward. Once
>>>>2.6.9 finally comes out (assuming and hoping that Linus really intends
>>>>to do a release and not -rc5), I'll start moving stuff over and make it
>>>>depend on BROKEN hopefully in time for 2.6.10-rc1.
>>>>
>>>>--
>>>>Tom Rini
>>>>
>>>>
>>>>
>>>Any progress?
>>>
>>>Jocke
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs•org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>>
>>>
>>>
>>>
>>I'm currently battling to make 2.6.10-rc1 work the same way it used do.
>>
>>But something changed in slab management and the kmallocs in request_irq
>>called by init_IRQ fails.
>>
>
>hmm, I think I saw something about that in the www log for Linus kernel. It is offline so
>I can't check now.
>
>The www I/F for both Linus tree(http://linux.bitkeeper.com/) and the ppc tree(http://ppc.bitkeeper.com/)
>are offline alot. Anyone who knows whats going on?
>
> Jocke
>
>
>
Found the bug.
IRQ code is now common for all arches, but ppc used a special
irq_kmalloc routine, since request irq was called very early.
The generic code just calls straight kmalloc, which obviously craps out
when too early.
Lets see what can I do to fix it...
BTW I'm curious if any embedded PPC actually works on 2.6.10...
Regards
Pantelis
next prev parent reply other threads:[~2004-10-29 12:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 14:53 Merge 8xx to Linus tree? Joakim Tjernlund
2004-10-14 22:16 ` Tom Rini
2004-10-14 22:29 ` Joakim Tjernlund
2004-10-14 22:25 ` Robert P. J. Day
2004-10-14 22:41 ` Tom Rini
2004-10-17 11:03 ` Robert P. J. Day
2004-10-17 12:30 ` Dale Farnsworth
2004-10-18 3:21 ` Dan Malek
2004-10-18 14:49 ` Tom Rini
2004-10-15 8:16 ` Robert P. J. Day
2004-10-29 12:07 ` Joakim Tjernlund
2004-10-29 12:12 ` Pantelis Antoniou
2004-10-29 12:27 ` Joakim Tjernlund
2004-10-29 12:54 ` Pantelis Antoniou [this message]
2004-10-29 14:22 ` Tom Rini
2004-10-29 14:23 ` Pantelis Antoniou
2004-10-29 14:35 ` Joakim Tjernlund
2004-10-29 14:49 ` Tom Rini
2004-10-29 14:53 ` Joakim Tjernlund
2004-10-29 14:19 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 14:44 Rune Torgersen
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=41823D68.1090100@intracom.gr \
--to=panto@intracom$(echo .)gr \
--cc=joakim.tjernlund@lumentis$(echo .)se \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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