On Mon, Feb 13, 2017 at 09:25:38AM +0800, Dongpo Li wrote: > > > On 2017/2/11 8:51, Marty Plummer wrote: > > On Fri, Feb 10, 2017 at 06:21:35PM +0800, Dongpo Li wrote: > >> I think the error "No irq resource" happened for some other reason, has no > >> relation with > >> the info "(unnamed net_device) (uninitialized):". > >> You can add more debug info to find bug. > > Do you have any particular suggestions as to what to check out, or is > > this just a general 'debug more' instruction? > I haven't encountered such a problem. So it needs you to debug what happens. > Yes, I've figured out the origin here. It was user error, in that I was not nesting the device node under the soc node, which had the interrupt-parent property. Moving it there fixed that issue.
In any case, I've ran into another problem. Basic gist is, I was giving it a go on my hi3521a board, because reading the registers for that and comparing it to the source, I find they are nearly bit-for-bit identical, but I suppose there is some tweakage needed to make it work 100%. What information would it take to have this driver expanded to enable a new, similar SoC? > > Regards, > Dongpo > > . >
