If we can't allocate the requested number of MSIs, we can still tell the
generic code how many we were able to allocate. That can then be passed
onto the driver, allowing it to request that many in future, and
probably succeeed.
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/
We also need to check that the device isn't using MSI-X in the irq fixup
routine, otherwise we might leave MSI-Xs configured at boot.
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/msi.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/
Firmware encodes the number of MSI-X requested by a device in a
different property than for MSI. Pull the property name out as a
parameter and share the logic for both cases.
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/msi.c | 20 +++-
1 files changed, 15
We need to increment i in the loop that queries what interrupts firmware
gave us, otherwise we'll incorrectly use the first value over and over.
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/msi.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch
Hi All,
I am using linux-2.6.26 on MPC8567 and microSD is connected through SPI
interface.
Is the existing mmc driver supports microSD?
--
--Amru
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Daniel Ng99 wrote:
>
>
> clock-frequency = <35>
> clock-frequency = <0x23>
> clock-frequency = <115200>
> clock-frequency = <1c200>
> clock-frequency = <70>
> clock-frequency = <17>
> clock-frequency = <66>
> clock-frequency = <33>
>
I've also tried these:
clock-frequency = <3300>
clock-f
Scott Wood-2 wrote:
>
> On Wed, Jan 21, 2009 at 06:15:26PM -0800, Daniel Ng99 wrote:
>> Adding 'clock-frequency = <0>;' to the brg node doesn't seem to make a
>> difference to my board's behaviour.
>
> Try setting it to the actual BRG clock.
>
My console runs at a baud rate of 115,200, so tha
From: Anton Vorontsov
Date: Thu, 22 Jan 2009 21:09:30 +0300
> Suspend/resume routines check for phydrv != NULL, but that is
> wrong because "phydrv" comes from container_of(drv). If drv is NULL,
> then container_of(drv) will return non-NULL result, and the checks
> won't work.
>
> The Freescale
In the VIO bus code the wrappers for dma alloc_coherent and free_coherent
calls are rounding to IOMMU_PAGE_SIZE. Taking a look at the underlying
calls, the actual mapping is promoted to PAGE_SIZE. Changing the
rounding in these two functions fixes under-reporting the entitlement
used by the syste
On Jan 21, 2009, at 8:00 PM, Anton Vorontsov wrote:
This patch adds a new driver: sdhci-of. The driver is similar to
the sdhci-pci, it contains common probe code, and controller-specific
ops and quirks.
So far there are only Freescale eSDHC ops and quirks.
Signed-off-by: Anton Vorontsov
---
On Thu, Jan 22, 2009 at 12:55:48PM +0100, Arnd Bergmann wrote:
> On Thursday 22 January 2009, Anton Vorontsov wrote:
> > + /*
> > + * These accessors duplicate sdhci_ops, but there are two reasons
> > for
> > + * this:
> > + * 1. sdhci_ops are const, so the sdhci driver
Suspend/resume routines check for phydrv != NULL, but that is
wrong because "phydrv" comes from container_of(drv). If drv is NULL,
then container_of(drv) will return non-NULL result, and the checks
won't work.
The Freescale TBI PHYs are driver-less, so "drv" is NULL, and that
leads to the followin
On Thu, Jan 22, 2009 at 12:45:22PM -0500, Haiying Wang wrote:
> On Thu, 2009-01-22 at 06:37 -0800, wael showair wrote:
>
> > m...@24520 {
> > #address-cells = <1>;
> > #size-cells = <0>;
> > device_type = "mdio";
> >
On Thu, 2009-01-22 at 06:37 -0800, wael showair wrote:
> m...@24520 {
> #address-cells = <1>;
> #size-cells = <0>;
> device_type = "mdio";
> compatible = "gianfar";
> reg = <
On Wed, Jan 21, 2009 at 06:15:26PM -0800, Daniel Ng99 wrote:
> So the brg node looks like this-
>
> b...@119f0 {
> compatible = "fsl,mpc8272-brg",
> "fsl,cpm2-brg";
> reg = <0x119f0 0x10 0x115f0 0x10>;
> clock-frequency = <0>;
>
> But aren't the
On Thu, Jan 22, 2009 at 06:47:01PM +1100, Daniel Ng wrote:
> Thanks Scott. What is the meaning of the Ethernet reg field?:
>
> reg = <0x11300 0x20 0x8400 0x100 0x11390 0x1>;
>
> Is it-
>
> 0x11300-> GFMR1 ie. the GFMR for FCC1?
> 0x20-> GFMR1 Fields are a total of 32 bits?
> 0x8400-> initial val
first of all,thanks Heiko for ur reply.
but i m afraid that i understand nothing from ur answer,
can u give me the steps to do ur suggestion?
is ur suggestion is about to change the device tree of my board?
Here is the dts file of my board, if so what are the modifictions i have to
do to execute
On Wed, Jan 21, 2009 at 11:37 AM, wael showair wrote:
>
> Hi All,
> i have a board with MPC8555 processor
> uboot version 1.1.6
> linux kernel 2.6.19-rc5
> ltib version: 6.2.2-sv
> gcc 3.4.3
>
> it boots successfully
> i want to upgrade my linux kernel to 2.6.27
> i upgraded the following:
> ltib
Heiko Schocher wrote:
Hello wael,
wael showair wrote:
i have a board with MPC8555 processor
uboot version 1.1.6
linux kernel 2.6.19-rc5
ltib version: 6.2.2-sv
gcc 3.4.3
it boots successfully
i want to upgrade my linux kernel to 2.6.27
i upgraded the following:
ltib version 8.1.2-sv
gcc 4.
On Thursday 22 January 2009, Anton Vorontsov wrote:
> This patch adds a new driver: sdhci-of. The driver is similar to
> the sdhci-pci, it contains common probe code, and controller-specific
> ops and quirks.
>
> So far there are only Freescale eSDHC ops and quirks.
Looks very good overall.
Acke
On Thursday 22 January 2009, Anton Vorontsov wrote:
> + /*
> + * These accessors duplicate sdhci_ops, but there are two reasons for
> + * this:
> + * 1. sdhci_ops are const, so the sdhci driver won't able to assign
> + * default ops;
You could assign the pointe
Hello wael,
wael showair wrote:
> i have a board with MPC8555 processor
> uboot version 1.1.6
> linux kernel 2.6.19-rc5
> ltib version: 6.2.2-sv
> gcc 3.4.3
>
> it boots successfully
> i want to upgrade my linux kernel to 2.6.27
> i upgraded the following:
> ltib version 8.1.2-sv
> gcc 4.1
> lin
On Thursday 22 January 2009 05:59:39 Dave Hansen wrote:
> Let's take, for instance, a 1-byte reservation. With this code, you've
> suddenly turned that into a 0-byte reservation, and that *can't* be
> right. The same thing happens if you have a reservation that spans two
> pages. If you uncondit
"Rafael J. Wysocki" writes:
> On Wednesday 21 January 2009, Paul Collins wrote:
>> Got a couple of these on a PowerBook running 2.6.29-rc2 either during
>> suspend or resume -- it's hard to tell. (The suspend message is
>> timestamped in syslog with the time I resumed, so I guess it was
>> buffe
24 matches
Mail list logo
