Hi,
I'm working on porting the Tizen build on Yocto. Right now we're still
in the process of getting everything from Tizen to build and work with
Yocto so we didn't pay much attention to memory usage and I don't think
we will have time to look at that soon... Anyway, memory usage in Tizen
Yocto shouldn't be that different from the memory usage in Tizen Common.
A first and easy way to reduce packages in the Tizen Yocto image is to
remove the ones you don't want in the image recipes:
meta-tizen/recipes-image (remove directly the packages or the features).
That way you will be able to reduce the image size but I doubt it will
have an impact on memory usage.
We recently succeeded to get a bootable x86 image using "MACHINE ?=
genericx86" in conf/local.conf but I doubt it will boot on a machine
with only 64 MB. As Thiago said, this is "quite constraining".
If you find a way to boot a Tizen image with Weston on such a machine I
think we will all be very interested by it.
Best regards,
Kevin
On 22/07/2014 03:10, 황형원 wrote:
Samsung Enterprise Portal mySingle
I haven't yet. The build script for tizen on yocto is based on
the x86-64 configuration.
So some effort is needed to make the build work for x86-32 machine.
Best regards,
Hyungwon Hwang
------- *Original Message* -------
*Sender* : 함명주<[email protected]> S5(책임)/책임/Frontier CS
Lab(S/W센터)/삼성전자
*Date* : 2014-07-22 09:53 (GMT+09:00)
*Title* : Re 4: [Dev] How should I do to make it boot on the low-end
machine with 64MB main memory?
Anyway, have you tried to use x86-32 rather than x86-64? Using x86-64
in 64MB system seems inappropriate.
------- Original Message -------
Sender : 함명주S5(책임)/책임/Frontier CS Lab(S/W센터)/삼성전자
Date : 2014-07-22 09:51 (GMT+09:00)
Title : Re: Re: Re: [Dev] How should I do to make it boot on the
low-end machine with 64MB main memory?
Reason: the ISA itself is different.
Even between x86-32 vs x86-64, usually, people report that the size
(both the binary size and runtime memory footprint) increases around
20%. Besides, we have been using THUMB for ARM (armv7 / aarch32) to
reduce the size and aarch64 does not allow to use THUMB, which in
turn, increases the size gap between aarch32 vs aarch64 further than
x86-32 vs x86-64.
Thus, it's trivial to expect that x86-64 (or even aarch64) will have
much larger size than aarch32/arm7 binaries. The question for you will
be how to reduce the size to fit in 64MB :)
Cheers,
MyungJoo.
------- Original Message -------
Sender : 황형원S3(사원)/사원/System S/W Lab(S/W센터)/삼성전자
Date : 2014-07-22 09:45 (GMT+09:00)
Title : Re: Re: [Dev] How should I do to make it boot on the low-end
machine with 64MB main memory?
Thanks for your reply.
As you expected, the image size of x86-64 is much larger then that of
arm. Also, the RSS and PSS of the
processes on x86-64 is larger than that of arm, even though the gap
betweenthe same processes differs
depending on the process. I also suspected like you, when I saw that
the boot with the x86-64 image failed.
But I couldn't find the reason from where this difference comes. From
where, could you expect like you said?
Best regards,
Hyungwon Hwang
------- Original Message -------
Sender : 함명주S5(책임)/책임/Frontier CS Lab(S/W센터)/삼성전자
Date : 2014-07-22 08:59 (GMT+09:00)
Title : Re: [Dev] How should I do to make it boot on the low-end
machine with 64MB main memory?
Have you compared the image size (and runtime memory footprint as
well) of ARM binaries and x86-64 binaries? I expect that the latter is
much larger.
------- Original Message -------
Sender : 황형원 S3(사원)/사원/System S/W Lab(S/W센터)/삼성전자
Date : 2014-07-22 08:56 (GMT+09:00)
Title : [Dev] How should I do to make it boot on the low-end machine
with 64MB main memory?
Hi,
I'm trying to run Tizen Linux in the machine with Intel ivy bridge,
and 64MB main memory. I followed the instructions in
https://wiki.tizen.org/wiki/Tizen_on_yocto. But it failed to boot
becuase out of memory. The image which is made after the instructions
includes weston for GUI, and systemd for init. It seems that they use
too many memory to run on the machine with 64MB. I saw that the image
core-image-sato, which includes X and matchbox for GUI and sysvinit
for init, is able to run on QEMU-ARM with 64MB, even though it failed
to do on QEMU-x86_64. But especially I am interested to boot the image
with weston. I wonder what I am missing. Is there someone who
succeeded to boot the Tizen Linux or a Linux with weston in this kind
of environments, or can give me some advice?
Thanks.
Best regards,
Hyungwon Hwang
--
MyungJoo Ham (함명주), PHD
Frontier CS Lab, Software Center
Samsung Electronics
Cell: +82-10-6714-2858
--
MyungJoo Ham (함명주), PHD
Frontier CS Lab, Software Center
Samsung Electronics
Cell: +82-10-6714-2858
--
MyungJoo Ham (함명주), PHD
Frontier CS Lab, Software Center
Samsung Electronics
Cell: +82-10-6714-2858
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
