Hi again,
On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell
wrote:
>
> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" wrote:
> >
> > On 12/14/2011 08:32 AM, Steven Rostedt wrote:
> > > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
> > >
> > >> Maybe caused by commit d5e553d
I thought it had been...? Need to investigate (as baby permits...)
Stephen Rothwell wrote:
>Hi again,
>
>On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell
> wrote:
>>
>> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin"
>wrote:
>> >
>> > On 12/14/2011 08:32 AM, Steven Rostedt wrote:
>> > >
> On 12/27/2011 05:25 AM, Zhao Chenhui wrote:
> > * The driver doesn't support MPC8536 Rev 1.0 due to a JOG erratum.
> >Subsequent revisions of MPC8536 have corrected the erratum.
>
> Where do you check for this?
Nowhere. I just notify this patch don't support MPC8536 Rev 1.0.
>
> > +#defi
Some of the other things which I am experiencing which may help to trace this
issue.
1: For Core 0 printk is not working in setup_arch "just before call to
paging_init", where as on Core 1 printk is working in the same function. I see
the source uses ppc_md.progress to display debug messages s
after entering:
echo standby > /sys/power/state
I'm unable to wake up the MPC8313 (on our custom designed
MPC8313 board).
I need it to wake up through GPIO IRQ.
I cause multiple GPIO interrupts (all properly handled by an isr),
but the MPC8313 does not wake up.
How should one wake up via GPGI
On 01/03/2012 09:11 PM, Huang Changming-R66093 wrote:
>
>
>> -Original Message-
>> From: Wood Scott-B07421
>> Sent: Tuesday, January 03, 2012 2:28 AM
>> To: Huang Changming-R66093
>> Cc: linuxppc-dev@lists.ozlabs.org; Huang Changming-R66093
>> Subject: Re: [PATCH] DTS: fix the bug and add
On 01/03/2012 09:14 PM, Huang Changming-R66093 wrote:
>
>
>> -Original Message-
>> From: Tabi Timur-B04825
>> Sent: Tuesday, January 03, 2012 4:30 AM
>> To: Huang Changming-R66093
>> Cc: linuxppc-dev@lists.ozlabs.org; Huang Changming-R66093
>> Subject: Re: [PATCH] DTS: fix the bug and add
On 01/04/2012 03:34 AM, Zhao Chenhui-B35336 wrote:
>> On 12/27/2011 05:25 AM, Zhao Chenhui wrote:
>>> * The driver doesn't support MPC8536 Rev 1.0 due to a JOG erratum.
>>>Subsequent revisions of MPC8536 have corrected the erratum.
>>
>> Where do you check for this?
>
> Nowhere. I just notify
On 01/04/2012 10:19 AM, Norbert van Bolhuis wrote:
>
> after entering:
>
> echo standby > /sys/power/state
>
> I'm unable to wake up the MPC8313 (on our custom designed
> MPC8313 board).
>
> I need it to wake up through GPIO IRQ.
> I cause multiple GPIO interrupts (all properly handled by an is
The following changes since commit e4f387d8db3ba3c2dae4d8bdfe7bb5f4fe1bcb0d:
powerpc: Fix unpaired probe_hcall_entry and probe_hcall_exit (2012-01-03
12:09:27 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git next
Andy Fleming (1)
On 12/22/2011 08:25 AM, Kyle Moffett wrote:
> The MPIC code checks for a "big-endian" property and sets the flag
> MPIC_BIG_ENDIAN if one is present. Unfortunately, the PowerQUICC-III
> compatible device-tree does not specify it, so all of the board ports
> need to manually set that flag when call
On Wed, 2012-01-04 at 15:22 -0800, Randy Dunlap wrote:
> On 12/22/2011 08:25 AM, Kyle Moffett wrote:
> > The MPIC code checks for a "big-endian" property and sets the flag
> > MPIC_BIG_ENDIAN if one is present. Unfortunately, the PowerQUICC-III
> > compatible device-tree does not specify it, so al
On Wed, Dec 28, 2011 at 04:51:02PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core tree got a conflict in
> arch/powerpc/kernel/sysfs.c between commit 595fe91447b0 ("powerpc: Export
> PIR data through sysfs") from the powerpc tree and commits 8a25a2fd126c
Arshad, Farrukh wrote:
> How can I verify if the memory mapped is coherent on both cores. My memory
> partitioning is given below
>
> Core Base AddressSize
> Core 00x, 0x1000, -->
> CONFIG_PHYSICAL_START = bootm_low = Base Address
From: Jerry Huang
Accordint to latest kernel, the auto-cmd12 property should be
"sdhci,auto-cmd12", and according to the SDHC binding and the workaround for
the special chip, add the chip compatible for eSDHC: "fsl,p1022-esdhc",
"fsl,mpc8536-esdhc", "fsl,p2020-esdhc" and "fsl,p1010-esdhc".
Signe
>> Was the kernel option, CONFIG_SMP, enabled for both two kernels?
Yes CONFIG_SMP is enabled for both kernels.
>> Maybe you should make sure if kernel have a appropriate memory attribute by
>> dumping TLB entry.
Thanks for the pointer. I will try this one.
Regards,
Farrukh Arshad
_
16 matches
Mail list logo
