[Top] [All Lists]

RE: TITAN GE driver

To: "Ralf Baechle" <>
Subject: RE: TITAN GE driver
From: "Anoop P.A." <>
Date: Wed, 2 Jun 2010 01:10:17 -0700
Cc: "linux-mips" <>
In-reply-to: <>
References: <> <>
Thread-index: Acr+gscrweuzBuNZSFmHArD+k3R8+ADpIFBA
Thread-topic: TITAN GE driver

>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?


> -----Original Message-----
> From:
>] On Behalf Of Ralf Baechle
> Sent: Friday, May 28, 2010 9:57 PM
> To: Anoop P.A.
> Cc: linux-mips
> Subject: Re: TITAN GE driver
> On Thu, May 27, 2010 at 10:51:47PM -0700, Anoop P.A. wrote:
> > Any body used titan GE device with more than 512MB physical memory?
> >
> >
> >
> > If buffer is getting allocated above physical address 0x1fff_ffff (
> > 30 bit buffer address) we may have to consider setting
> > (0x5018 ) .This is not taken care in original driver.  Any body had
> > in enabling this prefix. I have tried enabling it and I could do
> > ping with out packet loss. However when I do mass data transfer
> > getting panic. Further investigation showed kenel panics because DMA
> > copies data to wrong address (which is being used).
> The driver has not been used in ages so it's generally in a sad shape,
> doesn't even compile.  I think nobody touched this driver seriously in
> 5 years, probably longer.  So it's sort of expected to eat your cat or
> do other nasty stuff.
>   Ralf

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