[git pull] 5200 defconfigs and bootwrapper fix

2010-01-05 Thread Grant Likely
Hi Ben, Here's the 5200 defconfig updates and a fix for build errors when U-Boot's 'mkimage' tool isn't in $PATH. g. The following changes since commit 74d2e4f8d79ae0c4b6ec027958d5b18058662eea: Linus Torvalds (1): Linux 2.6.33-rc3 are available in the git repository at: git://git.s

[patch 1/6] powerpc: cpumask_of_node() should handle -1 as a node

2010-01-05 Thread Anton Blanchard
pcibus_to_node can return -1 if we cannot determine which node a pci bus is on. If passed -1, cpumask_of_node will negatively index the lookup array and pull in random data: # cat /sys/devices/pci:00/:00:01.0/local_cpus ,0003,, # cat /sys/devices/pci:00/

Re: How to set GPIO state in the dts or in platform

2010-01-05 Thread Ayman El-Khashab
On 1/5/2010 10:38 PM, Bill Gatliff wrote: Ayman El-Khashab wrote: I've got a custom board akin to the walnut. I've successfully got u-boot, the kernel, and a working filesystem. The only thing I lack is a clear idea of how to set a GPIO. Isn't that the "flags" parameter, e.g.: gpios

Re: How to set GPIO state in the dts or in platform

2010-01-05 Thread Bill Gatliff
Ayman El-Khashab wrote: > I've got a custom board akin to the walnut. I've successfully got > u-boot, > the kernel, and a working filesystem. The only thing I lack is a > clear idea > of how to set a GPIO. Isn't that the "flags" parameter, e.g.: gpios = ? If you are passing a 0 for the flags

How to set GPIO state in the dts or in platform

2010-01-05 Thread Ayman El-Khashab
I've got a custom board akin to the walnut. I've successfully got u-boot, the kernel, and a working filesystem. The only thing I lack is a clear idea of how to set a GPIO. I have the PHY reset connected to GPIO 3. I've got it setup in u-boot correctly, but by the time linux boots, it has tou

Re: [PATCH 0/2] *** SUBJECT HERE ***

2010-01-05 Thread Bill Gatliff
Bill Gatliff wrote: > *** BLURB HERE *** > Dangit, sometimes I really hate it when emacs leaves its backup files around... :( Like now, for example. Please disregard the noise generated by my careless use of filename wildcards... b.g. -- Bill Gatliff Embedded systems training and consult

[RFC/PATCH 0/2] Updates to improve device tree support

2010-01-05 Thread Bill Gatliff
This patch series updates the pca953x GPIO driver to take advantage of the new of_i2c_gpiochip_add() function, which registers i2c GPIO devices with the device tree API. These changes allow i2c-based GPIO expanders to be properly referenced from the proper entries in a device tree. The of_i2c_gpi

[PATCH 2/2] Reorder initialization to better support device tree data

2010-01-05 Thread Bill Gatliff
This patch changes the initialization sequence implemented in pca953x_probe(), so as to simplify the retrieval of device tree data when device trees are used. Incorporates the new of_i2c_gpiochip_add() function to register the newly-added GPIOs. Signed-off-by: Bill Gatliff --- drivers/gpio/pca9

[PATCH 1/2] Use struct of_i2c_gpio_chip instead of raw struct gpio_chip

2010-01-05 Thread Bill Gatliff
This patch is the first in a series that improves the pca953x driver's support for CONFIG_OF_GPIO a.k.a. device trees. It modifies the driver's chip structure definition to use a struct gpio_chip contained in a struct of_i2c_gpio_chip when CONFIG_OF_GPIO is set. If OF_GPIO is not used, an ordinar

[PATCH 0/2] *** SUBJECT HERE ***

2010-01-05 Thread Bill Gatliff
*** BLURB HERE *** Bill Gatliff (2): Use struct of_i2c_gpio_chip instead of raw struct gpio_chip Reorder initialization to better support device tree data drivers/gpio/pca953x.c | 168 +--- 1 files changed, 88 insertions(+), 80 deletions(-) _

[PATCH 1/2] Create a struct of_i2c_gpio_chip, for i2c-based GPIO devices

2010-01-05 Thread Bill Gatliff
Signed-off-by: Bill Gatliff --- include/linux/of_gpio.h | 23 +++ 1 files changed, 23 insertions(+), 0 deletions(-) diff --git a/include/linux/of_gpio.h b/include/linux/of_gpio.h index fc2472c..0c39242 100644 --- a/include/linux/of_gpio.h +++ b/include/linux/of_gpio.h @@ -

[PATCH 0/2] Create an of_i2c_gpiochip_add()

2010-01-05 Thread Bill Gatliff
This patch series creates an of_i2c_gpiochip_add() function, to allow i2c-based GPIO expanders to work with device tree gpio specifications. Bill Gatliff (2): Create a struct of_i2c_gpio_chip, for i2c-based GPIO devices Create an of_i2c_gpiochip_add() drivers/of/gpio.c | 55 +

[PATCH 2/2] Create an of_i2c_gpiochip_add()

2010-01-05 Thread Bill Gatliff
Signed-off-by: Bill Gatliff --- drivers/of/gpio.c | 55 + 1 files changed, 55 insertions(+), 0 deletions(-) diff --git a/drivers/of/gpio.c b/drivers/of/gpio.c index 6eea601..56b438a 100644 --- a/drivers/of/gpio.c +++ b/drivers/of/gpio.c @@ -

[PATCH -tip 3/8] x86/ptrace: Remove unused regs_get_argument_nth API

2010-01-05 Thread Masami Hiramatsu
Because of dropping function argument syntax from kprobe-tracer, we don't need this API anymore. Signed-off-by: Masami Hiramatsu Cc: Ingo Molnar Cc: Frederic Weisbecker Cc: Roland McGrath Cc: Oleg Nesterov Cc: Mahesh Salgaonkar Cc: Benjamin Herrenschmidt Cc: Michael Neuling Cc: Steven Rost

[PATCH -tip 2/8] tracing/kprobe: Drop function argument access syntax

2010-01-05 Thread Masami Hiramatsu
Drop function argument access syntax, because the function arguments are depends on not only architecture but also compile-options and function API. And now, we have perf-probe for finding register/memory assigned to each argument. Signed-off-by: Masami Hiramatsu Cc: Ingo Molnar Cc: Frederic Wei

[PATCH net-next v2 2/3] can: mscan-mpc5xxx: add support for the MPC512x processor

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger The main differences compared to the MSCAN on the MPC5200 are: - More flexibility in choosing the CAN source clock and frequency: Three different clock sources can be selected: "ip", "ref" or "sys". For the latter two, a clock divider can be defined as well. If the

[PATCH net-next v2 3/3] powerpc/mpc5xxx: add OF platform binding doc for FSL MSCAN devices

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger This patch adds documentation for the MSCAN OF device bindings for the MPC512x and moves the one for the MPC5200 to the new common file "Documentation/powerpc/dts-bindings/fsl/can.txt". Signed-off-by: Wolfgang Grandegger Acked-by: Wolfram Sang --- Documentation/power

[PATCH net-next v2 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x

2010-01-05 Thread Wolfgang Grandegger
This patch series adds support for the MPC512x from Freescale to the mpc5xxx_can MSCAN driver. Changes since v1: - Various coding style issues, printk formats, variable names and error messagaes and typos fixes or improved - MPC5xxx specific data are now passed to mpc5xxx_can_probe() via "of

[PATCH net-next v2 1/3] can: mscan: fix improper return if dlc < 8 in start_xmit function

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger The start_xmit function of the MSCAN Driver did return improperly if the CAN dlc check failed (skb not freed and invalid return code). This patch adds a proper check of the frame lenght and data size and returns now correctly. Furthermore, a typo has been fixed. Signed-

[PATCH net-next v2 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x

2010-01-05 Thread Wolfgang Grandegger
This patch series adds support for the MPC512x from Freescale to the mpc5xxx_can MSCAN driver. Changes since v1: - Various coding style issues, printk formats, variable names and error messagaes and typos fixes or improved - MPC5xxx specific data are now passed to mpc5xxx_can_probe() via of_

[PATCH net-next v2 1/3] can: mscan: fix improper return if dlc < 8 in start_xmit function

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger The start_xmit function of the MSCAN Driver did return improperly if the CAN dlc check failed (skb not freed and invalid return code). This patch adds a proper check of the frame lenght and data size and returns now correctly. Furthermore, a typo has been fixed. Signed-

[PATCH net-next v2 2/3] can: mscan-mpc5xxx: add support for the MPC512x processor

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger The main differences compared to the MSCAN on the MPC5200 are: - More flexibility in choosing the CAN source clock and frequency: Three different clock sources can be selected: "ip", "ref" or "sys". For the latter two, a clock divider can be defined as well. If the

[PATCH net-next v2 3/3] powerpc/mpc5xxx: add OF platform binding doc for FSL MSCAN devices

2010-01-05 Thread Wolfgang Grandegger
From: Wolfgang Grandegger This patch adds documentation for the MSCAN OF device bindings for the MPC512x and moves the one for the MPC5200 to the new common file "Documentation/powerpc/dts-bindings/fsl/can.txt". Signed-off-by: Wolfgang Grandegger Acked-by: Wolfram Sang --- Documentation/power

Re: powerpc: allmod config build failure

2010-01-05 Thread Avi Kivity
On 01/05/2010 03:03 PM, Alexander Graf wrote: On 05.01.2010, at 04:32, Stephen Rothwell wrote: Hi all, The powerpc allmodconfig build of Linus' tree has been failing like this since Dec 13 (and linux-next since Nov 7): arch/powerpc/kvm/built-in.o:(.toc1+0x18): undefined reference to `kvm

Re: powerpc: allmod config build failure

2010-01-05 Thread Alexander Graf
On 05.01.2010, at 04:32, Stephen Rothwell wrote: > Hi all, > > The powerpc allmodconfig build of Linus' tree has been failing like this > since Dec 13 (and linux-next since Nov 7): > > arch/powerpc/kvm/built-in.o:(.toc1+0x18): undefined reference to > `kvm_debugfs_dir' > > $ grep KVM .config

[PATCH] powerpc: fix pseries/dlpar compile warning without CONFIG_PROC_DEVICETREE

2010-01-05 Thread FUJITA Tomonori
cc1: warnings being treated as errors arch/powerpc/platforms/pseries/dlpar.c: In function 'dlpar_attach_node': arch/powerpc/platforms/pseries/dlpar.c:239: error: unused variable 'ent' arch/powerpc/platforms/pseries/dlpar.c: In function 'dlpar_detach_node': arch/powerpc/platforms/pseries/dlpar.c:271

Xilinx LL-Temac driver with two network interfaces

2010-01-05 Thread Mirek23
Dear All, I am successfully using LL-Temac driver on Virtex-4 cheap under linux 2.6.*. All works fine with one Network interface. Does anybody know how to configure the systems to deal with two network interfaces? I will be grateful for any hint. M. -- View this message in context: http://old