linux-kernel - Re: [RFC Patch v1 52/55] ARC: Support for single cycle Close Coupled Mem (CCM)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50F7878C.4020800@synopsys.com>
Date:	Thu, 17 Jan 2013 10:39:32 +0530
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RFC Patch v1 52/55] ARC: Support for single cycle Close Coupled
 Mem (CCM)

On Monday 12 November 2012 07:40 PM, Arnd Bergmann wrote:
> On Monday 12 November 2012, Vineet.Gupta1@...opsys.com wrote:
>> +config ARC_DCCM_SZ
>> +       int "DCCM Size in KB"
>> +       default "64"
>> +       depends on ARC_HAS_DCCM
>> +
>> +config ARC_DCCM_BASE
>> +       hex "DCCM map address"
>> +       default "0xA0000000"
>> +       depends on ARC_HAS_DCCM
>> +
> 
> I suppose these should be configured from the device tree at boot time, not
> during the build process.
> 
> I also wonder if the interface should be unified with what we use for
> accessing the sram on some of the ARM platforms.
> 
> 	Arnd
> 

Actually in ARC Port these are used in Linker script to layout the kernel
code/data at the addr where these hardware blocks are wired up. So can't be done
at runtime.

-Vineet
--
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/