All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Wolfgang Denk <wd@denx.de>
Cc: u-boot-users@lists.sourceforge.net,
	ppcembed Mailing List <linuxppc-embedded@ozlabs.org>
Subject: OT: Re: [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11
Date: Tue, 05 Sep 2006 15:28:54 +0200	[thread overview]
Message-ID: <44FD7B96.80405@anagramm.de> (raw)
In-Reply-To: <20060905121957.CF13F353A15@atlas.denx.de>

Hello, Wolfgang!

-> moving from u-boot-users to linuxppc-embedded

Wolfgang Denk wrote:
> In message <44FD5BD4.9090406@anagramm.de> you wrote:
> 
>>Now I try to boot a current linux kernel - the vanilla 2.6.17.11
>>with the default tqm8540 config but it doesn't show any sign of life
> 
> Please use the kernel from our repo instead; see
> http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git

Okay, the compilation after a make TQM8540_defconfig fails:

clemens@ecam:~/git/linux-2.6-denx$ make uImage
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-ppc
  CHK     include/linux/compile.h
  CC      arch/ppc/syslib/mpc85xx_devices.o
In file included from arch/ppc/syslib/mpc85xx_devices.c:23:
include/asm/cpm2.h:1193:1: warning: "FCC2_MEM_OFFSET" redefined
include/asm/cpm2.h:1192:1: warning: this is the location of the previous definition
arch/ppc/syslib/mpc85xx_devices.c:99: error: `F1_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:99: error: `F1_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:99: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:99: error: (near initialization for `mpc85xx_fcc1_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:100: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:100: error: (near initialization for `mpc85xx_fcc1_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:117: error: `F2_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:117: error: `F2_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:117: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:117: error: (near initialization for `mpc85xx_fcc2_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:118: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:118: error: (near initialization for `mpc85xx_fcc2_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:135: error: `F3_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:135: error: `F3_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:135: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:135: error: (near initialization for `mpc85xx_fcc3_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:136: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:136: error: (near initialization for `mpc85xx_fcc3_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:138: error: `FCC3_MEM_OFFSET' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:138: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:138: error: (near initialization for `mpc85xx_fcc3_pdata.mem_offset')
make[1]: *** [arch/ppc/syslib/mpc85xx_devices.o] Error 1
make: *** [arch/ppc/syslib] Error 2

>>Are there any tips&tricks to consider regarding that point?
> 
> Yes, use a working kernel. Not all our patches have been accepted
> upstream, and we have some lag with re-submissions.

According to TQC, the latest "working" kernel was a 2.6.15-git from your
(denx) tree. I get the details from Mr. Becher@TQC and see how far I can get.

Okay, let's move over to linux-ppc-embedded. (xposting)

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

WARNING: multiple messages have this Message-ID (diff)
From: Clemens Koller <clemens.koller@anagramm.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] OT: Re: Status of OF in TQM8540 and linux-2.6.17.11
Date: Tue, 05 Sep 2006 15:28:54 +0200	[thread overview]
Message-ID: <44FD7B96.80405@anagramm.de> (raw)
In-Reply-To: <20060905121957.CF13F353A15@atlas.denx.de>

Hello, Wolfgang!

-> moving from u-boot-users to linuxppc-embedded

Wolfgang Denk wrote:
> In message <44FD5BD4.9090406@anagramm.de> you wrote:
> 
>>Now I try to boot a current linux kernel - the vanilla 2.6.17.11
>>with the default tqm8540 config but it doesn't show any sign of life
> 
> Please use the kernel from our repo instead; see
> http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git

Okay, the compilation after a make TQM8540_defconfig fails:

clemens at ecam:~/git/linux-2.6-denx$ make uImage
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-ppc
  CHK     include/linux/compile.h
  CC      arch/ppc/syslib/mpc85xx_devices.o
In file included from arch/ppc/syslib/mpc85xx_devices.c:23:
include/asm/cpm2.h:1193:1: warning: "FCC2_MEM_OFFSET" redefined
include/asm/cpm2.h:1192:1: warning: this is the location of the previous definition
arch/ppc/syslib/mpc85xx_devices.c:99: error: `F1_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:99: error: `F1_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:99: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:99: error: (near initialization for `mpc85xx_fcc1_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:100: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:100: error: (near initialization for `mpc85xx_fcc1_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:117: error: `F2_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:117: error: `F2_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:117: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:117: error: (near initialization for `mpc85xx_fcc2_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:118: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:118: error: (near initialization for `mpc85xx_fcc2_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:135: error: `F3_RXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:135: error: `F3_TXCLK' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:135: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:135: error: (near initialization for `mpc85xx_fcc3_pdata.clk_route')
arch/ppc/syslib/mpc85xx_devices.c:136: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:136: error: (near initialization for `mpc85xx_fcc3_pdata.clk_trx')
arch/ppc/syslib/mpc85xx_devices.c:138: error: `FCC3_MEM_OFFSET' undeclared here (not in a function)
arch/ppc/syslib/mpc85xx_devices.c:138: error: initializer element is not constant
arch/ppc/syslib/mpc85xx_devices.c:138: error: (near initialization for `mpc85xx_fcc3_pdata.mem_offset')
make[1]: *** [arch/ppc/syslib/mpc85xx_devices.o] Error 1
make: *** [arch/ppc/syslib] Error 2

>>Are there any tips&tricks to consider regarding that point?
> 
> Yes, use a working kernel. Not all our patches have been accepted
> upstream, and we have some lag with re-submissions.

According to TQC, the latest "working" kernel was a 2.6.15-git from your
(denx) tree. I get the details from Mr. Becher at TQC and see how far I can get.

Okay, let's move over to linux-ppc-embedded. (xposting)

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

  reply	other threads:[~2006-09-05 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 11:13 [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11 Clemens Koller
2006-09-05 12:19 ` Wolfgang Denk
2006-09-05 13:28   ` Clemens Koller [this message]
2006-09-05 13:28     ` [U-Boot-Users] OT: " Clemens Koller
2006-09-05 15:06     ` OT: Re: [U-Boot-Users] " Vitaly Bordug
2006-09-05 15:06       ` [U-Boot-Users] OT: " Vitaly Bordug
2006-09-05 15:39       ` Wolfgang Denk
2006-09-05 18:06         ` Clemens Koller

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=44FD7B96.80405@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=u-boot-users@lists.sourceforge.net \
    --cc=wd@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.