From mboxrd@z Thu Jan 1 00:00:00 1970 From: xuwei5@hisilicon.com (Wei Xu) Date: Mon, 12 Sep 2016 09:19:06 +0100 Subject: [RFD] hix5hd2 datasheet? In-Reply-To: <37ac958a-2196-349d-6af9-995067f1bdb8@gmail.com> References: <57D2740C.10000@hisilicon.com> <37ac958a-2196-349d-6af9-995067f1bdb8@gmail.com> Message-ID: <57D664FA.3050006@hisilicon.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Jiancheng, On 11/09/2016 01:47, Marty Plummer wrote: > On 09/09/2016 03:34 AM, Wei Xu wrote: >> Hi Marty, >> >> On 08/09/2016 23:58, Marty Plummer wrote: >>> Hello, >>> >>> I'm currently working to get the ethernet interface for the >>> hi3520 SoC to work, and I think (emphasis on think) the hix5hd2-gmac >>> driver is compatible, or nearly so, as checking the sdk source code >>> for the interface has a fairly large amount of similar code (well, as >>> similar as 2.6.24 vs 4.8-rc4 code can be) and identical register >>> definitions to the very bit, so I was hoping to compare the datasheets >>> and see how far the commonality goes. Plus, having the datasheets >>> readily available will be of assistance to anyone else looking to >>> contribute. >> >> +Jiancheng into this mail group. >> Maybe you could get the hix5hd2 datasheets from him. >> Thanks! >> >> Best Regards, >> Wei >> >>> >>> Thanks, >>> Marty >>> >>> >> > In additon, I'm wondering how the second reg property for the > hix5hd2-gmac devicetree is determined (in fact, that is my main concern), > as I'm pretty sure it will work with the gmac on hi3520, but I can't > find a register in the hi3520 datasheet that I could 100% say is the > right one, and adding the driver to the initrd causes a kernel panic > (I'm assuming this is because of wrong reg values unless otherwise > proven) on an otherwise mostly working kernel. > Could you share more about the second external reg if you have? Thanks! Best Regards, Wei