Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

> >>> with this patch, this mpc8313 board does this: > >>> > >>> U-Boot 2009.06-00524-g28958b8 (Jul 23 2009 - 18:33:11) MPC83XX > >>> > >>> Reset Status: > >>> > >>> CPU: e300c3, MPC8313E, Rev: 1.0 at 333.333 MHz, CSB: 166.667 MHz > >>> Board: Freescale MPC8313ERDB > >>> I2C: ready > >>> DRAM:

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

Liu Dave-R63238 wrote: >>> with this patch, this mpc8313 board does this: >>> >>> U-Boot 2009.06-00524-g28958b8 (Jul 23 2009 - 18:33:11) MPC83XX >>> >>> Reset Status: >>> >>> CPU: e300c3, MPC8313E, Rev: 1.0 at 333.333 MHz, CSB: 166.667 MHz >>> Board: Freescale MPC8313ERDB >>> I2C: ready >>> DRA

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

> > with this patch, this mpc8313 board does this: > > > > U-Boot 2009.06-00524-g28958b8 (Jul 23 2009 - 18:33:11) MPC83XX > > > > Reset Status: > > > > CPU: e300c3, MPC8313E, Rev: 1.0 at 333.333 MHz, CSB: 166.667 MHz > > Board: Freescale MPC8313ERDB > > I2C: ready > > DRAM: 128 MB > > FLASH

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Fri, Jul 24, 2009 at 11:40:09AM -0500, Kim Phillips wrote: > with this patch, this mpc8313 board does this: > > U-Boot 2009.06-00524-g28958b8 (Jul 23 2009 - 18:33:11) MPC83XX > > Reset Status: > > CPU: e300c3, MPC8313E, Rev: 1.0 at 333.333 MHz, CSB: 166.667 MHz > Board: Freescale MPC8313ERD

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Jul 24, 2009, at 8:46 AM, Wolfgang Denk wrote: > Dear Peter, > > In message <20090723190101.c8f8a832e...@gemini.denx.de> I wrote: >> >> In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> >> you wrote: >>> Previously, non-e500 architectures only unlocked their data cache >>>

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Fri, Jul 24, 2009 at 09:41:21AM -0500, Peter Tyser wrote: > On Fri, 2009-07-24 at 15:46 +0200, Wolfgang Denk wrote: > > Dear Peter, > > > > In message <20090723190101.c8f8a832e...@gemini.denx.de> I wrote: > > > > > > In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> you > > > w

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Fri, 24 Jul 2009 15:46:16 +0200 Wolfgang Denk wrote: > Dear Peter, > > In message <20090723190101.c8f8a832e...@gemini.denx.de> I wrote: > > > > In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> you wrote: > > > Previously, non-e500 architectures only unlocked their data cache

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Fri, 2009-07-24 at 15:46 +0200, Wolfgang Denk wrote: > Dear Peter, > > In message <20090723190101.c8f8a832e...@gemini.denx.de> I wrote: > > > > In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> you wrote: > > > Previously, non-e500 architectures only unlocked their data cache wh

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

Dear Peter, In message <20090723190101.c8f8a832e...@gemini.denx.de> I wrote: > > In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> you wrote: > > Previously, non-e500 architectures only unlocked their data cache which > > was used as early RAM when booting to Linux using the "bootm

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Thu, 23 Jul 2009 21:01:01 +0200 Wolfgang Denk wrote: > FLASH: ## Unknown FLASH on Bank 1 - Size = 0x0200 = 0 MB > 32 MB > PCI: Bus Dev VenId DevId Class Int > 00 0b 104c ac55 0607 ff > 00 0b 104c ac55 0607 ff > => fli > >

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

Dear Peter Tyser, In message <1247269570-11406-1-git-send-email-pty...@xes-inc.com> you wrote: > Previously, non-e500 architectures only unlocked their data cache which > was used as early RAM when booting to Linux using the "bootm" command. > This change causes all PPC boards with CONFIG_SYS_INIT

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Jul 20, 2009, at 6:44 PM, Liu Dave-R63238 wrote: I've tested this on 86xx boards, it'd be great if someone could test on 83xx and 74xx/7xx. 85xx boards should not be affected by >> this change. This change assumes http://thread.gmane.org/gmane.comp.boot-loaders.u

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

> > > I've tested this on 86xx boards, it'd be great if someone > > > could test on > > > 83xx and 74xx/7xx. 85xx boards should not be affected by > this change. > > > > > > This change assumes > > > http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/63423 > > > has already been applied, o

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

Dear "Liu Dave-R63238", In message you wrote: > > Previously, non-e500 architectures only unlocked their data > > cache which > > was used as early RAM when booting to Linux using the "bootm" command. > > This change causes all PPC boards with > > CONFIG_SYS_INIT_RAM_LOCK defined > > to unlock

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

On Sat, 2009-07-11 at 07:52 +0800, Liu Dave-R63238 wrote: > > Previously, non-e500 architectures only unlocked their data > > cache which > > was used as early RAM when booting to Linux using the "bootm" command. > > This change causes all PPC boards with > > CONFIG_SYS_INIT_RAM_LOCK defined > >

Re: [U-Boot] [PATCH] ppc: Unlock cache-as-ram in a consistent manner

> Previously, non-e500 architectures only unlocked their data > cache which > was used as early RAM when booting to Linux using the "bootm" command. > This change causes all PPC boards with > CONFIG_SYS_INIT_RAM_LOCK defined > to unlock their data cache during U-Boot's initialization. This > imp