Hello,
I hope someone could help me with my problem. Currently I am porting
a new kernel (3.3.8) for a tqm5200s based board.
The previous kernel was 2.6.23. The new kernel version is needed because
of support for a wireless card.
I got issues with the i2c bus and this kernel. When the kernel boot
> The dtb file from the kernel 2.6.23 looks as follows:
> i2c@3d40 {
>
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "fsl,mpc5200-i2c","fsl-i2c";
> reg = <0x3d40 0x40>;
> interrupts = <2 16 0>;
> fsl5200-clocking;
> };
sry, but this was a mistake. This is the
Hi,
On Thu, 3 Jan 2013 14:20:41 +0100
Johannes Braun wrote:
> Hello,
>
> I hope someone could help me with my problem. Currently I am porting
> a new kernel (3.3.8) for a tqm5200s based board.
> The previous kernel was 2.6.23. The new kernel version is needed because
> of support for a wireless
On Sun, Nov 25, 2012 at 10:51 PM, Olof Johansson wrote:
> Enable PRINTK_TIME in pasemi_defconfig. Also regenerate it, it seems
> that a lot of options have moved around since last time savedefconfig
> was ran on it.
>
> Signed-off-by: Olof Johansson
Ping?
-Olof
On Thu, 2013-01-03 at 12:54 -0800, Olof Johansson wrote:
> On Sun, Nov 25, 2012 at 10:51 PM, Olof Johansson wrote:
> > Enable PRINTK_TIME in pasemi_defconfig. Also regenerate it, it seems
> > that a lot of options have moved around since last time savedefconfig
> > was ran on it.
> >
> > Signed-of
On Fri, Dec 28, 2012 at 05:13:18PM -0200, Thadeu Lima de Souza Cascardo wrote:
>The functions used are already defined as empty inline functions for the
>case where EEH is disabled.
>
>Signed-off-by: Thadeu Lima de Souza Cascardo
Acked-by: Gavin Shan
>---
> arch/powerpc/kernel/of_platform.c |
On Fri, Dec 28, 2012 at 05:13:19PM -0200, Thadeu Lima de Souza Cascardo wrote:
>The DDW code uses a eeh_dev struct from the pci_dev. However, this is
>not set until eeh_add_device_late is called.
>
>Since pci_bus_add_devices is called before eeh_add_device_late, the PCI
>devices are added to the bu
On Wed, 2012-10-24 at 08:45 +0300, Robert Berger wrote:
> Hi Ben,
> >
> > Remind me what is the symptom ? A specific device isn't working ? Or the
> > whole kernel goes toast ?
>
> The whole kernel goes toast! Just reboots without saying much before;)
>
> > My feeling is that those patches make M
On Sun, 23 Dec 2012 at 13:34, Christian Kujau wrote:
> On Sat, 22 Dec 2012 at 16:28, Maciej Rutecki wrote:
> > Got during suspend to disk:
>
> I got a similar message on a powerpc G4 system, right after bootup (no
> suspend involved):
>
> http://nerdbynature.de/bits/3.8.0-rc1/
FWIW, this i
On most architectures (arm, mips, s390, sh and x86) idle thread of a cpu does
not cleanly exit nohz state before dying upon hot-remove. As a result,
offline cpu is seen to be in nohz mode (ts->idle_active = 1) and its offline
time can potentially be included in total idle time reported via /proc/st
Modify idle loop of arm, mips, s390, sh and x86 architectures to exit from nohz
state before dying upon hot-remove. This change is needed to avoid userspace
tools like top command from seeing a rollback in total idle time over some
sampling periods.
Additionaly, modify idle loop on all architectur
With offline cpus no longer beeing seen in nohz mode (ts->idle_active=0), we
don't need the check for cpu_online() introduced in commit 7386cdbf. Offline
cpu's idle time as last recorded in its ts->idle_sleeptime will be reported
(thus excluding its offline time as part of idle time statistics).
C
On Thu, 2012-11-29 at 08:42 -0800, Carl E. Love wrote:
> Ben:
>
> Please review the following patch. If it is acceptable, will you please
> commit it to the mainline tree. Thanks.
>
> Carl Love
>
> P.S. Looks like I sent it to the wrong mailing list the first time to
> get it in
On Tue, 2012-12-11 at 11:18 +0530, Suzuki K. Poulose wrote:
> On 12/03/2012 08:37 PM, Suzuki K. Poulose wrote:
> > From: Suzuki K. Poulose
> >
> > External/Decrement exceptions have lower priority than the Debug Exception.
> > So, we don't have to disable the External interrupts before a single st
> This is expected since you didn't add sub-nodes for your i2c devices
> 24c32a and PCF8563 in the i2c adapter node.
Ok this was the issue.
>> Is there something wrong with my dtb file or is it a bug in the mpc-i2c
>> driver
>
> It is an issue with our dtb file. Please look at the I2C eeprom
> s
15 matches
Mail list logo
