* Sebastian Reichel <sebastian.reichel@xxxxxxxxxxxxxxx> [170710 03:16]:
> Hi,
>
> On Mon, Jul 10, 2017 at 10:13:35AM +0200, Pavel Machek wrote:
> > On Mon 2017-07-10 09:46:10, Pavel Machek wrote:
> > > Hi!
> > >
> > > First, I got segfault from make:
> > >
> > > : 0: Can't open
> > > scripts/Makefile.build:561: recipe for target
> > > 'drivers/iio/imu/st_lsm6dsx' failed
> > > make[3]: *** [drivers/iio/imu/st_lsm6dsx] Segmentation fault (core
> > > dumped)
> > > scripts/Makefile.build:561: recipe for target 'drivers/iio/imu' failed
> > > make[2]: *** [drivers/iio/imu] Error 2
> > > scripts/Makefile.build:561: recipe for target 'drivers/iio' failed
> > > make[1]: *** [drivers/iio] Error 2
> > > make[1]: *** Waiting for unfinished jobs....
> > > Makefile:1008: recipe for target 'drivers' failed
> > > make: *** [drivers] Error 2
> > > make: *** Waiting for unfinished jobs....
> > > pavel@duo:/data/l/linux-n900$ ./mkit
> > >
> > > Then compile worked, but it failed to boot. I've now cleaned caches
> > > and am rebuilding to make sure it is not build machine that has
> > > glitches.
> > >
> > > No such luck :-(.
> > >
> > > I tested linux-next relatively recently, and it worked ok.
> >
> > > af3c8d98508d37541d4bf57f13a984a7f73a328c is broken.
> > > 650fc87 worked ok.
> >
> > 2b97620 is broken.
> >
> > commit a51166ce71844ffbb8f78d63647b44dd69e46cf1
> > Add linux-next specific files for 20170628
>
> I just rebased my droid4 development branch. I do not have any
> problems with segfaulting toolchain, but boot also fails on OMAP4
> based Droid 4. The problem seems to be SPI being accessed without
> runtime PM (clocks) being enabled:
Care to check if commit c5b3955828ba ("ARM: OMAP4: Fix legacy code
clean-up regression") make that one go away? I have already sent
a pull request for that one.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
