I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
embeddedplanet-ep405pc & motorola-sandpoint are both PPC so won't build anyway.
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and newisys-khepri all failed to have a config file that buildtarget was happy with.
via-epia, digitallogic-adl855pc, digitallogic-msm586seg, eaglelion-5bcm & emulation-qemu-i386 all have problems with udelay.
amd-serenade has an error I don't quite understand.
island-aruma has a non-standard build dir so it doesn't get picked up. Again this is something I'll fix up in the config file unless I hear complaints.
I've got my EPIA-M code to the point where it's hitting the udelay problem various other ports have. I haven't quite tracked down what other change has made this happen though. EPIA was certainly building a month or so ago from the tree when I tried it.
J.
On Thu, 2005-08-04 at 16:59 +0100, Jonathan McDowell wrote:
I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
Do you mean I left "payload /home/ollie/xxxx" there ?
embeddedplanet-ep405pc & motorola-sandpoint are both PPC so won't build anyway.
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and newisys-khepri all failed to have a config file that buildtarget was happy with.
totalimpac-briq should be PPC. technologic-ts5300 is never finished.
via-epia, digitallogic-adl855pc, digitallogic-msm586seg, eaglelion-5bcm & emulation-qemu-i386 all have problems with udelay.
I have a quick fix to the udelay but I am not sure it is the correct way to do it.
amd-serenade has an error I don't quite understand.
island-aruma has a non-standard build dir so it doesn't get picked up. Again this is something I'll fix up in the config file unless I hear complaints.
I've got my EPIA-M code to the point where it's hitting the udelay problem various other ports have. I haven't quite tracked down what other change has made this happen though. EPIA was certainly building a month or so ago from the tree when I tried it.
J.
All tyan MB are using CAR, So I wonder if something related that.
But seems that Ollie already verified with gcc 3.3 or 3.4 romcc version could work too.
YH
On 8/4/05, Li-Ta Lo ollie@lanl.gov wrote:
On Thu, 2005-08-04 at 16:59 +0100, Jonathan McDowell wrote:
I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
Do you mean I left "payload /home/ollie/xxxx" there ?
embeddedplanet-ep405pc & motorola-sandpoint are both PPC so won't build anyway.
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and newisys-khepri all failed to have a config file that buildtarget was happy with.
totalimpac-briq should be PPC. technologic-ts5300 is never finished.
via-epia, digitallogic-adl855pc, digitallogic-msm586seg, eaglelion-5bcm & emulation-qemu-i386 all have problems with udelay.
I have a quick fix to the udelay but I am not sure it is the correct way to do it.
amd-serenade has an error I don't quite understand.
island-aruma has a non-standard build dir so it doesn't get picked up. Again this is something I'll fix up in the config file unless I hear complaints.
I've got my EPIA-M code to the point where it's hitting the udelay problem various other ports have. I haven't quite tracked down what other change has made this happen though. EPIA was certainly building a month or so ago from the tree when I tried it.
J.
-- Li-Ta Lo ollie@lanl.gov Los Alamos National Lab
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
On Thu, Aug 04, 2005 at 10:17:03AM -0600, Li-Ta Lo wrote:
On Thu, 2005-08-04 at 16:59 +0100, Jonathan McDowell wrote:
I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
Do you mean I left "payload /home/ollie/xxxx" there ?
Yes. The attached patch cleans up the payload bits (put them in targets/<vendor>/payloads like the Tyan boards do) and also fixes island-aruma to put itself in the same format of directory as everything else. With it I get PASSes for amd-quartet, amd-solo, arima-hdama, ibm-e325 & island-aruma, in addition to the Tyan boards. That brings us up to 17 images building fine and 13 failing.
embeddedplanet-ep405pc & motorola-sandpoint are both PPC so won't build anyway.
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and newisys-khepri all failed to have a config file that buildtarget was happy with.
totalimpac-briq should be PPC. technologic-ts5300 is never finished.
buildtarget can't even parse their config files, so my test rig never even tries to compile them.
via-epia, digitallogic-adl855pc, digitallogic-msm586seg, eaglelion-5bcm & emulation-qemu-i386 all have problems with udelay.
I have a quick fix to the udelay but I am not sure it is the correct way to do it.
Can you show me your quick fix even to give me an idea of where the issue is?
J.
On Thu, 2005-08-04 at 17:51 +0100, Jonathan McDowell wrote:
On Thu, Aug 04, 2005 at 10:17:03AM -0600, Li-Ta Lo wrote:
On Thu, 2005-08-04 at 16:59 +0100, Jonathan McDowell wrote:
I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
Do you mean I left "payload /home/ollie/xxxx" there ?
Yes. The attached patch cleans up the payload bits (put them in targets/<vendor>/payloads like the Tyan boards do) and also fixes island-aruma to put itself in the same format of directory as everything else. With it I get PASSes for amd-quartet, amd-solo, arima-hdama, ibm-e325 & island-aruma, in addition to the Tyan boards. That brings us up to 17 images building fine and 13 failing.
Did you get your commit privilege yet? Can you commit your patch?
On Thu, Aug 04, 2005 at 11:05:05AM -0600, Li-Ta Lo wrote:
On Thu, 2005-08-04 at 17:51 +0100, Jonathan McDowell wrote:
On Thu, Aug 04, 2005 at 10:17:03AM -0600, Li-Ta Lo wrote:
Do you mean I left "payload /home/ollie/xxxx" there ?
Yes. The attached patch cleans up the payload bits (put them in targets/<vendor>/payloads like the Tyan boards do) and also fixes island-aruma to put itself in the same format of directory as everything else. With it I get PASSes for amd-quartet, amd-solo, arima-hdama, ibm-e325 & island-aruma, in addition to the Tyan boards. That brings us up to 17 images building fine and 13 failing.
Did you get your commit privilege yet? Can you commit your patch?
I did, yes. I've been posting patches to the list before committing them, but you've been committing them for me so far. :) I'll commit this one now.
J.
-
Jonathan McDowell -
Li-Ta Lo -
yhlu