Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758744Ab0GUSgx (ORCPT ); Wed, 21 Jul 2010 14:36:53 -0400 Received: from mailout3.w1.samsung.com ([210.118.77.13]:63680 "EHLO mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751170Ab0GUSgv convert rfc822-to-8bit (ORCPT ); Wed, 21 Jul 2010 14:36:51 -0400 MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed; delsp=yes Date: Wed, 21 Jul 2010 20:38:12 +0200 From: =?utf-8?B?TWljaGHFgiBOYXphcmV3aWN6?= Subject: Re: [PATCH 2/4] mm: cma: Contiguous Memory Allocator added In-reply-to: <1279736348.31376.20.camel@c-dwalke-linux.qualcomm.com> To: Daniel Walker Cc: linux-mm@kvack.org, Marek Szyprowski , Pawel Osciak , Xiaolin Zhang , Hiremath Vaibhav , Robert Fekete , Marcus Lorentzon , linux-kernel@vger.kernel.org, Kyungmin Park , linux-arm-msm@vger.kernel.org Message-id: Organization: Samsung Electronics Content-transfer-encoding: 8BIT User-Agent: Opera Mail/10.60 (Linux) References: <1279649724.26765.23.camel@c-dwalke-linux.qualcomm.com> <1279654698.26765.31.camel@c-dwalke-linux.qualcomm.com> <1279733750.31376.14.camel@c-dwalke-linux.qualcomm.com> <1279736348.31376.20.camel@c-dwalke-linux.qualcomm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1893 Lines: 38 > On Wed, 2010-07-21 at 20:11 +0200, Michał Nazarewicz wrote: >> Not really. This will probably be used mostly on embedded systems >> where users don't have much to say as far as hardware included on the >> platform is concerned, etc. Once a phone, tablet, etc. is released >> users will have little need for customising those strings. On Wed, 21 Jul 2010 20:19:08 +0200, Daniel Walker wrote: > You can't assume that user won't want to reflash their own kernel on the > device. Your assuming way too much. If user is clever enough to reflash a phone she will find the strings easy especially that they are provided from: (i) bootloader which is even less likely to be reflashed and if someone do reflash bootloader she is a guru who'd know how to make the strings; or (ii) platform defaults which will be available with the rest of the source code for the platform. > If you assume they do want their own kernel then they would need this > string from someplace. If your right and this wouldn't need to change, > why bother allowing it to be configured at all ? Imagine a developer who needs to recompile the kernel and reflash the device each time she wants to change the configuration... Command line arguments seems a better option for development. And the configuration is needed because it is platform-dependent so it needs to be set for each platform. -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Michał "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/