All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>, "Ивайло Димитров" <freemangordon@abv.bg>
Cc: sre@ring0.de, sre@debian.org, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Compile failure on linux-n900 branch -- MEDIA_CAMERA_SUPPORT needed for n900 compilation
Date: Sun, 1 Dec 2013 21:36:39 +0100	[thread overview]
Message-ID: <201312012136.39919@pali> (raw)
In-Reply-To: <20131201202500.GA24067@amd.pavel.ucw.cz>

[-- Attachment #1: Type: Text/Plain, Size: 1647 bytes --]

On Sunday 01 December 2013 21:25:00 Pavel Machek wrote:
> Hi!
> 
> Interesting; with Sebastian DT config
> (http://elektranox.org/n900-kernel-config.txt), I get the same
> 
> 
> 
> [   17.967651] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.968109] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.968566] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969055] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969512] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969970] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.970428] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.970886] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.971313] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.967651] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.968109] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.968566] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969055] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969512] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.969970] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.970428] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.970886] omap_i2c 48070000.i2c: Too much work in one IRQ
> [   17.971313] omap_i2c 48070000.i2c: Too much work in one IRQ
> 
> ...infinite loop during bootup. So, Sebastian, it looks
> problem is in linux-n900, too. Will switch to defconfig, that
> worked...
> 
> 									Pavel

Today freemangordon wrote (on IRC), that i2c is broken in 3.13.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-12-01 20:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 12:51 hci_h4p from linux-n900 branch: fix with new bluetooth for 3.13-rc1 Pavel Machek
2013-11-27 14:59 ` Pali Rohár
2013-11-27 19:13   ` Pavel Machek
2013-11-27 19:44     ` Pali Rohár
2013-11-29 23:58       ` Pali Rohár
2013-11-30 17:29         ` Pavel Machek
2013-11-30 23:15           ` device-tree based boot on linux-n900 branch Pavel Machek
2013-12-01  9:50             ` Pali Rohár
2013-12-01 10:24               ` Sebastian Reichel
2013-12-01 19:21               ` Compile failure on linux-n900 branch -- MEDIA_CAMERA_SUPPORT needed for n900 compilation Pavel Machek
2013-12-01 19:25                 ` Pali Rohár
2013-12-01 20:01                   ` Pavel Machek
2013-12-01 20:25                     ` Pavel Machek
2013-12-01 20:36                       ` Pali Rohár [this message]
2013-12-02  9:23                         ` linux-n900: minor coding style fixes Pavel Machek
2013-12-01 20:29                     ` Compile failure on linux-n900 branch -- MEDIA_CAMERA_SUPPORT needed for n900 compilation Pali Rohár
2013-12-01 10:48   ` hci_h4p from linux-n900 branch: fix with new bluetooth for 3.13-rc1 Sebastian Reichel
2013-12-01 11:16     ` Pali Rohár
2013-12-01 11:30       ` Sebastian Reichel
     [not found] ` <201312021613.19521@pali>
     [not found]   ` <20131204122204.GA10262@amd.pavel.ucw.cz>
     [not found]     ` <201312041732.05400@pali>
2013-12-05 11:56       ` [patch] fix n900 bt error handling Pavel Machek
2013-12-05 13:08         ` Pali Rohár

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201312012136.39919@pali \
    --to=pali.rohar@gmail.com \
    --cc=freemangordon@abv.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sre@debian.org \
    --cc=sre@ring0.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.