From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kumar Gala Date: Wed, 17 Mar 2004 09:03:33 -0600 Subject: [U-Boot-Users] Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board In-Reply-To: <16472.11906.932212.186931@gargle.gargle.HOWL> References: <16450.14241.889562.784232@gargle.gargle.HOWL> <4EC0928B-7716-11D8-A105-000393DBC2E8@motorola.com> <16470.43901.237514.894926@gargle.gargle.HOWL> <761C62B8-7757-11D8-A4C6-000393DBC2E8@motorola.com> <16472.11906.932212.186931@gargle.gargle.HOWL> Message-ID: <42A63F2D-7824-11D8-A7BF-000393DBC2E8@motorola.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 Mar 17, 2004, at 4:54 AM, Yuli Barcohen wrote: >>>>>> Kumar Gala writes: > > Kumar> Yuli, I agree with only enabling ports that will be used. I > Kumar> guess I would expect the port to be used in Linux. > > If it's to be used in Linux but not in the U-Boot, let Linux initialise > it. > > Kumar> I'm working on an updated 2.6 SCC uart driver and realized > Kumar> that I needed to enable the 2nd port in BCSR. I had > expected > Kumar> that u-boot would have already handled it. > > I see. In Arabella Linux, there is clear separation between boot and > kernel and between chip-specific and board-specific code. ADS-specific > file in Linux kernel is the place where the BCSR handling lives, so > we've got generic SCC UART driver and perform all the initialisations > (including board-specific BCSR) only when some code requests them. > Your correct, I will have the platform code for the board deal with initializing the BCSR in Linux. Thanks - kumar