From: Franck <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: DISCONTIGMEM suuport on 32 bits MIPS
Date: Fri, 30 Sep 2005 14:40:31 +0200 [thread overview]
Message-ID: <cda58cb80509300540i7a419fb8u@mail.gmail.com> (raw)
In-Reply-To: <20050929235025.GC3983@linux-mips.org>
2005/9/30, Ralf Baechle <ralf@linux-mips.org>:
> 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 ?
Thanks
--
Franck
next prev parent reply other threads:[~2005-09-30 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 9:16 DISCONTIGMEM suuport on 32 bits MIPS Franck
2005-09-26 12:21 ` Ralf Baechle
2005-09-26 12:46 ` Franck
2005-09-29 23:50 ` Ralf Baechle
2005-09-30 12:40 ` Franck [this message]
2005-09-30 13:49 ` Ralf Baechle
2005-09-30 15:35 ` Franck
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=cda58cb80509300540i7a419fb8u@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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