Bug 3514 - Doesn't checks if the kernel fits in the memory
Summary: Doesn't checks if the kernel fits in the memory
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.3
Hardware: Routerstationpro mips
: Medium normal
Target Milestone: 1.4
Assignee: Michel Thebeau
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-11-29 20:29 UTC by Lisandro Damián Nicanor Pérez Meyer
Modified: 2013-04-22 20:04 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lisandro Damián Nicanor Pérez Meyer 2012-11-29 20:29:27 UTC 
The current latest kernel for the routerstationpro machine is far beyond the 16MB of it's flash size [0].

I think it would be good to test if the size of the image is below that size.

[0] <http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/machines/routerstationpro/>
Comment 1 Alexandru Georgescu 2012-12-03 11:38:30 UTC 
Do you mean "test if the size of the image is above that size" ? 

In this case, you could suggest a test case in the upcoming Testopia feature of bugzilla. You can find further info on this in the upcoming Testopia wiki page.
Comment 2 Darren Hart 2013-03-07 16:19:39 UTC 
b32a0c38 sys940x: Add linux-yocto_3.4 bbappend
Comment 3 Darren Hart 2013-03-07 16:21:29 UTC 
Sorry updated wrong bug.
Comment 4 Darren Hart 2013-03-07 16:21:36 UTC 
.
Comment 5 Richard Purdie 2013-03-07 16:21:45 UTC 
There is the KERNEL_IMAGE_MAXSIZE variable, can we set this for the routerstationpro?
Comment 6 Darren Hart 2013-03-07 16:23:30 UTC 
Bruce, can you have a look at adding something appropriate with the KERNEL_IMAGE_MAXSIZE for the RSP?
Comment 7 Michel Thebeau 2013-03-26 16:01:38 UTC 
The do_sizecheck task using KERNEL_IMAGE_MAXSIZE is a little bit broken (the object file ${KERNEL_OUTPUT} is not found), and becomes a little more broken after applying my fix for bug #3515.

I'll need to think more about that.  (FYI)