I had two ideas on simple ways to convey the value of CCSRBAR, IMMR,
etc.. on various Freescale PPC SoCs. Knowing the value is useful in
debugging if you need to dump the register space. I wanted to see if
people had a preference or other ideas:
1. add it as output when we boot:
U-Boot
Dear Kumar Gala,
In message 7acc3970-1b73-4828-941c-48c6601a7...@kernel.crashing.org you wrote:
I had two ideas on simple ways to convey the value of CCSRBAR, IMMR,
etc.. on various Freescale PPC SoCs. Knowing the value is useful in
debugging if you need to dump the register space. I
On Aug 4, 2009, at 9:24 AM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message
7acc3970-1b73-4828-941c-48c6601a7...@kernel.crashing.org you wrote:
I had two ideas on simple ways to convey the value of CCSRBAR, IMMR,
etc.. on various Freescale PPC SoCs. Knowing the value is useful in
On Tue, 2009-08-04 at 09:27 -0500, Kumar Gala wrote:
On Aug 4, 2009, at 9:24 AM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message
7acc3970-1b73-4828-941c-48c6601a7...@kernel.crashing.org you wrote:
I had two ideas on simple ways to convey the value of CCSRBAR, IMMR,
etc.. on
On Aug 4, 2009, at 9:43 AM, Peter Tyser wrote:
We'd toyed around with adding a memmap command which would display
chip select mappings, and/or tlb mappings. I think lots of people
(especially end-users) would find this info useful as the same issue
you
have with determining the CCSR
5 matches
Mail list logo
