linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michael Welling <mwelling@ieee.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Tony Lindgren" <tony@atomide.com>,
	"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Nishanth Menon" <nm@ti.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux 4.2-rc1 broken Nokia N900
Date: Tue, 21 Jul 2015 11:34:41 +0200	[thread overview]
Message-ID: <20150721093441.GA23241@amd> (raw)
In-Reply-To: <20150720204647.GA11931@deathstar>

On Mon 2015-07-20 15:46:47, Michael Welling wrote:
> On Tue, Jul 14, 2015 at 09:14:12AM +0200, Pali Rohár wrote:
> > On Monday 13 July 2015 17:36:07 Michael Welling wrote:
> > > On Tue, Jul 14, 2015 at 12:02:44AM +0200, Pali Rohár wrote:
> > > > I think nothing special. I just call:
> > > > 
> > > > export ARCH=arm
> > > > export CROSS_COMPILE=arm-linux-gnueabi-
> > > > make rx51_defconfig
> > > > rm -f arch/arm/boot/zImage
> > > > make -j12 zImage modules omap3-n900.dtb CONFIG_DEBUG_SECTION_MISMATCH=y
> > > > cat arch/arm/boot/zImage arch/arm/boot/dts/omap3-n900.dtb > arch/arm/boot/zImage.new
> > > > mv arch/arm/boot/zImage.new arch/arm/boot/zImage
> > > >
> > > 
> > > Where are you getting rx51_defconfig from?
> > > 
> > > This does not appear to be in the kernel source any longer.
> > > 
> > > Can you try the above with omap2plus_defconfig?
> > >  
> > 
> > It is in my linux-n900 repository: https://github.com/pali/linux-n900
> > Repository contains more n900 specific patches but SPI code is unpatched
> > 
> > https://github.com/pali/linux-n900/blob/HEAD/arch/arm/configs/rx51_defconfig
> > 
> > Later in week I can try to compile also with omap2plus_defconfig...
> > But in my opinion kernel should not crash with different configuration.
> 
> Has any progress been made on this?
> 
> Seeing as I was dropped into the middle of this thread,
> I took a look at the discussion previous.
> 
> It appears that you are building the drivers as modules.
> Perhaps I can again attempt to duplicate the issue using modules.
> Though this should not make a difference.

Actually.. for the record I'm _not_ using modules. So either I hit
something different, or problem happens regardless of modules.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2015-07-21  9:34 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 12:05 linux 4.2-rc1 broken Nokia N900 Pali Rohár
2015-07-13  6:44 ` Tony Lindgren
2015-07-13  8:09   ` Sebastian Reichel
2015-07-13 17:03     ` Michael Welling
2015-07-13 17:09       ` Pali Rohár
2015-07-13 17:56         ` Michael Welling
2015-07-13 20:28         ` Michael Welling
2015-07-13 20:34           ` Pali Rohár
2015-07-13 21:52             ` Michael Welling
2015-07-13 22:02               ` Pali Rohár
2015-07-13 22:36                 ` Michael Welling
2015-07-14  7:14                   ` Pali Rohár
2015-07-14  7:45                     ` Tony Lindgren
2015-07-14 16:33                     ` Michael Welling
2015-07-14 20:01                       ` Pavel Machek
2015-07-14 20:17                         ` Michael Welling
2015-07-15 19:49                           ` Pavel Machek
2015-07-15 20:10                             ` Michael Welling
2015-07-21  7:31                               ` Pavel Machek
2015-07-21  7:33                                 ` Pavel Machek
2015-07-21  8:04                                   ` Pali Rohár
2015-07-20 20:48                             ` Michael Welling
2015-07-20 20:46                     ` Michael Welling
2015-07-20 20:58                       ` Pali Rohár
2015-07-21  9:34                       ` Pavel Machek [this message]
2015-07-21 21:28                         ` Michael Welling
2015-07-22  0:17                         ` Michael Welling
2015-07-22  2:03                           ` Sebastian Reichel
2015-07-22  5:13                             ` Michael Welling
2015-07-22  7:27                               ` Pali Rohár
2015-07-22 13:33                                 ` Sebastian Reichel
2015-07-22 14:27                                   ` Pali Rohár
2015-07-22 13:30                             ` Pavel Machek
2015-07-25  8:55                             ` Pali Rohár
2015-07-28  8:39                               ` Pali Rohár
2015-07-28 12:26                                 ` Sebastian Reichel
2015-07-28 12:32                                   ` Pali Rohár
2015-07-13 11:10   ` Pali Rohár
2015-07-13 13:26     ` Tony Lindgren
2015-07-13 15:51 ` Sebastian Reichel
2015-07-13 16:05   ` Pali Rohár
2015-07-13 19:32     ` Sebastian Reichel
2015-07-14  0:18       ` Krzysztof Kozlowski
2015-07-24  8:18 ` Dave Young
2015-07-24  8:30   ` Ivaylo Dimitrov
2015-07-24 10:28     ` Dave Young
2015-07-24 10:53       ` Pali Rohár
2015-07-24  8:40   ` Pali Rohár
2015-07-24 10:33     ` Dave Young
2015-07-24 10:52       ` Pali Rohár
2015-07-24 15:50     ` Pali Rohár
2015-07-24  8:51   ` Pavel Machek
2015-07-24 10:39     ` Dave Young

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=20150721093441.GA23241@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mwelling@ieee.org \
    --cc=nm@ti.com \
    --cc=pali.rohar@gmail.com \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).