linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Kenneth Fairweather <kenneth.fairweather@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: errors compiling 2.6.20 for mpc866ads
Date: Fri, 2 Mar 2007 19:32:04 +0300	[thread overview]
Message-ID: <20070302193204.3a0e5047@vitb.dev.rtsoft.ru> (raw)
In-Reply-To: <200703021625.14661.kenneth.fairweather@freescale.com>

On Fri, 2 Mar 2007 16:25:14 +0000
Kenneth Fairweather <kenneth.fairweather@freescale.com> wrote:

> Compiling a vanilla 2.6.20 kernel and applying Vitaly Bordug's 7 patches (21st 
> Jan'07) for mpc866_ads_defconfig gives compiler errors:
> 
>   LD      arch/powerpc/platforms/8xx/built-in.o
>   LD      arch/powerpc/platforms/built-in.o
>   CC      drivers/net/fs_enet/fs_enet-main.o
> linux-2.6.20/drivers/net/fs_enet/fs_enet-main.c: In function `setup_immap':
> inux-2.6.20/drivers/net/fs_enet/fs_enet-main.c:1139: error: `IMAP_ADDR' 
> undeclared (first use in this function)
>

Please update to current Linus' git and retry. All patches should be in there,
let me know if not and/or something not working.
 
> Are these patches for 2.6.20 kernel, and/or are there other patches required? 
> should I still be using ppc branch?
> 
> Also, tried to grab Vitaly's git tree, but it is failing on http (I'm behind a 
> firewall). Is this a known problem?
> 
> cg-clone http://source.mvista.com/git/linux-2.6-vitb.git
> defaulting to local storage area
> Fetching head...
> cg-fetch: unable to get the HEAD branch
> 
Heh, sort of - I've synced my tree with mainline a while ago which reminds me to have a look at it...

-- 
Sincerely, 
Vitaly

      reply	other threads:[~2007-03-02 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 16:25 errors compiling 2.6.20 for mpc866ads Kenneth Fairweather
2007-03-02 16:32 ` Vitaly Bordug [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=20070302193204.3a0e5047@vitb.dev.rtsoft.ru \
    --to=vbordug@ru.mvista.com \
    --cc=kenneth.fairweather@freescale.com \
    --cc=linuxppc-embedded@ozlabs.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).