* Murali Karicheri [150903 12:21]:
> Tony,
> On 09/03/2015 10:26 AM, Tony Lindgren wrote:
> >* santosh shilimkar [150902 08:55]:
> >>
> >>I suspected the same. I know back then we started with SERDES code
> >>with NETCP but as you already know, its a separate block which
> >>is needed for NIC car
Tony,
On 09/03/2015 10:26 AM, Tony Lindgren wrote:
* santosh shilimkar [150902 08:55]:
I suspected the same. I know back then we started with SERDES code
with NETCP but as you already know, its a separate block which
is needed for NIC card to work. Its more of phy and hence its
having differen
On 9/3/15 7:26 AM, Tony Lindgren wrote:
* santosh shilimkar [150902 08:55]:
I suspected the same. I know back then we started with SERDES code
with NETCP but as you already know, its a separate block which
is needed for NIC card to work. Its more of phy and hence its
having different address s
* santosh shilimkar [150902 08:55]:
>
> I suspected the same. I know back then we started with SERDES code
> with NETCP but as you already know, its a separate block which
> is needed for NIC card to work. Its more of phy and hence its
> having different address space is not surprising.
The point
On 09/02/2015 02:25 PM, santosh shilimkar wrote:
9/2/2015 10:58 AM, Murali Karicheri wrote:
On 09/02/2015 01:24 PM, santosh shilimkar wrote:
On 9/2/2015 9:35 AM, Murali Karicheri wrote:
Santosh,
---Cut---
I suspected the same. I know back then we started with SERDES code
w
9/2/2015 10:58 AM, Murali Karicheri wrote:
On 09/02/2015 01:24 PM, santosh shilimkar wrote:
On 9/2/2015 9:35 AM, Murali Karicheri wrote:
Santosh,
---Cut---
I suspected the same. I know back then we started with SERDES code
with NETCP but as you already know, its a separate
On 09/02/2015 01:24 PM, santosh shilimkar wrote:
On 9/2/2015 9:35 AM, Murali Karicheri wrote:
Santosh,
---Cut---
I suspected the same. I know back then we started with SERDES code
with NETCP but as you already know, its a separate block which
is needed for NIC card to work.
Subject: Re: [PATCH] ARM: dts: keystone: use one to one address
translations
under netcp
On 9/1/15 1:28 PM, WingMan Kwok wrote:
Network subsystem NetCP in Keystone-2 devices includes some HW blocks
that are memory mapped to ranges outside that of the NetCP itself.
Thus address space of a child
one to one address
translations
under netcp
On 9/1/15 1:28 PM, WingMan Kwok wrote:
Network subsystem NetCP in Keystone-2 devices includes some HW blocks
that are memory mapped to ranges outside that of the NetCP itself.
Thus address space of a child node of the NetCP node needs to be
mapped 1:1
...@hellion.org.uk; ga...@codeaurora.org;
li...@arm.linux.org.uk; devicet...@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; linux-kernel@vger.kernel.org; ssant...@kernel.org
Cc: Karicheri, Muralidharan
Subject: Re: [PATCH] ARM: dts: keystone: use one to one address translations
under netcp
On 9/1/15 1:28
urora.org;
> li...@arm.linux.org.uk; devicet...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linux-kernel@vger.kernel.org; ssant...@kernel.org
> Cc: Karicheri, Muralidharan
> Subject: Re: [PATCH] ARM: dts: keystone: use one to one address translations
> under netcp
>
> O
On 9/1/15 1:28 PM, WingMan Kwok wrote:
Network subsystem NetCP in Keystone-2 devices includes some HW blocks
that are memory mapped to ranges outside that of the NetCP itself.
Thus address space of a child node of the NetCP node needs to be
mapped 1:1 onto the parent address space. Hence empty r
Network subsystem NetCP in Keystone-2 devices includes some HW blocks
that are memory mapped to ranges outside that of the NetCP itself.
Thus address space of a child node of the NetCP node needs to be
mapped 1:1 onto the parent address space. Hence empty ranges
should be used under the NetCP node
13 matches
Mail list logo
