[PATCH 1/2] powerpc/85xx: Add P1024rdb dts support

2012-05-24 Thread b29983
From: Tang Yuantian Signed-off-by: Jin Qing Signed-off-by: Li Yang Signed-off-by: Tang Yuantian --- arch/powerpc/boot/dts/p1024rdb.dtsi| 228 arch/powerpc/boot/dts/p1024rdb_32b.dts | 87 arch/powerpc/boot/dts/p1024rdb_36b.dts | 87 +++

[PATCH 2/2] powerpc/85xx: Add P1024rdb board support

2012-05-24 Thread b29983
From: Tang Yuantian The p1024rdb has the similar feature as the p1020rdb. Therefore, p1024rdb use the same platform file as the p1/p2 rdb board. Overview of P2020RDB platform - DDR3 1G - NOR flash 16M - 3 Ethernet interfaces - NAND Flash 32M - SPI EEPROM 16

Re: [PATCH] gianfar:don't add FCB length to hard_header_len

2012-05-24 Thread Joe Perches
On Thu, 2012-05-24 at 17:04 +0200, Jan Ceuleers wrote: > On 05/22/2012 09:18 PM, David Miller wrote: > > From: Jiajun Wu > > Date: Tue, 22 May 2012 17:00:48 +0800 > > > >> FCB(Frame Control Block) isn't the part of netdev hard header. > >> Add FCB to hard_header_len will make GRO fail at MAC comp

Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.

2012-05-24 Thread Timur Tabi
David Daney wrote: > Yes. You may note in the DTS file I attached in the parent (sorry for > the fubar mime types), that there are two, almost identical, MDIO > masters. smi0 has two directly attached PHYs. smi1 goes to the mux, > and each child of the mux has four attached PHYs. I'm till ha

Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.

2012-05-24 Thread David Daney
On 05/24/2012 11:28 AM, Timur Tabi wrote: David Daney wrote: Yes. You may note in the DTS file I attached in the parent (sorry for the fubar mime types), that there are two, almost identical, MDIO masters. smi0 has two directly attached PHYs. smi1 goes to the mux, and each child of the mux ha

Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.

2012-05-24 Thread Timur Tabi
David Daney wrote: > Well, the MDIO bus must have an associated device tree node. > > For my OCTEON code, the MDIO bus device is created as a result of the > call to of_platform_bus_probe(), which takes care of filling in all the > device tree nodes of the devices it finds and creates. Ok, let

Re: [PATCH] gianfar:don't add FCB length to hard_header_len

2012-05-24 Thread Jan Ceuleers
On 05/22/2012 09:18 PM, David Miller wrote: > From: Jiajun Wu > Date: Tue, 22 May 2012 17:00:48 +0800 > >> FCB(Frame Control Block) isn't the part of netdev hard header. >> Add FCB to hard_header_len will make GRO fail at MAC comparision stage. >> >> Signed-off-by: Jiajun Wu > > Applied, thanks

Re: [PATCH] gianfar:don't add FCB length to hard_header_len

2012-05-24 Thread Jan Ceuleers
On 05/24/2012 06:16 PM, Joe Perches wrote: > On Thu, 2012-05-24 at 17:04 +0200, Jan Ceuleers wrote: >> On 05/22/2012 09:18 PM, David Miller wrote: >>> Someone needs to go through this driver when net-next opens up >>> and fix all of the indentation in this driver. >> >> May I give that a go? > > I

Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support.

2012-05-24 Thread David Daney
On 05/24/2012 12:03 PM, Timur Tabi wrote: David Daney wrote: Well, the MDIO bus must have an associated device tree node. For my OCTEON code, the MDIO bus device is created as a result of the call to of_platform_bus_probe(), which takes care of filling in all the device tree nodes of the devic

module loading issue/flaw in busy memory situation?

2012-05-24 Thread Wrobel Heinz-R39252
Hi, let's assume a module gets loaded into an already busy system, and the ".init.text" section with the __init function gets loaded into one memory region, and the normal ".text" section gets loaded into a totally different memory region. Now assume that both regions are >32MB apart in address

Re: Oops with Radeon/Uninorth on Maple

2012-05-24 Thread Benjamin Herrenschmidt
On Thu, 2012-05-24 at 10:18 +0400, Dmitry Eremin-Solenikov wrote: > Hello, colleagues, > > I'm trying to enable an AGP slot (again) on my Maple board (dual > PPC970FX board, with CPC925 (U3H) north bridge). > > For now I'm stuck with a problem: I use radeon card, drm-radeon driver > with KMS.

Re: [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path

2012-05-24 Thread Benjamin Herrenschmidt
On Wed, 2012-05-23 at 16:37 -0600, Bjorn Helgaas wrote: > From: Hiroo Matsumoto > > PowerPC initialized DMA and IRQ information in the pci_scan_child_bus() > -> pcibios_fixup_bus() path. Some hotplug drivers use that path, but > others don't, e.g., pciehp, so sometimes hot-added devices are only

Re: [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path

2012-05-24 Thread Bjorn Helgaas
On Thu, May 24, 2012 at 9:00 PM, Benjamin Herrenschmidt wrote: > On Wed, 2012-05-23 at 16:37 -0600, Bjorn Helgaas wrote: >> From: Hiroo Matsumoto >> >> PowerPC initialized DMA and IRQ information in the pci_scan_child_bus() >> -> pcibios_fixup_bus() path.  Some hotplug drivers use that path, but

Re: [PATCH v3 1/2] powerpc/PCI: move DMA & IRQ init to device_add() notification path

2012-05-24 Thread Benjamin Herrenschmidt
On Thu, 2012-05-24 at 21:08 -0600, Bjorn Helgaas wrote: > > OK. Are you worried about cardbus in particular? > > This is headed for the 3.6, not 3.5, so we should have plenty of time. > As soon as everything for the current merge window gets merged and > -next is ready for the next batch, I'll