From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: new irq works status (#2)
Date: Fri, 30 Jun 2006 17:50:55 +1000 [thread overview]
Message-ID: <1151653855.13194.9.camel@localhost.localdomain> (raw)
I uploaded a new version at http://gate.crashing.org/~benh/irq-WIP/
This one applies on top of a linus git checkout from today and thus
should also apply on top of a recent powerpc.git tree. It contains
various fixes & cleanups over the previous ones, significant fixes in
the mpic code (mpic based pseries work now) and powermac 64 bits is
ported over.
Remaining bits are:
- PowerMac 32 bits. There is a bit of work to replace the old
workarounds for broken device-trees
here, those used to be done by changing device_node->intrs which is
now gone
- Maple (should be trivial, +/- a small nit for some SLOF version)
- CHRP (should be really trivial :) Just need to be careful of Pegasos
lack of a valid
interrupt-tree and properly default to the PCI_INTERRUPT_LINE config
space register
in that case, which shall match 8259 interrupts
- embedded6xx/* platforms. I'll leave the pleasure of fixing these to
the maintainers for now
unless I decide to beat them to it, but since I'm not too familiar,
I'd rather have them do
the job. It should be fairly trivial to just make them work. The next
step though is to make
them _use_ the new stuff which will probably involve device-tree
updates.
I expect to have PowerMac32 and possibly CHRP fixed tomorrow and will
proceed to the merge asap, leaving Maple and embedded6xx as "to be fixed
before 2.6.18 is finished".
I'd appreciate review and comments.
Cheers,
Ben.
next reply other threads:[~2006-06-30 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 7:50 Benjamin Herrenschmidt [this message]
2006-06-30 7:57 ` new irq works status (#2) Benjamin Herrenschmidt
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=1151653855.13194.9.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).