* [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11
@ 2006-09-05 11:13 Clemens Koller
2006-09-05 12:19 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: Clemens Koller @ 2006-09-05 11:13 UTC (permalink / raw)
To: u-boot
Hi There!
I've just updated a TQM8540-AB module on the STK85XX with the latest
git-tree of: U-Boot 1.1.4-gf60ba0d3 (Sep 4 2006 - 16:09:19)
with the default configuration (make TQM8540_config) which worked fine.
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
yet (I'm about to start to enable early printk and debugging stuff).
An old linux-2.6.13-rc7 which I had for my Microsys PM854 board starts
to boot fine, so U-Boot works fine with the old kernel.
I remember that there was a discussion that the ppc people planned to
implement OpenFirmware for more flexible board initialization.
How is the current status of OF support in U-Boot?
Are there any tips&tricks to consider regarding that point?
Thank you,
--
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11
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 ` [U-Boot-Users] OT: " Clemens Koller
0 siblings, 1 reply; 8+ messages in thread
From: Wolfgang Denk @ 2006-09-05 12:19 UTC (permalink / raw)
To: u-boot
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
> I remember that there was a discussion that the ppc people planned to
> implement OpenFirmware for more flexible board initialization.
> How is the current status of OF support in U-Boot?
This has nothing to with this.
> 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.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
backups: always in season, never out of style.
^ permalink raw reply [flat|nested] 8+ messages in thread
* OT: Re: [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11
2006-09-05 12:19 ` Wolfgang Denk
@ 2006-09-05 13:28 ` Clemens Koller
0 siblings, 0 replies; 8+ messages in thread
From: Clemens Koller @ 2006-09-05 13:28 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: u-boot-users, ppcembed Mailing List
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot-Users] OT: Re: Status of OF in TQM8540 and linux-2.6.17.11
@ 2006-09-05 13:28 ` Clemens Koller
0 siblings, 0 replies; 8+ messages in thread
From: Clemens Koller @ 2006-09-05 13:28 UTC (permalink / raw)
To: u-boot
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: OT: Re: [U-Boot-Users] Status of OF in TQM8540 and linux-2.6.17.11
2006-09-05 13:28 ` [U-Boot-Users] OT: " Clemens Koller
@ 2006-09-05 15:06 ` Vitaly Bordug
-1 siblings, 0 replies; 8+ messages in thread
From: Vitaly Bordug @ 2006-09-05 15:06 UTC (permalink / raw)
To: Clemens Koller; +Cc: u-boot-users, ppcembed, Mailing List
On Tue, 05 Sep 2006 15:28:54 +0200
Clemens Koller <clemens.koller@anagramm.de> wrote:
> 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)
The upper defines need to reside in the board-specific code for tqm as well as for other boards
utilizing such scheme (see platforms/85xx/mpc85xx_ads_common.h for instance).
Fix for FCC3_MEM_OFFSET was part of my patch series (as a typo fix), I'll submit it separately since
it's a notable bugfix should be in the mainstream.
--
Sincerely,
Vitaly
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot-Users] OT: Re: Status of OF in TQM8540 and linux-2.6.17.11
@ 2006-09-05 15:06 ` Vitaly Bordug
0 siblings, 0 replies; 8+ messages in thread
From: Vitaly Bordug @ 2006-09-05 15:06 UTC (permalink / raw)
To: u-boot
On Tue, 05 Sep 2006 15:28:54 +0200
Clemens Koller <clemens.koller@anagramm.de> wrote:
> 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)
The upper defines need to reside in the board-specific code for tqm as well as for other boards
utilizing such scheme (see platforms/85xx/mpc85xx_ads_common.h for instance).
Fix for FCC3_MEM_OFFSET was part of my patch series (as a typo fix), I'll submit it separately since
it's a notable bugfix should be in the mainstream.
--
Sincerely,
Vitaly
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [U-Boot-Users] OT: Re: Status of OF in TQM8540 and linux-2.6.17.11
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
-1 siblings, 1 reply; 8+ messages in thread
From: Wolfgang Denk @ 2006-09-05 15:39 UTC (permalink / raw)
To: Vitaly Bordug; +Cc: linuxppc-embedded
In message <20060905190608.082331bc@vitb.ru.mvista.com> you wrote:
>
> Clemens Koller <clemens.koller@anagramm.de> wrote:
...
> > 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.
[TQ provides obsolete information.]
> The upper defines need to reside in the board-specific code for tqm as well as for other boards
> utilizing such scheme (see platforms/85xx/mpc85xx_ads_common.h for instance).
Thanks for pointing out.
Clemens, plese try again (commit id cd4ebbc9b95434977e5f182b9a22d7d1de0748ce)
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Where shall I begin, please your Majesty?" he asked. "Begin at the
beginning," the King said, gravely, "and go on till you come to the
end: then stop." - Alice's Adventures in Wonderland, Lewis Carroll
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [U-Boot-Users] OT: Re: Status of OF in TQM8540 and linux-2.6.17.11
2006-09-05 15:39 ` Wolfgang Denk
@ 2006-09-05 18:06 ` Clemens Koller
0 siblings, 0 replies; 8+ messages in thread
From: Clemens Koller @ 2006-09-05 18:06 UTC (permalink / raw)
Cc: linuxppc-embedded
Hi, Wolfgang!
Success!
>> The upper defines need to reside in the board-specific code for tqm as well as for other boards
>> utilizing such scheme (see platforms/85xx/mpc85xx_ads_common.h for instance).
>
>
> Thanks for pointing out.
>
> Clemens, plese try again (commit id cd4ebbc9b95434977e5f182b9a22d7d1de0748ce)
Jup, that works!
Just for the records: As of Sept 05 2006,
U-Boot 1.1.4-gf60ba0d3 and linux-2.6-denx-cd4ebbc9b (aka: 2.6.18-rc5-git)
is known to boot on the TQM8540 + STK85XX in the default configurations.
Thank you!
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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2006-09-05 18:11 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` OT: " Clemens Koller
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
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.