From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: cort@cs.nmt.edu, linuxppc-dev@lists.linuxppc.org,
Gabriel Paubert <paubert@iram.es>
Subject: Re: Interrupt routing in prep_pci.c
Date: Sun, 14 Feb 1999 19:06:44 -0800 (PST) [thread overview]
Message-ID: <XFMail.990214190644.jeremy@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.04.9902132334480.4390-100000@narn.local.drgw.net>
On 14-Feb-99 Troy Benjegerdes wrote:
> You may also find my patches for MTX SMP support usefull. It contains most
> of the stuff in Geert's patches, with the addition that most all of the
> architecture-dependent functions have been redone to be dispatched by a
> structure of function pointers. (Thanks to Corey Minyard) This gets rid of
> a great number of case statements, and what could be the framework for a
> good cleaning up of the arch/ppc/kernel directory. I suspect it might make
> porting to a yellowknife like board easier. If the yellowknife board
> supports SMP and has an OpenPIC, my SMP patches might work also ;)
Thanks a lot - this should be very helpful. BTW, how much work has been put
into using Open Firmware callbacks rather than blowing OFW away (I guess that's
more of a CHRP rather than PReP or MTX question)?
J
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-15 3:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-11 4:32 Interrupt routing in prep_pci.c Jeremy Fitzhardinge
1999-02-11 9:07 ` Gabriel Paubert
1999-02-14 5:42 ` Troy Benjegerdes
1999-02-15 3:06 ` Jeremy Fitzhardinge [this message]
1999-02-15 9:25 ` Gabriel Paubert
1999-02-15 9:23 ` Gabriel Paubert
1999-02-21 16:56 ` Johnnie Peters
1999-02-21 18:28 ` Cort Dougan
1999-02-22 8:45 ` VALETTE Eric
1999-02-22 18:25 ` Cort Dougan
1999-02-22 18:06 ` VALETTE Eric
1999-02-22 19:26 ` Cort Dougan
1999-02-23 8:40 ` VALETTE Eric
1999-02-23 14:53 ` Johnnie Peters
1999-02-23 15:55 ` VALETTE Eric
1999-02-26 7:18 ` Cort Dougan
1999-02-26 8:53 ` VALETTE Eric
1999-02-26 18:54 ` Cort Dougan
1999-02-26 7:09 ` bootloader problems and linux/ppc developers tree Cort Dougan
1999-02-26 9:02 ` VALETTE Eric
1999-02-26 11:05 ` Gabriel Paubert
1999-02-23 20:39 ` Interrupt routing in prep_pci.c Matt Porter
1999-02-26 7:21 ` Cort Dougan
1999-03-02 16:56 ` Matt Porter
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=XFMail.990214190644.jeremy@goop.org \
--to=jeremy@goop.org \
--cc=cort@cs.nmt.edu \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).