This patch fixes a wrong check on num_txbdfree. It could lead to num_txbdfree
become nagative.
Result was that the gianfar stops sending data.
Signed-off-by: Rini van Zetten rini at arvoo dot nl
---
drivers/net/gianfar.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: Rini van Zetten r...@arvoo.nl
Date: Thu, 26 Feb 2009 09:56:58 +0100
This patch fixes a wrong check on num_txbdfree. It could lead to
num_txbdfree become nagative. Result was that the gianfar stops
sending data.
Signed-off-by: Rini van Zetten rini at arvoo dot nl
Please use
This patch fixes a wrong check on num_txbdfree. It could lead to num_txbdfree
become nagative.
Result was that the gianfar stops sending data.
Changes from first version :
- removed a space between parens (David Millers comment)
- full email address in signed off line
Signed-off-by: Rini van
In the DTB tree created by firmware on Maple 64bit target, host bridge
parent
node has specified both of these two properties to be 2. However, the actual
cell value for host bridge node is 1. we have to provide one fixup
function.
Signed-off-by: Tiejun Chen tiejun.ch...@gmail.com
---
On Thu, Feb 26, 2009 at 03:07:24PM +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Please pull a few regression fixes for powerpc.
Cheers,
Ben.
The following changes since commit 169d418b127b98a3e464e9c4b807ad083760f98c:
Linus Torvalds (1):
Merge branch 'for-linus' of
Hi David,
Hmmm... my bad, I think you need to keep the CONFIG_NUMA
there too as there is a TLB usage penalty for non-NUMA
systems if you only use CONFIG_64BIT there.
Sorry that was my screwup, here's a fixed version.
Anton
--
On PowerPC we allocate large boot time hashes on node 0. This
From: Anton Blanchard an...@samba.org
Date: Thu, 26 Feb 2009 22:24:32 +1100
On PowerPC we allocate large boot time hashes on node 0. This leads to
an imbalance in the free memory, for example on a 64GB box (4 x 16GB
nodes):
Free memory:
Node 0: 97.03%
Node 1: 98.54%
Node 2: 98.42%
Node
As far as I understand the DTS bindings now support an SPI master controller to
- use the chip-selects controlled directly by the SPI master controller hardware
or
- to use GPIO's trough gpiolib as chip selects
but not a combination of both, am I right?
Now every SPI driver needs to be adapted to
Leo, sorry for sending this twice. Forgot to cc the list.
I am hoping someone can shed some light on the state of the USB support in
the
2.6.28 kernel for USB OTG on the MPC8313E RDB. The configuration options
are
a bit different than the ones from the provided LTIB kernel--- for
obvious
Hello,
I've got a target derived from the Lite5200 that needs to use simple
interrupt GPIO pins. I created a patch to support this kind of GPIO.
I would need your opinion and like to hear any criticism. Esp. the
facts that I ad to split up struct mpc52xx_gpio and that the GPIO
numbering might
Hi all,
I'm using the mpc8313erdb. I got two external interrupt sources which
are
handled by two UIO drivers.
These interrupts shall be triggered on falling edge.
Therefore I just added (Kernel version 2.6.24) in
arch/powerpc/sysdev/ipic.c in function ipic_set_irq_type
at line ~484 flow_type =
(note: added the devicetree-discuss mailing list to this thread)
On Wed, Feb 25, 2009 at 2:20 AM, Pieter phenn...@vastech.co.za wrote:
Hi all
I am busy porting my board to Linux 2.6.27 from 2.6.19. The old Linux
was compiled using the ppc architecture, and had a platform_device
struct ure
On Thu, 26 Feb 2009, Rini van Zetten wrote:
This patch fixes a wrong check on num_txbdfree. It could lead to num_txbdfree
become nagative.
Result was that the gianfar stops sending data.
A quick mental note for your next patch submission:
Changes from first version :
- removed a space
On Tuesday 24 February 2009, Ira Snyder wrote:
This adds support to Linux for using virtio between two computers linked by
a PCI interface. This allows the use of virtio_net to create a familiar,
fast interface for communication. It should be possible to use other virtio
devices in the future,
On Thu, 26 Feb 2009, Arnd Bergmann wrote:
On Tuesday 24 February 2009, Ira Snyder wrote:
+/* Virtio-over-PCI descriptors: 12 bytes. These can chain together via
next */
+struct vop_desc {
+ /* Address (host physical) */
+ __le32 addr;
Only 32-bit? Is this
On Thu, 26 Feb 2009, Mark Nelson wrote:
On Thu, 26 Feb 2009 09:45:41 am Mark Nelson wrote:
On Thu, 26 Feb 2009 12:31:20 am Geert Uytterhoeven wrote:
On Wed, 25 Feb 2009, Mark Nelson wrote:
Does the following patch fix the errors you're seeing? (it applies the
same fix as the previous
I'm trying to use some drivers which are not yet OF aware
(in particular net/dsa). In order to use these drivers, I
need platform_device pointers for my network any MII bus (PHY).
In the OF world, how do I get to these? I have a MPC834x
based board and somehow I need access to these devices
Hello everyone,
I recently obtained a Mikrotik RB600 and applied the patch from http://cynigram.com/~nfontes/rb600/
to get it up and running with 2.6.28.3
With this patch applied everything was detected on the board and
worked. For testing purposes I tried a recent git snapshot and noticed
I have looking for kexec support on pppc32. Where can I find and download all
the patches for kernel the kexec-tools? Which kernel version should the patches
apply to?
Thanks
Liang Chai
___
Linuxppc-dev mailing list
On Thu, Feb 26, 2009 at 05:15:27PM +0100, Arnd Bergmann wrote:
On Tuesday 24 February 2009, Ira Snyder wrote:
This adds support to Linux for using virtio between two computers linked by
a PCI interface. This allows the use of virtio_net to create a familiar,
fast interface for
On Thu, Feb 26, 2009 at 05:53:56PM +0100, Geert Uytterhoeven wrote:
On Thu, 26 Feb 2009, Arnd Bergmann wrote:
On Tuesday 24 February 2009, Ira Snyder wrote:
+/* Virtio-over-PCI descriptors: 12 bytes. These can chain together via
next */
+struct vop_desc {
+ /* Address (host
On Thu, 2009-02-26 at 18:08 +0800, Tiejun Chen wrote:
In the DTB tree created by firmware on Maple 64bit target, host bridge
parent
node has specified both of these two properties to be 2. However, the
actual
cell value for host bridge node is 1. we have to provide one fixup
function.
Hi !
On Thu, 2009-02-26 at 06:28 -0500, Josh Boyer wrote:
On Thu, Feb 26, 2009 at 03:07:24PM +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Please pull a few regression fixes for powerpc.
Cheers,
Ben.
The following changes since commit 169d418b127b98a3e464e9c4b807ad083760f98c:
Linus
On Thursday 26 February 2009, Ira Snyder wrote:
On Thu, Feb 26, 2009 at 05:15:27PM +0100, Arnd Bergmann wrote:
I think so too. I was just getting something working, and thought it
would be better to have it out there rather than be working on it
forever. I'll try to break things up as I have
On Fri, Feb 27, 2009 at 07:30:21AM +1100, Benjamin Herrenschmidt wrote:
On Thu, 2009-02-26 at 06:28 -0500, Josh Boyer wrote:
On Thu, Feb 26, 2009 at 03:07:24PM +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Please pull a few regression fixes for powerpc.
Cheers,
Ben.
The following
On Thu, 2009-02-26 at 15:46 -0500, Josh Boyer wrote:
It's a regression from 2.6.28, yes. See:
http://ozlabs.org/pipermail/linuxppc-dev/2009-February/067914.html
and
http://patchwork.ozlabs.org/patch/21527/
(note the Accepted state)
if it's in my next or test branch ? I would have
On Thu, Feb 26, 2009 at 09:37:14PM +0100, Arnd Bergmann wrote:
On Thursday 26 February 2009, Ira Snyder wrote:
On Thu, Feb 26, 2009 at 05:15:27PM +0100, Arnd Bergmann wrote:
I think so too. I was just getting something working, and thought it
would be better to have it out there rather
On Thu, Feb 26, 2009 at 4:25 AM, Rini van Zetten r...@arvoo.nl wrote:
This patch fixes a wrong check on num_txbdfree. It could lead to
num_txbdfree become nagative.
Result was that the gianfar stops sending data.
Changes from first version :
- removed a space between parens (David Millers
On Tue, Feb 24, 2009 at 6:09 AM, Octavian Purdila opurd...@ixiacom.com wrote:
Signed-off-by: Octavian Purdila opurd...@ixiacom.com
---
arch/powerpc/kernel/cputable.c | 6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/cputable.c
Hi Linus
And here's another little regression fix. For some reason, that one was
done and acked ages ago, marked accepted in patchwork and never
actually merged anywhere ... go figure.
The following changes since commit 64e71303e44f3697e4568147caa966de74bdb4fb:
Linus Torvalds (1):
On Thursday 26 February 2009, Ira Snyder wrote:
On Thu, Feb 26, 2009 at 09:37:14PM +0100, Arnd Bergmann wrote:
The registers are part of the board control registers. They don't fit at
all in the message unit. Doing this in the bootloader seems like a
logical place, but that would require any
On Thu, 2009-02-26 at 16:30 -0600, Andy Fleming wrote:
I know this saves you some code, but it seems hacky. It would be
better to modify oprofile to detect the proper cpu type. Also, this
will screw things up if you try to use the different event set that
the 750 has.
Agreed. Note that
On Thu, Feb 26, 2009 at 11:34:33PM +0100, Arnd Bergmann wrote:
On Thursday 26 February 2009, Ira Snyder wrote:
On Thu, Feb 26, 2009 at 09:37:14PM +0100, Arnd Bergmann wrote:
The registers are part of the board control registers. They don't fit at
all in the message unit. Doing this in
Some more information regarding this board. This is the output of
dtc /proc/device/ree:
I removed all information not relevant to networking
/dts-v1/;
/ {
linux,phandle = 0x100;
#size-cells = 0x1;
#address-cells = 0x1;
compatible = MPC83xx;
model =
On Friday 27 February 2009, Ira Snyder wrote:
On Thu, Feb 26, 2009 at 11:34:33PM +0100, Arnd Bergmann wrote:
I guess the best option for doing it in Linux then would be to have
a board control driver (not sure if this already exists) that exports
high-level functions to set up the inbound
2009/2/27 Benjamin Herrenschmidt b...@kernel.crashing.org
On Thu, 2009-02-26 at 18:08 +0800, Tiejun Chen wrote:
In the DTB tree created by firmware on Maple 64bit target, host bridge
parent
node has specified both of these two properties to be 2. However, the
actual
cell value for host
Hi all,
I'm using linux version 2.6.29-rc5.
I've compiled the SPI diver (spi_mpc83xx.c) as a module, but it fails the load
with a No such device error.
I've managed to track it down to platform_driver_probe() in
drivers/base/platform.c
which returns -ENODEV because a device list is empty.
Hi Roman,
Thanks for this work. Comments below.
On Thu, Feb 26, 2009 at 7:24 AM, Roman Fietze
roman.fie...@telemotive.de wrote:
Hello,
I've got a target derived from the Lite5200 that needs to use simple
interrupt GPIO pins. I created a patch to support this kind of GPIO.
I would need
Thanks for the patch Wolfram. Comments below.
On Wed, Feb 25, 2009 at 8:32 AM, Wolfram Sang w.s...@pengutronix.de wrote:
Signed-off-by: Wolfram Sang w.s...@pengutronix.de
---
arch/powerpc/boot/dts/pcm032.dts | 391 +++
arch/powerpc/configs/52xx/pcm032_defconfig | 1394
From: Grant Likely grant.lik...@secretlab.ca
To better match the ePAPR specification, device nodes which claim
simple-bus compatibility should be probed by default.
Signed-off-by: Grant Likely grant.lik...@secretlab.ca
---
arch/powerpc/platforms/52xx/mpc52xx_common.c |3 ++-
1 files
On Wed, Feb 25, 2009 at 8:25 PM, Mike Ditto mdi...@consentry.com wrote:
Daniel Ng wrote:
f0010d40:00 not found
eth0: Could not attach to PHY
These messages are typical of having the wrong GPIO pins in the mdio
node or the wrong MDIO address (reg property) in the ethernet-phy node.
41 matches
Mail list logo
