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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 22 Nov 2015 22:24:01 +0100
From:	Marcin Wojtas <>
To:	Arnd Bergmann <>
Cc:	"" 
	Thomas Petazzoni <>,
	Andrew Lunn <>,
	Russell King - ARM Linux <>,
	Jason Cooper <>,
	Yair Mahalalel <>,
	Grzegorz Jaszczyk <>,
	Simon Guinot <>,
	Evan Wang <>,,
	Lior Amsalem <>,
	Tomasz Nowicki <>,
	Gregory Clément 
	"David S. Miller" <>,
	Sebastian Hesselbarth <>
Subject: Re: [PATCH 07/13] bus: mvebu-mbus: provide api for obtaining IO and
 DRAM window information


2015-11-22 21:02 GMT+01:00 Arnd Bergmann <>:
> On Sunday 22 November 2015 08:53:53 Marcin Wojtas wrote:
>> This commit enables finding appropriate mbus window and obtaining its
>> target id and attribute for given physical address in two separate
>> routines, both for IO and DRAM windows. This functionality
>> is needed for Armada XP/38x Network Controller's Buffer Manager and
>> PnC configuration.
>> Signed-off-by: Marcin Wojtas <>
>> [DRAM window information reference in LKv3.10]
>> Signed-off-by: Evan Wang <>
> It's too long ago to remember all the details, but I thought we
> had designed this so the configuration can just be done by
> describing it in DT. What am I missing?

And those functions do not break this approach. They just enable
finding and reading the settings of MBUS windows done during initial
configuration. Please remember that mvebu-mbus driver fills the MBUS
windows registers basing on DT, however it just configures access CPU
- DRAM/perfipheral.

In this particular case only physical adresses of buffers are known
and we have to 'open windows' between BM <-> DRAM and NETA <-> BM
internal memory. Hence instead of hardcoding size/target/attribute, we
can take information stored in CPU DRAM/IO windows registers.

Best regards,
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists