From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [Power.org:parch] devicetree: Musings on reserved regions Date: Tue, 08 Feb 2011 08:39:26 +1100 Message-ID: <1297114766.14982.76.camel@pasglop> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Grant Likely Cc: "parch-QRwYI7m9GJLYtjvyW6yDsg@public.gmane.org" , devicetree-discuss , David Gibson , Stuart Yoder , Scott Wood , Matthew McClintock List-Id: devicetree@vger.kernel.org > In addition to the reserved regions block in the header, define a set > of properties in the memory node that specify the reserved regions > with the name reflecting the usage. > For example: > > memory@0 { > device_type = "memory"; > reg = <0 0x40000000>; > reserved-ramdisk = <0xc00000 0x200000>; /* 2MB ramdisk */ > reserved-dtb = <0xbf0000 0x1000>; /* devicetree */ > reserved-fb0 = 0x1000000 0x400000>; /* framebuffer */ > }; > > Each reserved property would start with "reserved-" followed by a > name. reserved-ramdisk and reserved-dtb would be reserved for ramdisk > and dtb images respectively. Other names could also be defined; for > example, reserved-openfirmware. I very much dislike the list of properties with magic names. I'd rather have a pair of properties containing lists (reserved-names and reserved-ranges). Cheers, Ben.