I am running XFS filesystem on my self-built MPC8548 based(a NAS box),
kernel version is 2.6.31.6. I have encountered a very very odd problem
which has been unsoled untill now, see
this:http://oss.sgi.com/archives/xfs/2009-12/msg00073.html
I wonder if anybody on this list had experience to use XFS
Hi,
> On recent ppc64 kernels, limiting the stack (using 'ulimit -s blah') is
> now more restrictive than it was before. On 2.6.31 with 4k pages I
> could run 'ulimit -s 16; /usr/bin/test' without a problem. Now with
> mainline, even 'ulimit -s 64; /usr/bin/test' gets killed.
>
> Using 64k pag
On Fri, 2010-02-05 at 20:03 -0500, Josh Boyer wrote:
> On Sat, Feb 06, 2010 at 07:57:46AM +1100, Benjamin Herrenschmidt wrote:
> >On Fri, 2010-02-05 at 08:55 -0500, Josh Boyer wrote:
> >> This works around the PCIe bridge setup on the iMac iSight boxen.
> >
> >Is this still needed ? I though I had
On Sat, Feb 06, 2010 at 07:57:46AM +1100, Benjamin Herrenschmidt wrote:
>On Fri, 2010-02-05 at 08:55 -0500, Josh Boyer wrote:
>> This works around the PCIe bridge setup on the iMac iSight boxen.
>
>Is this still needed ? I though I had fixed the root cause (incorrect
>setup of the bridge) a while b
On recent ppc64 kernels, limiting the stack (using 'ulimit -s blah') is
now more restrictive than it was before. On 2.6.31 with 4k pages I
could run 'ulimit -s 16; /usr/bin/test' without a problem. Now with
mainline, even 'ulimit -s 64; /usr/bin/test' gets killed.
Using 64k pages is even worse.
Quick question. I have a 8313 based custom board. If I wanted
to include my config file and dts into mainline are there any
restrictions or requirements? Just curious.
Thanks, please let me know.
Ron
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.o
These changes add MDIO and phy lib support to the driver as the
IP core now supports the MDIO bus.
The MDIO bus and phy are added as a child to the emaclite in the device
tree as illustrated below.
mdio {
#address-cells = <1>;
#size-cells = <0>;
compatible = "xlnx,emaclite
This patch adds NOR Flash, LEDs and PIB support for MPC8568E-MDS
boards. Plus, move bcsr node into localbus node, and add bcsr5
gpio-controller node.
Some platform code modifications were also needed.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8568mds.dts | 65 ++
On Power7 processors running in SMT4 mode with 2, 3, or 4 idle threads
there is performance benefit to idling the higher numbered threads in
the core.
This patch implements arch_scale_smt_power to dynamically update smt
thread power in these idle cases in order to prefer threads 0,1 over
thread
The new Power7 processor has 4 way SMT. This 4 way SMT benefits from
dynamic power updates that arch_scale_smt_power was designed to provide.
The first patch fixes a generic scheduler bug necessary for arch_scale_smt
to properly function. The second patch implements arch_scale_smt_power
for powe
Enable the scheduler feature that allows use of arch_scale_smt_power. Stub out
the broken x86 implementation.
Signed-off-by: Joel Schopp
---
Index: linux-2.6.git/kernel/sched_features.h
===
--- linux-2.6.git.orig/kernel/sched_featur
On Fri, 2010-02-05 at 08:55 -0500, Josh Boyer wrote:
> This works around the PCIe bridge setup on the iMac iSight boxen.
Is this still needed ? I though I had fixed the root cause (incorrect
setup of the bridge) a while back...
Cheers,
Ben.
> ---
>
> --- linux/arch/powerpc/platforms/powermac/pc
The driver wrongly sets default state for LEDs that don't specify
default-state property.
Currently the driver handles default state this way:
memset(&led, 0, sizeof(led));
for_each_child_of_node(np, child) {
state = of_get_property(child, "default-state", NULL);
if (state) {
OF GPIO infrastructure is using dynamic GPIO bases, so it is possible
that of_get_gpio()'s returned GPIO number will be no longer valid, or
worse, it may point to an unexpected GPIO controller.
This scenario is possible:
driver A: driver B: driver C:
-
Platform code use node->data to store some private information
associated with a node.
Previously there was no need for any locks and accessors since we were
initializing the data mostly at boot time and never modified it later.
Though, nowadays OF GPIO infrastructure supports GPIO chips detachin
So far of_node_init() just initializes a kref, later we'll have to
initialize other fields (for example node->data_lock).
Signed-off-by: Anton Vorontsov
---
arch/microblaze/kernel/prom.c |4 ++--
arch/powerpc/kernel/prom.c|4 ++--
arch/powerpc/platforms/iserie
Hi all,
OF GPIO infrastructure is using dynamic GPIO bases, so it is possible
that of_get_gpio()'s returned GPIO number will be no longer valid, or
worse, it may point to an unexpected GPIO controller.
This scenario is possible:
driver A: driver B: driver C:
-
With the new OF GPIO infrastructure it's much easier to handle I2C
GPIO controllers, i.e. now drivers don't have to deal with the
OF-specific bits.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 68 +---
1 files changed, 14 insertions(+)
This patch implements GPIOLIB notifier hooks, and thus makes device-enabled
GPIO chips (i.e. the ones that have gpio_chip->dev specified) automatically
attached to the OpenFirmware subsystem. Which means that now we can handle
I2C and SPI GPIO chips almost* transparently.
* "Almost" because some c
I2C/SPI drivers allocate gpio_chip structure already, so we don't need
'struct gpio_chip gc' in the OF GPIO subsystem, instead we need to store
just a pointer, and then attach the already allocated gpio_chip to the
of_gpio_chip structure.
With this patch there are two ways to register OF GPIO cont
Some platforms (e.g. OpenFirmware) want to know when a particular chip
added or removed, so that the platforms could add their specifics for
non-platform devices, like I2C or SPI GPIO chips.
This patch implements the notifier for chip addition and removal events.
Signed-off-by: Anton Vorontsov
-
Hi all,
Here comes v2. Changes:
- In 'gpiolib: Introduce chip addition/removal notifier', open-coded
gpio_call_chain().
- In 'of/gpio: Add support for two-stage registration for the
of_gpio_chips', improved commit message.
David, I think it would be best if these patches could go via power
On Fri, Feb 5, 2010 at 9:16 AM, John Tyner wrote:
>
>
> Grant Likely wrote:
>>
>> On Mon, Feb 1, 2010 at 4:25 PM, John Tyner wrote:
>>>
>>> This patch adds support for using the LL TEMAC Ethernet driver on
>>> non-Virtex
>>> 5 platforms by adding support for accessing the Soft DMA registers as if
On Fri, Feb 5, 2010 at 10:50 AM, John Linn wrote:
>> -Original Message-
>> From: Grant Likely
>> Sent: Thurs, 4 Feb 2010 11:12:29 AM
>> To: John Linn
>> Subject: FW: [PATCH] net: emaclite: adding MDIO and phy lib support
>>
>> Hi John and Sadanand. Looks like a good patch, but a few issue
> -Original Message-
> From: Grant Likely
> Sent: Thurs, 4 Feb 2010 11:12:29 AM
> To: John Linn
> Subject: FW: [PATCH] net: emaclite: adding MDIO and phy lib support
>
> Hi John and Sadanand. Looks like a good patch, but a few issues to
> resolve. Comments below.
>
> g.
Somehow I didn'
Grant Likely wrote:
On Mon, Feb 1, 2010 at 4:25 PM, John Tyner wrote:
This patch adds support for using the LL TEMAC Ethernet driver on non-Virtex
5 platforms by adding support for accessing the Soft DMA registers as if
they were memory mapped instead of solely through the DCR's (available on
On Fri, 5 Feb 2010, Josh Boyer wrote:
> On Fri, Feb 05, 2010 at 02:49:14PM +0100, Geert Uytterhoeven wrote:
> >On Fri, 5 Feb 2010, Josh Boyer wrote:
> >> This allows the upgrade path from older kernel releases to work
> >> with the Fedora mkinitrd tool.
> >>
> >> ---
> >>
> >> --- linux-2.6.22.pp
On Fri, 5 Feb 2010, Josh Boyer wrote:
> This allows the upgrade path from older kernel releases to work
> with the Fedora mkinitrd tool.
>
> ---
>
> --- linux-2.6.22.ppc64/drivers/block/ps3disk.c~ 2007-07-25
> 16:06:16.0 +0100
> +++ linux-2.6.22.ppc64/drivers/block/ps3disk.c
On Fri, Feb 05, 2010 at 08:35:52AM -0500, Josh Boyer wrote:
>Hi All,
>
>Below are the set of ppc/ppc64 specific patches that Fedora has been
>carrying for a very long time now. It would be good to get some eyes
>on them to see if they could just be incorporated upstream.
David, I think you are th
On Fri, Feb 05, 2010 at 02:49:14PM +0100, Geert Uytterhoeven wrote:
>On Fri, 5 Feb 2010, Josh Boyer wrote:
>> This allows the upgrade path from older kernel releases to work
>> with the Fedora mkinitrd tool.
>>
>> ---
>>
>> --- linux-2.6.22.ppc64/drivers/block/ps3disk.c~ 2007-07-25
>> 16:06
On Fri, Feb 05, 2010 at 08:53:54AM -0500, Josh Boyer wrote:
>Provide a modalias entry for VIO devices in sysfs. I believe
>this was another initrd generation bugfix for anaconda.
Bah, subject on this should have been [PATCH 3/4] Provide VIO modalias
___
I have recently attempted to boot an 8641D based board from an NFS root.
The boot process grinds to a halt not long after the first access of the
NFS root and I receive multiple "nfs: server 192.168.0.1 not responding,
still trying" messages. Wireshark suggests that there is no further
traffic from
This works around the PCIe bridge setup on the iMac iSight boxen.
---
--- linux/arch/powerpc/platforms/powermac/pci.c~2008-03-22
19:08:07.0 +
+++ linux/arch/powerpc/platforms/powermac/pci.c 2008-03-23 09:10:46.0
+
@@ -1271,6 +1271,12 @@ void pmac_pci_fixup_pciata
Provide a modalias entry for VIO devices in sysfs. I believe
this was another initrd generation bugfix for anaconda.
---
diff --git a/arch/powerpc/kernel/vio.c b/arch/powerpc/kernel/vio.c
index f988672..12a0851 100644
--- a/arch/powerpc/kernel/vio.c
+++ b/arch/powerpc/kernel/vio.c
@@ -294,9 +29
This changes the thresholds for the liquid cooled G5 thermal
shutdown mechanism to prevent an errant shutdown.
This has been carried since about Fedora Core 5. I have no idea
if it's really needed or not.
---
--- linux-2.6.15/drivers/macintosh/therm_pm72.c.orig2006-04-02
21:34:48.0
Signed-off-by: Wolfgang Denk
Signed-off-by: Detlev Zundel
Signed-off-by: Anatolij Gustschin
Cc: Grant Likely
---
Provide this file for easier testing. Note that FEC
support is not enabled in this config. Enable it
manualy if FEC patches will be used for testing.
Changes since v1:
- place defc
Collects several changes needed after applying
previous mpc5121 platform and driver patches:
- Add mpc5121 reset module node
- Clean up and fix NAND description, remove unused properties
here and correct NAND flash chip size.
- Clean up I2C nodes: remove obsolete "cell-index" properties,
add "
MPC5121 DIU configuration/setup as initialized by the boot
loader currently will get lost while booting Linux. As a
result displaying the boot splash is not possible through
the boot process.
To prevent this we reserve configured DIU frame buffer
address range while booting and preserve AOI descri
Platform specific code for MPC5121 USB Host support.
The patch also contains changes to FSL EHCI platform driver
needed to support MPC5121 USB controller. MPC5121 Rev 2.0
silicon EHCI registers are in big endian format. The
appropriate flags are set using the information in the
platform data struc
Factor out common code for registering a FSL EHCI platform
device into new fsl_usb2_register_device() function. This
is done to avoid code duplication while adding code for
instantiating of MPC5121 dual role USB platform devices.
Then, the subsequent patch can use
for_each_compatible_node(np, NULL,
From: Piotr Ziecik
Adds initial version of MPC512x DMA driver.
Only memory to memory transfers are currenly supported.
Signed-off-by: Piotr Ziecik
Signed-off-by: Wolfgang Denk
Signed-off-by: Anatolij Gustschin
Cc: Dan Williams
Cc: Grant Likely
Cc: John Rigby
---
No changes since v2
Change
Instantiate NAND Flash Controller device if it's
description is found in the device tree.
Signed-off-by: Anatolij Gustschin
Cc: Grant Likely
---
arch/powerpc/platforms/512x/mpc512x_shared.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platforms/51
Adds NAND Flash Controller driver for MPC5121 Revision 2.
All device features, except hardware ECC and power management,
are supported.
Signed-off-by: Piotr Ziecik
Signed-off-by: Wolfgang Denk
Signed-off-by: Anatolij Gustschin
Cc:
Cc: Grant Likely
Cc: John Rigby
---
Changes since v2:
- move
Add support for MPC5121 real time clock module.
Signed-off-by: John Rigby
Signed-off-by: Piotr Ziecik
Signed-off-by: Wolfgang Denk
Signed-off-by: Anatolij Gustschin
Cc:
Cc: Grant Likely
Cc: John Rigby
---
Changes since v2:
- change commit message to describe what the patch is
- use __dev
Add reset module registers representation and
machine restart callback for mpc5121 platform.
Signed-off-by: Piotr Ziecik
Signed-off-by: Wolfgang Denk
Signed-off-by: Anatolij Gustschin
Cc: Grant Likely
Cc: John Rigby
---
Changes since v2:
- call mpc512x_restart_init() explicitely from platfor
Move mpc5121_clk_init() call to platform init code so it won't
get called on non-5121 platforms on a multiplatform kernel.
Signed-off-by: Anatolij Gustschin
Cc: Grant Likely
---
Note to avoid confusion: this patch is new and was not
in previous v2 patch series. It was generated as a cleanup
patc
The patches are based on v2.6.33-rc6 and cover the following
items:
- platform, DTS
- DMA
- DIU
- UART (without h/w flow control)
- I2C
- NAND
- RTC
The code has been tested on the Freescale/STX "MPC5121ADS" board
(board rev. 4) with a MPC5121e Rev. 2. No attempt was made to provide
backward comp
This allows the upgrade path from older kernel releases to work
with the Fedora mkinitrd tool.
---
--- linux-2.6.22.ppc64/drivers/block/ps3disk.c~ 2007-07-25 16:06:16.0
+0100
+++ linux-2.6.22.ppc64/drivers/block/ps3disk.c 2007-07-26 08:49:44.0
+0100
@@ -628,3 +628,4 @@ MODULE_L
Hi All,
Below are the set of ppc/ppc64 specific patches that Fedora has been
carrying for a very long time now. It would be good to get some eyes
on them to see if they could just be incorporated upstream.
josh
___
Linuxppc-dev mailing list
Linuxppc-de
49 matches
Mail list logo