public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: N810: linux-2.6.26-rc2-omap1 with muru.com N810 patches (success)
Date: Thu, 15 May 2008 18:10:58 -0500	[thread overview]
Message-ID: <20080515231058.GB11713@swansys> (raw)
In-Reply-To: <20080515202511.GT8928@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

On Thu, 2008.05.15, 136, Tony Lindgren wrote:
> * green <greenfreedom10@gmail.com> [080515 12:45]:
> > Okay, I've got the zImage and updated patches; thanks.  This zImage does work, 
> > but fails to mount root device (maybe something I did wrong; I'll worry about 
> > that later).  Could you send the config you used?  Or maybe I'm doing 
> > something wrong when compiling.
> 
> The last patch in the series contains the changes to n800_defconfig.
> Also attached as .config.

I don't understand, then, why there are differences between the config 
generated by 'make n800_defconfig' and the config you attached.  Like 
CONFIG_FRAMEBUFFER_CONSOLE is Y in the attached config but N in the generated 
config (and others).

> > I'm compiling on an amd64 system with the following packages (and their 
> > dependencies) from emdebian.org:
> > binutils-arm-linux-gnueabi 2.18.1~cvs20080103-4
> > cpp-4.3-arm-linux-gnueabi 4.3.0-4
> > g++-4.3-arm-linux-gnueabi 4.3.0-4
> > gcc-4.3-arm-linux-gnueabi 4.3.0-4
> > 
> > and in the Makefile:
> > CROSS_COMPILE   ?= arm-linux-gnueabi-
> > 
> > For now I'll try with the latest from linux-omap-2.6 with your patches.
> 
> Yeah that should work. Just dor ARCH=arm CROSS_COMPILE=gcc-4.3-arm-linux-gnueabi-
> If in doubt, you can also try the codesourcery toolchain, but sounds
> like your compiler is just fine.

I have been using the Makefile instead, just changing this:
CROSS_COMPILE ?= arm-linux-gnueabi-

But that still doesn't work so:

I installed 4.2.3-5 of cpp, g++, and gcc and tried it again and finally it 
works.  So I guess I can blame the 4.3 packages, because I have been using them 
all this time in some form, both in the chroot and on the amd64 system.  I 
should have tried 4.2 earlier.

Thanks for your help.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-05-15 23:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 14:09 N810: linux-2.6.26-rc2-omap1 with muru.com N810 patches green
2008-05-15 16:14 ` Felipe Balbi
2008-05-15 18:19   ` green
2008-05-15 16:54 ` green
2008-05-15 18:28   ` Tony Lindgren
2008-05-15 19:33     ` green
2008-05-15 20:25       ` Tony Lindgren
2008-05-15 23:10         ` green [this message]

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=20080515231058.GB11713@swansys \
    --to=greenfreedom10@gmail.com \
    --cc=linux-omap@vger.kernel.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