From mboxrd@z Thu Jan 1 00:00:00 1970 From: Holger Brunck Date: Tue, 12 Jun 2012 12:30:53 +0200 Subject: [U-Boot] [PATCH 04/20] arm/km: add kmnusa board support In-Reply-To: References: <1339063620-8890-1-git-send-email-valentin.longchamp@keymile.com><1339063620-8890-5-git-send-email-valentin.longchamp@keymile.com> <4FD6FF12.7080902@keymile.com> Message-ID: <4FD71A5D.2080707@keymile.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 06/12/2012 11:40 AM, Prafulla Wadaskar wrote: > > >> -----Original Message----- >> From: Holger Brunck [mailto:holger.brunck at keymile.com] >> Sent: 12 June 2012 14:04 >> To: Prafulla Wadaskar >> Cc: Valentin Longchamp; prafulla at mavell.com; u-boot at lists.denx.de; >> Gerlando Falauto >> Subject: Re: [PATCH 04/20] arm/km: add kmnusa board support >> >> On 06/12/2012 06:39 AM, Prafulla Wadaskar wrote: >>> >>> >>>> -----Original Message----- >>>> From: Valentin Longchamp [mailto:valentin.longchamp at keymile.com] >>>> Sent: 07 June 2012 15:37 >>>> To: prafulla at mavell.com >>>> Cc: Holger Brunck; u-boot at lists.denx.de; Valentin Longchamp; >> Gerlando >>>> Falauto; Prafulla Wadaskar >>>> Subject: [PATCH 04/20] arm/km: add kmnusa board support >>>> >>>> From: Holger Brunck >>>> >>>> This board is similar to portl2, but it has the u-boot environment >>>> in a SPI NOR flash and not in an i2c eeprom like portl2 have. >>>> >>>> Some other details: >>>> - IVM EEPROM is at adress: pca9547:70:9 >>>> - PCI is enabled >>>> - PIGGY4 is connected via MV88E6352 simple switch. There is no phy >>>> between the simple switch and the kirkwood. >>>> >>>> Signed-off-by: Holger Brunck >>>> Signed-off-by: Valentin Longchamp >>>> cc: Gerlando Falauto >>>> cc: Prafulla Wadaskar >>>> --- >>>> MAINTAINERS | 1 + >>>> board/keymile/km_arm/128M16-1.cfg | 294 >>>> +++++++++++++++++++++++++++++++++++++ >>> >>> Please avoid file names starting with numbers. >>> >> >> would sdram128M16-1.cfg be ok? The reason for this numbering is to >> have a chance >> to know which organisation this RAM has. > > I think kwbimage_128M16_1.cfg should be okay, > BTW: if the configuration is similar to any other already supported board, may you think to reuse the same. > yes of course, but it isn't. I'll fix the naming in a v2. Regards Holger