lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 22 Nov 2015 12:41:34 +0300 From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com> To: Marcin Wojtas <mw@...ihalf.com>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org Cc: davem@...emloft.net, linux@....linux.org.uk, sebastian.hesselbarth@...il.com, andrew@...n.ch, jason@...edaemon.net, thomas.petazzoni@...e-electrons.com, gregory.clement@...e-electrons.com, simon.guinot@...uanux.org, nadavh@...vell.com, alior@...vell.com, xswang@...vell.com, myair@...vell.com, nitroshift@...oo.com, jaz@...ihalf.com, tn@...ihalf.com Subject: Re: [PATCH 10/13] ARM: mvebu: add buffer manager nodes to armada-38x.dtsi Hello. On 11/22/2015 10:53 AM, Marcin Wojtas wrote: > Armada 38x network controller supports hardware buffer management (BM). > Since it is now enabled in mvneta driver, appropriate nodes can be added > to armada-38x.dtsi - for the actual common BM unit (bm@...00) and its > internal SRAM (bm-bppi), which is used for indirect access to buffer > pointer ring residing in DRAM. > > Pools - ports mapping, bm-bppi entry in 'soc' node's ranges and optional > parameters are supposed to be set in board files. > > Signed-off-by: Marcin Wojtas <mw@...ihalf.com> > --- > arch/arm/boot/dts/armada-38x.dtsi | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi > index b7868b2..b9f4ce2 100644 > --- a/arch/arm/boot/dts/armada-38x.dtsi > +++ b/arch/arm/boot/dts/armada-38x.dtsi > @@ -539,6 +539,14 @@ > status = "disabled"; > }; > > + bm: bm@...00 { The ePAPR standard tells us to give generic names to the device nodes, hence this should be named "buffer-manager" (?). [...] > @@ -617,6 +625,16 @@ > #size-cells = <1>; > ranges = <0 MBUS_ID(0x09, 0x15) 0 0x800>; > }; > + > + bm_bppi: bm-bppi { And this one "memory" (?). [...] MBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists