linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] staging/dream: add missing include files/fix compilation
Date: Thu, 25 Feb 2010 20:41:25 +0100	[thread overview]
Message-ID: <20100225194125.GA7645@elf.ucw.cz> (raw)
In-Reply-To: <1267126586.5439.56.camel@c-dwalke-linux.qualcomm.com>

Hi!

> > > /home/dwalker/linux-2.6/drivers/video/msm/msm_fb.c:24: fatal error: linux/msm_mdp.h: No such file or directory
> > > compilation terminated.
> > > make[4]: *** [drivers/video/msm/msm_fb.o] Error 1
> > > make[3]: *** [drivers/video/msm] Error 2
> > > make[3]: *** Waiting for unfinished jobs....
> > > make[2]: *** [drivers/video] Error 2
> > > make[1]: *** [drivers] Error 2
> > > make: *** [sub-make] Error 2
> > 
> > Yes, framebuffer has problems.
> > 
> > > Even with the framebuffer off I still don't get any serial output on a
> > > plain 2.6.33-rc6 .. I'm using a config that you sent me when you first
> > > tested my -next tree .
> > 
> > 2.6.33 boots here, with attached config. I'll try -next next.
> 
> My -next tree hasn't changed much since you last looked at it .. I
> wouldn't bother testing it. I might take some small fixes from that tree
> to merge, but what's there is still too much of a mess to merge.

Ok, so your -next tree will not be merged for 2.6.34?

> I just pushed another tree called "working-mmc" which still needs some
> clean up but should have working mmc if you want to test that.

Do you have git url? Yes, I'd like to play.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-02-25 19:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 20:59 [PATCH] staging/dream: add missing include files/fix compilation Pavel Machek
2010-01-15  0:24 ` Greg KH
2010-01-19  5:45   ` Pavel Machek
2010-01-19 15:14     ` Daniel Walker
2010-01-31  8:44       ` Pavel Machek
2010-01-31  9:28         ` Pavel Machek
2010-01-31 15:58           ` Daniel Walker
2010-02-25 19:30             ` Pavel Machek
2010-02-25 19:36               ` Daniel Walker
2010-02-25 19:41                 ` Pavel Machek [this message]
2010-02-25 19:48                   ` Daniel Walker
     [not found]                     ` <20100226213107.GA29615@elf.ucw.cz>
     [not found]                       ` <1267469856.29769.9.camel@c-dwalke-linux.qualcomm.com>
2010-03-01 21:10                         ` Pavel Machek
2010-03-01 21:15                           ` Daniel Walker
2010-03-01 21:41                             ` Pavel Machek
2010-03-03  6:48                             ` Pavel Machek
2010-01-31 13:31         ` Daniel Walker
2010-01-19 15:54     ` Greg KH

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=20100225194125.GA7645@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).