Introduce basic support for the Freescale P1022DS reference board, based on the
Freescale BSP for this board. This patch excludes the DIU, SSI, and MMC/SD
drivers. Only a 36-bit DTS is provided.
Update mpc86xx_smp_defconfig and mpc85xx_defconfig to support the P1022DS.
This means enabling 64-bit
Sandeep,
I believe you are the author of the code that adds multiple queue and
multiple group support to the Gianfar driver. Can you update
Documentation/powerpc/dts-bindings/fsl/tsec.txt with the binding
documentation for these nodes, so that we can all know what they're supposed
to look like?
On Fri, 2 Jul 2010 12:16:11 -0700
Shawn Jin wrote:
> >> The chipselect? Isn't it just the child-bus-addr? BTW, do we have
> >> to define the #address-cells to 2? 1 is not enough?
> >
> > The first cell of the child bus address is the chip select, the
> > second cell is the offset into the chip se
>> The chipselect? Isn't it just the child-bus-addr? BTW, do we have to
>> define the #address-cells to 2? 1 is not enough?
>
> The first cell of the child bus address is the chip select, the second
> cell is the offset into the chip select.
I see. So the #address-sells of 2 doesn't necessarily in
On Fri, 2 Jul 2010 20:47:44 +0200
Alexander Graf wrote:
>
> On 02.07.2010, at 19:59, Hollis Blanchard wrote:
>
> > [Resending...]
> >
> > Please reconcile this with
> > http://www.linux-kvm.org/page/PowerPC_Hypercall_ABI, which has been
> > discussed in the (admittedly closed) Power.org embedd
On 02.07.2010, at 19:59, Hollis Blanchard wrote:
> [Resending...]
>
> Please reconcile this with
> http://www.linux-kvm.org/page/PowerPC_Hypercall_ABI, which has been
> discussed in the (admittedly closed) Power.org embedded hypervisor
> working group. Bear in mind that other hypervisors are alr
On 02.07.2010, at 18:27, Segher Boessenkool wrote:
>> +To find out if we're running on KVM or not, we overlay the PVR register.
>> Usually
>> +the PVR register contains an id that identifies your CPU type. If, however,
>> you
>> +pass KVM_PVR_PARA in the register that you want the PVR result in
[Resending...]
Please reconcile this with
http://www.linux-kvm.org/page/PowerPC_Hypercall_ABI, which has been
discussed in the (admittedly closed) Power.org embedded hypervisor
working group. Bear in mind that other hypervisors are already
implementing the documented ABI, so if you have concerns,
On Fri, 2 Jul 2010 10:06:47 -0700
Shawn Jin wrote:
> > Or more generally update this section to hold whatever is connected
> > to the localbus on your board. The first cell is the chipselect.
>
> The chipselect? Isn't it just the child-bus-addr? BTW, do we have to
> define the #address-cells to
>> local...@fa200100 {
>> compatible = "fsl,mpc885-localbus", "fsl,pq1-localbus",
>> "simple-bus";
>> #address-cells =<2>;
>> #size-cells =<1>;
>> reg =<0xfa200100 0x40>;
>>
>> ranges =<
>>
On 02.07.2010, at 18:22, Segher Boessenkool wrote:
>> [without]
>>
>> debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /dev/null;
>> done
>>
>> real0m14.659s
>> user0m8.967s
>> sys 0m5.688s
>>
>> [with]
>>
>> debian-powerpc:~# time for i in {1..1000}; do /bin/echo
+To find out if we're running on KVM or not, we overlay the PVR
register. Usually
+the PVR register contains an id that identifies your CPU type. If,
however, you
+pass KVM_PVR_PARA in the register that you want the PVR result in,
the register
+still contains KVM_PVR_PARA after the mfpvr cal
v1 -> v2:
- RMO -> PAM
Except you forgot the subject line.
Segher
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
[without]
debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /
dev/null; done
real0m14.659s
user0m8.967s
sys 0m5.688s
[with]
debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /
dev/null; done
real0m7.557s
user0m4.121s
sys 0m3.426s
So th
Alexander Graf wrote:
> We need to override EA as well as PA lookups for the magic page. When the
> guest
> tells us to project it, the magic page overrides any guest mappings.
>
> In order to reflect that, we need to hook into all the MMU layers of KVM to
> force map the magic page if necessary.
Simply add a proper ID into the device table.
Signed-off-by: Anton Vorontsov
---
drivers/edac/mpc85xx_edac.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
index 52ca09b..f39b00a 100644
--- a/drivers/edac/mpc85xx
Since commit 5753c082f66eca5be81f6bda85c1718c5eea6ada ("powerpc/85xx:
Kconfig cleanup"), there is no MPC85xx Kconfig symbol anymore, so the
driver became non-selectable.
This patch fixes the issue by switching to PPC_85xx symbol.
Signed-off-by: Anton Vorontsov
---
drivers/edac/Kconfig |2 +-
On Thu, 1 Jul 2010, Alexander Graf wrote:
> Currently x86 is the only architecture that uses kvm_guest_init(). With
> PowerPC we're getting a second user, but the signature is different there
> and we don't need to export it, as it uses the normal kernel init framework.
Making the signatures match
On 02.07.2010, at 09:41, Geert Uytterhoeven wrote:
> On Thu, 1 Jul 2010, Alexander Graf wrote:
>> Currently x86 is the only architecture that uses kvm_guest_init(). With
>> PowerPC we're getting a second user, but the signature is different there
>> and we don't need to export it, as it uses the
On Thursday 01 July 2010 11:55 PM, Maciej Rutecki wrote:
On środa, 30 czerwca 2010 o 13:22:27 divya wrote:
While running fs_racer test from LTP on a POWER6 box against latest
git(2.6.35-rc3-git4 - commitid 984bc9601f64fd) came across the following
warning followed by multiple oops.
I
20 matches
Mail list logo
