From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id B7E9CB7063 for ; Thu, 20 Aug 2009 17:37:00 +1000 (EST) Received: from ns0.datapatterns.co.in (mx0.datapatterns.co.in [121.242.18.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id E0914DDD0B for ; Thu, 20 Aug 2009 17:36:59 +1000 (EST) Received: from itd210 (itd210.datapatterns [10.5.4.110]) (authenticated bits=0) by ns0.datapatterns.co.in (8.14.2/8.14.2) with ESMTP id n7K7Yekt009261 for ; Thu, 20 Aug 2009 13:04:41 +0530 Message-ID: From: "Thirumalai" To: References: In-Reply-To: Subject: Re: Regarding TSI108 ethernet DMA issue Date: Thu, 20 Aug 2009 13:01:30 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B7_01CA2196.55E9B0F0" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00B7_01CA2196.55E9B0F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I found that the header file(dma-mapping.h) has changed. I saw = this change has happened on Linux -2.6.28 kernel onwards. earlier kernel = is having COMFIT_PPC64 macro. Based on this macro the things were = happened. Is there any fixes available right now or any reasons behind = this changes.=20 Regards, T. ----- Original Message -----=20 From: Thirumalai Pachamuthu=20 To: linuxppc-dev@ozlabs.org=20 Sent: Thursday, August 20, 2009 9:45 AM Subject: Regarding TSI108 ethernet DMA issue Hi all, I am trying to port linux 2.6.30 for my TSI108 based custom = board where i am getting the following kernel panic message. I found = that it was due to dma allocation function call particularly = dma_alloc_coherent() of tsi108_open function. When we see the = implementation of dma_alloc_coherent. It was bit changed from the = previous linux versions it seems.=20 The implementation of dma_alloc_coherent was kept on the = arch/powerpc/include/asm/dma-mapping.h file. Earlier implementation is = not considering the first parameter what the tsi108 driver is passing as = NULL. But the current implementation is considering this parameter and = because of this the panic is coming what i believe. So kindly let me know any patches for this problem or any fixes. Regards, T. -------------------------------------------------------------------------= ----- _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev ------=_NextPart_000_00B7_01CA2196.55E9B0F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
        I found=20 that the header file(dma-mapping.h) has changed. I saw this change = has=20 happened on Linux -2.6.28 kernel onwards. earlier kernel is having=20 COMFIT_PPC64 macro. Based on this macro the things were=20 happened. Is there any fixes available right now or any reasons = behind this=20 changes.
Regards,
T.
----- Original Message -----
From:=20 Thirumalai = Pachamuthu
Sent: Thursday, August 20, 2009 = 9:45=20 AM
Subject: Regarding TSI108 = ethernet DMA=20 issue

Hi all,
      I am trying to port linux 2.6.30 = for my=20 TSI108 based custom board where i am getting the following kernel = panic=20 message. I found that it was due to dma allocation function call = particularly=20 dma_alloc_coherent() of tsi108_open function. When we see the = implementation=20 of dma_alloc_coherent. It was bit changed from the previous linux = versions it=20 seems.
      The implementation of = dma_alloc_coherent=20 was kept on the arch/powerpc/include/asm/dma-mapping.h file. Earlier=20 implementation is not considering the first parameter what the tsi108 = driver=20 is passing as NULL. But the current implementation is considering this = parameter and because of this the panic is coming what i = believe.
 
      So kindly let me know any patches = for this=20 problem or any fixes.
Regards,
T.

_______________________________________________
Linuxppc-dev = mailing=20 = list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinf= o/linuxppc-dev ------=_NextPart_000_00B7_01CA2196.55E9B0F0--