public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Greg KH <greg@kroah.com>, Arve Hj?nnev?g <arve@android.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Brian Swetland <swetland@google.com>,
	Iliyan Malchev <malchev@google.com>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] staging/dream: add missing include files/fix compilation
Date: Sun, 31 Jan 2010 10:28:29 +0100	[thread overview]
Message-ID: <20100131092829.GJ2238@elf.ucw.cz> (raw)
In-Reply-To: <20100131084421.GG2238@elf.ucw.cz>

Hi!

> > > > > This adds missing include files, so it should now compile. ifdef
> > > > > guards were added to Kconfig, so it should not cause problems on
> > > > > non-arch-msm machines.
> > > > > 
> > > > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > > > 
> > > > Odd, this doesn't apply to the linux-next tree, some of the files are
> > > > already there.
> > > 
> > > Strange, it seems it is almost all already in. Well, good :-).
> > > 
> > > But there's small problem. linux-next now contains dwalker's tree, and
> > > I could not get it to compile, even with staging disabled. I'll need
> > > to look into that.
> > 
> > I worked on it a little, but I won't have time to really start cleaning
> > up that tree till next week, or this weekend.
> > 
> > I pushed a new tree for next that should compile for dream with the
> > attached config. I also included the patch that I added to get it to
> > compile (you'll need the machine types too which I didn't include).
> 
> Thanks! I checked out linux-next version, and it seems to include
> 
> > commit cdf6c137865357112aa31666b65b938ab29fa736
> >     msm: compile fixes for dream.
> 
> this patch. It still fails with:
> 
> arch/arm/mach-msm/rpc_hsusb.c: In function 'msm_chg_rpc_connect':
> arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
> function 'machine_is_msm7201a_surf'
> arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
> function 'machine_is_msm7x27_surf'
> arch/arm/mach-msm/rpc_hsusb.c:157: error: implicit declaration of
> function 'machine_is_qsd8x50_surf'
> make[1]: *** [arch/arm/mach-msm/rpc_hsusb.o] Error 1
> make: *** [arch/arm/mach-msm] Error 2
> 
> (and similar error further down). This fixes it, but you probably want
> to add machine_is_* to your git. (Aha, is that what you meant by
> "machine types"?
> 
> With this patch it compiles.

Ok, it compiles, but I do not see it booting. You config has:

CONFIG_MSM_DEBUG_UART=3
# CONFIG_MSM_DEBUG_UART_NONE is not set
# CONFIG_MSM_DEBUG_UART1 is not set
# CONFIG_MSM_DEBUG_UART2 is not set
CONFIG_MSM_DEBUG_UART3=y
...
CONFIG_DEBUG_LL=y
CONFIG_EARLY_PRINTK=y

set, so I'd expect it to say something on the serial line... (right?
Or do I still need to patch printk.c to get that?). And I see nothing
:-(.

I'm using

./fastboot -c "console=ttyMSM2 root=/dev/mmcblk0p1 rootdelay=5 fbcon=rotate:1" boot /data/l/linux-dwalker/arch/arm/boot/zImage

...with different kernel, it works (as in "I get most of the boot on
serial line; it will not actually mount root").
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-01-31  9:28 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 [this message]
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
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=20100131092829.GJ2238@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=dwalker@codeaurora.org \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malchev@google.com \
    --cc=swetland@google.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