Hi,
I'm trying to enable ethernet driver in Domain0 for R-Car H2, but it
doesn't work. The root cause of the problem is that driver cannot satisfy
the condition of dma_capable(). I found the same problem in the mailing
list, but the problem is still remaining I guess. previous mail: (
http://lists
016-04-13 2:10 GMT+09:00 Konrad Rzeszutek Wilk :
> On Tue, Apr 12, 2016 at 04:54:55PM +0900, Wonseok Ko wrote:
> > Hi,
> >
> > I'm trying to enable ethernet driver in Domain0 for R-Car H2, but it
> > doesn't work. The root cause of the problem is that driver c
Hi Konrad,
Did you read the reply? How do I fix it?
Thanks,Wonseok
Sent from Outlook Mobile
On Tue, Apr 12, 2016 at 10:10 AM -0700, "Konrad Rzeszutek Wilk"
wrote:
On Tue, Apr 12, 2016 at 04:54:55PM +0900, Wonseok Ko wrote:
> Hi,
>
> I'm trying to enable et
you for your help!
Thanks,
Wonseok.
Thanks,
Wonseok.
2016-04-14 22:52 GMT+09:00 Konrad Rzeszutek Wilk :
> On Wed, Apr 13, 2016 at 02:18:09PM +0900, Wonseok Ko wrote:
> > Hi Konrad,
> >
> > In dma_capable(), it checks that mask, size and address of device.
> >
> > Cu
Hi, Konrad
It's not same. I am attaching a macro as below.
#define SET_NETDEV_DEV(net, pdev) ((net)->dev.parent = (pdev))
So that's why I was setting the dma mask to ndev.
Thanks,
Wonseok Ko
Thanks,
Wonseok.
2016-05-18 6:10 GMT+09:00 Konrad Rzeszutek Wilk :
> On Fri,
Hi, All
I founded the previous post to solve the problem as the same as mine, the
patch was applied in latest version, but I've got the data abort.
previous post:
https://lists.xen.org/archives/html/xen-devel/2013-09/msg00606.html and I
referred to the wiki page:
http://wiki.xen.org/wiki/Xen_ARM_w
uld you please explain the reason why the above fault?
Thanks,
Wonseok
Thanks,
Wonseok.
2016-07-12 19:09 GMT+09:00 Julien Grall :
>
>
> On 12/07/16 06:20, Wonseok Ko wrote:
>
>> Hi, All
>>
>
> Hello,
>
> I founded the previous post to solve the problem as t
yprintk console=ttyAMA0"
Thanks,
Wonseok
Thanks,
Wonseok.
2016-07-12 20:56 GMT+09:00 Wonseok Ko :
> Thank you for your help, Julien
>
> I found the memory overlapping problem between Kernel and Device Tree in
> bootwrapper.
> The problem came from INITRD_OFFSET and PHYS
