linux-mips
[Top] [All Lists]

Re: patch / rfc

To: Dan Malek <dan@embeddededge.com>
Subject: Re: patch / rfc
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Fri, 26 Aug 2005 16:53:04 +0100 (BST)
Cc: ppopov@embeddedalley.com, "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
In-reply-to: <0cc66f0b0b5afa994744547699f687bf@embeddededge.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1125006681.14435.1065.camel@localhost.localdomain> <Pine.LNX.4.61L.0508261340460.9561@blysk.ds.pg.gda.pl> <1125069898.14435.1215.camel@localhost.localdomain> <0cc66f0b0b5afa994744547699f687bf@embeddededge.com>
Sender: linux-mips-bounce@linux-mips.org
On Fri, 26 Aug 2005, Dan Malek wrote:

> If you do this, I suggest using another PowerPC-ism.  They
> have a ppc_md data structure that is filled with indirect function
> pointers to machine dependent functions.  We could create
> a mips_md that does this same thing.  The reason I like this
> is it collects all machine dependent information in a single
> place, so it's easy to see what functions/data are available
> and what you may need to do.  It's also clear when used
> that anything in this structure is a machine/board dependent
> function.  In the proper places, you then do what is shown above:

 Well, that's actually Alpha-ism, which has been that port since 1998 or 
so and is a long-term plan for our multi-platform support too. :-)  If you 
want to implement it right now, please go ahead!

  Maciej

<Prev in Thread] Current Thread [Next in Thread>