[LinuxBIOS] r3021 build service

[LinuxBIOS information]

Dear LinuxBIOS readers!

This is the automated build check service of LinuxBIOS.

The developer "cozzie" checked in revision 3021 to
the LinuxBIOS source repository and caused the following 
changes:

Change Log:
More abuild fixes, this should be the last (trivial)

Signed-off-by: Corey Osgood 
Acked-by: Corey Osgood

Build Log:
Compilation of amd:serengeti_cheetah_fam10 is still broken
See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_...

If something broke during this checkin please be a pain 
in cozzie's neck until the issue is fixed.

If this issue is not fixed within 24h the revision should 
be backed out.

Best regards,
     LinuxBIOS automatic build system

[Corey Osgood]

On Dec 19, 2007 4:26 PM, LinuxBIOS information  wrote:
> Dear LinuxBIOS readers!
>
> This is the automated build check service of LinuxBIOS.
>
> The developer "cozzie" checked in revision 3021 to
> the LinuxBIOS source repository and caused the following
> changes:
>
> Change Log:
> More abuild fixes, this should be the last (trivial)
>
> Signed-off-by: Corey Osgood 
> Acked-by: Corey Osgood
>
> Build Log:
> Compilation of amd:serengeti_cheetah_fam10 is still broken
> See the error log at
> http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_...

Oh for cripe's sake, ld now? Will fix when I make it home tonight.

-Corey

[Corey Osgood]

Corey Osgood wrote:
> On Dec 19, 2007 4:26 PM, LinuxBIOS information <[e-mail]
> > wrote:
> Dear LinuxBIOS readers!
>
> This is the automated build check service of LinuxBIOS.
>
> The developer "cozzie" checked in revision 3021 to
> the LinuxBIOS source repository and caused the following
> changes:
>
> Change Log:
> More abuild fixes, this should be the last (trivial)
>
> Signed-off-by: Corey Osgood < [e-mail]
> <mailto:[e-mail]>>
> Acked-by: Corey Osgood <[e-mail]
> <mailto:[e-mail]>>
>
>
>
> Build Log:
> Compilation of amd:serengeti_cheetah_fam10 is still broken
> See the error log at
> http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd
> <http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd>
>
>
> Oh for cripe's sake, ld now? Will fix when I make it home tonight.
>
> -Corey

Scratch that, someone else can wrap it up. I don't know if it just needs
a ROM_SIZE increase or something deeper is wrong, I've been completely
unable to reproduce the error. Someone with access to the build server
or a similar setup is probably the best candidate to fix this (I've done
my share ;-) )

-Corey

[Marc Jones]

Corey Osgood wrote:
> Corey Osgood wrote:
> > On Dec 19, 2007 4:26 PM, LinuxBIOS information <[e-mail]
> > > wrote:
> > Dear LinuxBIOS readers!
> >
> > This is the automated build check service of LinuxBIOS.
> >
> > The developer "cozzie" checked in revision 3021 to
> > the LinuxBIOS source repository and caused the following
> > changes:
> >
> > Change Log:
> > More abuild fixes, this should be the last (trivial)
> >
> > Signed-off-by: Corey Osgood < [e-mail]
> > <mailto:[e-mail]>>
> > Acked-by: Corey Osgood <[e-mail]
> > <mailto:[e-mail]>>
> >
> >
> >
> > Build Log:
> > Compilation of amd:serengeti_cheetah_fam10 is still broken
> > See the error log at
> > http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd
> > <http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd>
> >
> >
> > Oh for cripe's sake, ld now? Will fix when I make it home tonight.
> >
> > -Corey
>
> Scratch that, someone else can wrap it up. I don't know if it just needs
> a ROM_SIZE increase or something deeper is wrong, I've been completely
> unable to reproduce the error. Someone with access to the build server
> or a similar setup is probably the best candidate to fix this (I've done
> my share ;-) )
>
> -Corey

Corey,

I looked at the output and I don't see anything obvious. It doesn't fail 
for me either. I'll work with Stefan when he is able to look at it.

Marc

[Myles Watson]

Here's my attempt at fixing abuild for serengeti_cheetah_fam10.

It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in
Config.lb and putting it in Config-abuild.lb.  When I reduce this size
(past what it is in Config-abuild.lb), it gives me the same overlap
error in my system that abuild is seeing.

I also added XIP_ROM_SIZE, although I admit freely that I don't know
anything about this variable.  I just wanted to make it match Marc's
Config.lb.

Maybe the right thing to do would be to remove both XIP_ROM_SIZE
references in Config-abuild.lb

Either way,  I think the ROM_IMAGE_SIZE change will help.

Myles

Signed-off-by: Myles Watson

On Dec 20, 2007 12:19 PM, Marc Jones  wrote:
> Corey Osgood wrote:
> > Corey Osgood wrote:
> > > On Dec 19, 2007 4:26 PM, LinuxBIOS information <[e-mail]
> > > > wrote:
> > > Dear LinuxBIOS readers!
> > >
> > > This is the automated build check service of LinuxBIOS.
> > >
> > > The developer "cozzie" checked in revision 3021 to
> > > the LinuxBIOS source repository and caused the following
> > > changes:
> > >
> > > Change Log:
> > > More abuild fixes, this should be the last (trivial)
> > >
> > > Signed-off-by: Corey Osgood < [e-mail]
> > > <mailto:[e-mail]>>
> > > Acked-by: Corey Osgood <[e-mail]
> > > <mailto:[e-mail]>>
> > >
> > >
> > >
> > > Build Log:
> > > Compilation of amd:serengeti_cheetah_fam10 is still broken
> > > See the error log at
> > > http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd
> > > <http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd>
> > >
> > >
> > > Oh for cripe's sake, ld now? Will fix when I make it home tonight.
> > >
> > > -Corey
> >
> > Scratch that, someone else can wrap it up. I don't know if it just needs
> > a ROM_SIZE increase or something deeper is wrong, I've been completely
> > unable to reproduce the error. Someone with access to the build server
> > or a similar setup is probably the best candidate to fix this (I've done
> > my share ;-) )
> >
> > -Corey
>
> Corey,
>
> I looked at the output and I don't see anything obvious. It doesn't fail
> for me either. I'll work with Stefan when he is able to look at it.
>
> Marc

[Marc Jones]

Myles Watson wrote:
> Here's my attempt at fixing abuild for serengeti_cheetah_fam10.
>
> It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in
> Config.lb and putting it in Config-abuild.lb.  When I reduce this size
> (past what it is in Config-abuild.lb), it gives me the same overlap
> error in my system that abuild is seeing.
>
> I also added XIP_ROM_SIZE, although I admit freely that I don't know
> anything about this variable.  I just wanted to make it match Marc's
> Config.lb.
>
> Maybe the right thing to do would be to remove both XIP_ROM_SIZE
> references in Config-abuild.lb
>
> Either way,  I think the ROM_IMAGE_SIZE change will help.

Myles,

Thanks, the bigger problem is that the rom generated by the auto abuild 
is larger than expected. We are investigating the tool chain. Once we 
understand what is going on I will feel more comfortable with increasing 
the ROM_IMAGE_SIZE.

Marc

[Marc Jones]

Marc Jones wrote:
> Myles Watson wrote:
> > Here's my attempt at fixing abuild for serengeti_cheetah_fam10.
> >
> > It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in
> > Config.lb and putting it in Config-abuild.lb.  When I reduce this size
> > (past what it is in Config-abuild.lb), it gives me the same overlap
> > error in my system that abuild is seeing.
> >
> > I also added XIP_ROM_SIZE, although I admit freely that I don't know
> > anything about this variable.  I just wanted to make it match Marc's
> > Config.lb.
> >
> > Maybe the right thing to do would be to remove both XIP_ROM_SIZE
> > references in Config-abuild.lb
> >
> > Either way,  I think the ROM_IMAGE_SIZE change will help.
>
> Myles,
>
> Thanks, the bigger problem is that the rom generated by the auto abuild 
> is larger than expected. We are investigating the tool chain. Once we 
> understand what is going on I will feel more comfortable with increasing 
> the ROM_IMAGE_SIZE.
>
> Marc

I made a very sexy picture of what a failover coreboot v2 image looks 
like and what ROM_IMAGE_SIZE and other variables are.

http://www.coreboot.org/Anatomy_of_a_Failover_LinuxBIOSv2_Image

Marc

[Carl-Daniel Hailfinger]

On 11.01.2008 23:07, Marc Jones wrote:
> I made a very sexy picture of what a failover coreboot v2 image looks 
> like and what ROM_IMAGE_SIZE and other variables are.
>
> http://www.coreboot.org/Anatomy_of_a_Failover_LinuxBIOSv2_Image

Great, thanks! One of the things I'd always wanted to have an image of.

Regards,
Carl-Daniel

[ron minnich]

On Jan 11, 2008 2:07 PM, Marc Jones  wrote:
> I made a very sexy picture of what a failover coreboot v2 image looks
> like and what ROM_IMAGE_SIZE and other variables are.
>
> http://www.coreboot.org/Anatomy_of_a_Failover_LinuxBIOSv2_Image

I think we should make you Chairman of the Graphics Department :-)

This is great!

ron

[Corey Osgood]

Myles Watson wrote:
> Here's my attempt at fixing abuild for serengeti_cheetah_fam10.
>
> It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in
> Config.lb and putting it in Config-abuild.lb.  When I reduce this size
> (past what it is in Config-abuild.lb), it gives me the same overlap
> error in my system that abuild is seeing.
>
> I also added XIP_ROM_SIZE, although I admit freely that I don't know
> anything about this variable.  I just wanted to make it match Marc's
> Config.lb.

This should be set in the src/*/Config.lb, not here. Can you try it
without the change?
> Maybe the right thing to do would be to remove both XIP_ROM_SIZE
> references in Config-abuild.lb
>
> Either way,  I think the ROM_IMAGE_SIZE change will help.
>
> Myles
>
> Signed-off-by: Myles Watson

Please check the above, but either way

Acked-by: Corey Osgood