[Top] [All Lists]

Re: DISCONTIGMEM suuport on 32 bits MIPS

To: Ralf Baechle <>
Subject: Re: DISCONTIGMEM suuport on 32 bits MIPS
From: Franck <>
Date: Fri, 30 Sep 2005 14:40:31 +0200
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V4DqR6OaY3zdWju5MZ8RdnIKEoMuN4DK32LkSrPDIadIcceFzpgexUEPltaDGjElQSrXbCtGxtMkY+SBc/cd811WgcBbv37NVXg0R8uUjX1O7hSszEil4DMAe5xNKnJuY1xlFQo1VhuExwpthod3RF3UmE/z0v7n4Ksm665vTtc=
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <>
Reply-to: Franck <>
2005/9/30, Ralf Baechle <>:
> On Mon, Sep 26, 2005 at 02:46:02PM +0200, Franck wrote:
> > > IP27 currently the only system that absolutely needs discontiguous
> > > memory in order to work at all.  A few other systems could make use of
> > > discontiguous memory to reduce the waste of memory - the family of
> > > Broadcom SB1 based systems comes to mind.
> >
> > Isn't discontiguous memory common for embedded system as well ? I
> > thought so...Anyways can we make discontiguous memory thing move into
> > generic MIPS code so every future needs for that will profit ? I
> > looked at other arch, and they seem to implement it that way (in
> > arch/xxx/mm/discontig.c).
> Yes, that would be a good thing.  There are several platforms that could
> make good use of discontiguous memory support such as Broadcom's Sibyte
> SoCs with their insanely large hole in the memory map but also others.

Ok I'll try to do that soon (maybe in 1 or 2 weeks). I looked at the
ARM's code and I should be able to do the same on MIPS. Should I keep
IP27 data structure and code although ARM's ones seem to be easier to
understand ?


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