There is the beginnins of a port but there is no sc520 code. What is the status of this?
With nothing checked into the tree I cannot fix it along with everything else.
Eric
* Eric W. Biederman ebiederman@lnxi.com [041104 04:57]:
There is the beginnins of a port but there is no sc520 code. What is the status of this?
With nothing checked into the tree I cannot fix it along with everything else.
I started the port but was unable to finish it up to now.. :-(
Stefan
Stefan Reinauer stepan@openbios.org writes:
- Eric W. Biederman ebiederman@lnxi.com [041104 04:57]:
There is the beginnins of a port but there is no sc520 code. What is the status of this?
With nothing checked into the tree I cannot fix it along with everything else.
I started the port but was unable to finish it up to now.. :-(
Ok that explains it. Do you have enough northbridge/southbridge code that it even builds for you?
Eric
On Thu, 4 Nov 2004, Eric W. Biederman wrote:
Ok that explains it. Do you have enough northbridge/southbridge code that it even builds for you?
stefan and I had talked on this one and were probably not going to do a seperate north/south as they are all so tightly integrated on this chip. It was a bit of an experiment.
That's my memory anyway.
ron
"Ronald G. Minnich" rminnich@lanl.gov writes:
On Thu, 4 Nov 2004, Eric W. Biederman wrote:
Ok that explains it. Do you have enough northbridge/southbridge code that it even builds for you?
stefan and I had talked on this one and were probably not going to do a seperate north/south as they are all so tightly integrated on this chip. It was a bit of an experiment.
That's my memory anyway.
Sounds sane.
In any case we need to start running abuild regularly. We need to have a way of dealing with ports that we are totally broken in the tree.
Eric
* Eric W. Biederman ebiederman@lnxi.com [041104 20:21]:
In any case we need to start running abuild regularly. We need to have a way of dealing with ports that we are totally broken in the tree.
I implemented simple cross compiling support in LinuxBIOS abuild. So far it supports compiling x86 images on AMD64 and possibly PPC images on PPC64 (untested).
If I'd find a set of cross-ppc-gcc rpms for SUSE 9.0-AMD64 I could set up cross building ppc binaries on openbios.org and have the results put to a web page or mailed regularly to the LinuxBIOS mailinglist.
It seems no mainboard says "use LD" at all yet. Some still don't "use CC" but this is minor..
What's the usual naming convention for the cross compiler and cross linker of a given platform? We also need to cope with multiple payloads if we want to be able to use the resulting binaries... (in an ideal world the next step would be to automatically flash them)
Your check for a previous successful compile is really useful when flying over the tree and fixing a larger number of boards. To detect any regressions easily I added the option -a so all motherboard builds can be forced.
also with -t vendor/board it is possible to only build a given board
./abuild.sh -at arima/hdama will always rebuild the single target arima hdama
Stefan
Stefan Reinauer stepan@openbios.org writes:
- Eric W. Biederman ebiederman@lnxi.com [041104 20:21]:
In any case we need to start running abuild regularly. We need to have a way of dealing with ports that we are totally broken in the tree.
I implemented simple cross compiling support in LinuxBIOS abuild. So far it supports compiling x86 images on AMD64 and possibly PPC images on PPC64 (untested).
If I'd find a set of cross-ppc-gcc rpms for SUSE 9.0-AMD64 I could set up cross building ppc binaries on openbios.org and have the results put to a web page or mailed regularly to the LinuxBIOS mailinglist.
It seems no mainboard says "use LD" at all yet. Some still don't "use CC" but this is minor..
Actually what you should be looking for is "uses CROSS_COMPILE" Currently we don't seem to call LD directly so as long as gcc can find the proper one we are ok.
What's the usual naming convention for the cross compiler and cross linker of a given platform? We also need to cope with multiple payloads if we want to be able to use the resulting binaries... (in an ideal world the next step would be to automatically flash them)
I suspect that we will want to have a simple Config.lb in targets that we can start with and add cross compiling and other options to.
Your check for a previous successful compile is really useful when flying over the tree and fixing a larger number of boards. To detect any regressions easily I added the option -a so all motherboard builds can be forced.
also with -t vendor/board it is possible to only build a given board
./abuild.sh -at arima/hdama will always rebuild the single target arima hdama
-a and -t sound like useful additions.
Just don't forget that ultimately if we can fix the dependencies in the tree we both -a and my caching of what actually built successfully should be trivial.
Note: I had to tweak the parser so it would work when I specified where the linuxbios tree was. It was putting single quotes around the pathname nad ls was not really fond of './freebios2/'/src/mainboard ....
Eric
On Thu, 4 Nov 2004, Stefan Reinauer wrote:
I started the port but was unable to finish it up to now.. :-(
guess stefan and I were both trying.
ron
On Wed, 3 Nov 2004, Eric W. Biederman wrote:
There is the beginnins of a port but there is no sc520 code. What is the status of this?
It got stuck, don't worry about this. The flash was soldered-on and I've decided to do the port with a digital logic card instead (this one does have removable flash).
ron
-
ebiederman＠lnxi.com -
Ronald G. Minnich -
Stefan Reinauer