| To: | "Anoop P.A." <Anoop_P.A@pmc-sierra.com> |
|---|---|
| Subject: | Re: TITAN GE driver |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Wed, 2 Jun 2010 09:32:56 +0100 |
| Cc: | linux-mips <linux-mips@linux-mips.org> |
| In-reply-to: | <A7DEA48C84FD0B48AAAE33F328C0201404E2DC94@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca> |
| References: | <A7DEA48C84FD0B48AAAE33F328C0201404E2D834@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca> <20100528162722.GB7148@linux-mips.org> <A7DEA48C84FD0B48AAAE33F328C0201404E2DC94@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.20 (2009-08-17) |
On Wed, Jun 02, 2010 at 01:10:17AM -0700, Anoop P.A. wrote: > >From the datasheets and design discussion it looks like prefix has been > designed to be static i.e they are expecting all buffers to get > allocated with same prefix. In another words all the buffers should be > below < 0x1fff_ffff ( physical address) or between 0x2000_0000 and > 0x3fff_ffff like that. > > Is there any way to force kmalloc to allocate memory in certain region > or below some region? Nothing that would uniformly work for 32-bit and 64-bit kernels and also Linux only has flags that allocate below certain addresses; nothing that tells the allocator "give me something between 0x20000000 and 0x3fffffff". Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: TITAN GE driver, Anoop P.A. |
|---|---|
| Next by Date: | [PATCH v2] MIPS: Unify the suffix of compressed vmlinux.bin, Wu Zhangjin |
| Previous by Thread: | RE: TITAN GE driver, Anoop P.A. |
| Next by Thread: | RE: TITAN GE driver, Anoop P.A. |
| Indexes: | [Date] [Thread] [Top] [All Lists] |