Russell King wrote:
>
> On Thu, Jul 08, 2010 at 09:01:16AM +0900, Kukjin Kim wrote:
> > Ok...let's suppose the size of section is 32MiB.
> >
> > Physical Mem.Sections
> > . .
> > . .
> > .
On Thu, Jul 08, 2010 at 09:01:16AM +0900, Kukjin Kim wrote:
> Ok...let's suppose the size of section is 32MiB.
>
> Physical Mem.Sections
> . .
> . .
> . .
> | ||
Russell King wrote:
>
> On Wed, Jul 07, 2010 at 08:27:53AM +0900, Kukjin Kim wrote:
> > Russell King wrote:
> > > What is the spacing of chunks of memory, and minimum alignment of
those
> > > chunks in physical address space?
> >
> > Some S5PC110(MCP D-type) has only available 80MiB in a bank.
> >
On Wed, Jul 07, 2010 at 08:27:53AM +0900, Kukjin Kim wrote:
> Russell King wrote:
> > What is the spacing of chunks of memory, and minimum alignment of those
> > chunks in physical address space?
>
> Some S5PC110(MCP D-type) has only available 80MiB in a bank.
> So the space accounts for 432MiB in
On Wed, Jul 7, 2010 at 8:27 AM, Kukjin Kim wrote:
> Russell King wrote:
>>
> Hi Russell :-)
>
>> On Tue, Jul 06, 2010 at 01:36:47PM +0900, Kukjin Kim wrote:
>> > This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
>> > Because smallest size of a bank on S5PV210/S5PC110 is align
Joonyoung Shim wrote:
>
> On 7/7/2010 8:27 AM, Kukjin Kim wrote:
> > Russell King wrote:
> > Hi Russell :-)
> >
> >> On Tue, Jul 06, 2010 at 01:36:47PM +0900, Kukjin Kim wrote:
> >>> This patch fixes on SECTION_SIZE_BITS for Sparsemem on
> S5PV210/S5PC110.
> >>> Because smallest size of a bank on
On 7/7/2010 8:27 AM, Kukjin Kim wrote:
> Russell King wrote:
> Hi Russell :-)
>
>> On Tue, Jul 06, 2010 at 01:36:47PM +0900, Kukjin Kim wrote:
>>> This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
>>> Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
>>>
Kyungmin Park wrote:
>
> On Tue, Jul 6, 2010 at 1:36 PM, Kukjin Kim wrote:
> > This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
> > Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
> > So each section's maximum size should be 16MB.
>
> Could you expla
Sergei Shtylyov wrote:
>
> Hello.
Hi :-)
>
> Kukjin Kim wrote:
>
> > This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
> > Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
> > So each section's maximum size should be 16MB.
>
> > Reported-by: Kyongho
Russell King wrote:
>
Hi Russell :-)
> On Tue, Jul 06, 2010 at 01:36:47PM +0900, Kukjin Kim wrote:
> > This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
> > Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
> > So each section's maximum size should be 16
Hello.
Kukjin Kim wrote:
This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
So each section's maximum size should be 16MB.
Reported-by: Kyongho Cho
Signed-off-by: Kukjin Kim
---
arch/arm/mach-s5pv2
On Tue, Jul 06, 2010 at 01:36:47PM +0900, Kukjin Kim wrote:
> This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
> Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
> So each section's maximum size should be 16MB.
What is the spacing of chunks of memory, a
On Tue, Jul 6, 2010 at 1:36 PM, Kukjin Kim wrote:
> This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
> Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
> So each section's maximum size should be 16MB.
Could you explain what's the problem?
Even though
This patch fixes on SECTION_SIZE_BITS for Sparsemem on S5PV210/S5PC110.
Because smallest size of a bank on S5PV210/S5PC110 is aligned by 16MB.
So each section's maximum size should be 16MB.
Reported-by: Kyongho Cho
Signed-off-by: Kukjin Kim
---
arch/arm/mach-s5pv210/include/mach/memory.h |8
14 matches
Mail list logo