1:39 a.m.
Thanks for your work on this project.
I am collecting celadon for my tablet on cpu intel core m3 6Y30. I compiled version 12 of
caas-userdebug with some of my patches for peripherals (wifi, touchscreen, etc.) as a disk
image for direct booting from an external usb (to m.2 sata) ssd. Of the problems I
noticed, I can note stuttering when playing video. I also had to turn off the wifi display
in the overlay, and the not working gallery in aosp was not even surprised - the patch for
11 android is well known - I hope it will work at 12.
I noticed that the development of celadon has shifted towards running on a virtual machine
in Linux, which is just as interesting, but in a more convenient form than now, when it is
necessary to carry out a lot of actions to configure the OS and components.
Unfortunately, another version 11 stopped loading into VMware under windows - it was
convenient for quick debugging and checking celadon assemblies with minimal overhead.
I also understand that the formation of a common image with a large set of partitions
meets the requirements of Google, but this form requires a dedicated disk to run, which is
not always convenient for users to boot. For celadon 9, I still managed to boot from the
system.img, vendor.img, ramdisk.img, kernel and data.img files from the windows partition
with ntfs via refind. As the experience of the android x86 project shows, this option is
still possible for newer versions of android. If you implemented this loading method, it
would be convenient for many users.
2:17 a.m.
I would also like to add a request to include in android 12 translation of the arm32 /
arm64 houdini code in the form of executable files. For android 9 and 11, these files are
already available in google chromeos distributions. The likelihood that Google will
include android 12 in chromeos is very small, and without houdini, celadon assemblies are
not of great interest for running games and applications. Of course, you can always take
google ndk translation files from the android sdk emulator, but its work is noticeably
worse than houdini.
10:20 p.m.
Thank for your mail and feedback.
Celadon is targeting a CDD compliance Android reference. So some feature require advanced
feature like TEE, which could conflict to VMWare/Hyper-V etc.
To make the Celadon build work on VMWare or Hyper-V, some tweak is required like disable
Trusty.
For super partition support, we follow the upstream implementation which is introduce in
Android 10. Disable super partition will impact other features like OTA. We don't have
plan to support it.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Does a dedicate data.img help on your case?
Regards,
Luhai
-----Original Message-----
From: fguy2002(a)yandex.ru <fguy2002(a)yandex.ru>
Sent: Monday, October 11, 2021 4:40 PM
To: celadon(a)lists.01.org
Subject: [01.org Celadon] Android 12 caas
Thanks for your work on this project.
I am collecting celadon for my tablet on cpu intel core m3 6Y30. I compiled version 12 of
caas-userdebug with some of my patches for peripherals (wifi, touchscreen, etc.) as a disk
image for direct booting from an external usb (to m.2 sata) ssd. Of the problems I
noticed, I can note stuttering when playing video. I also had to turn off the wifi display
in the overlay, and the not working gallery in aosp was not even surprised - the patch for
11 android is well known - I hope it will work at 12.
I noticed that the development of celadon has shifted towards running on a virtual machine
in Linux, which is just as interesting, but in a more convenient form than now, when it is
necessary to carry out a lot of actions to configure the OS and components.
Unfortunately, another version 11 stopped loading into VMware under windows - it was
convenient for quick debugging and checking celadon assemblies with minimal overhead.
I also understand that the formation of a common image with a large set of partitions
meets the requirements of Google, but this form requires a dedicated disk to run, which is
not always convenient for users to boot. For celadon 9, I still managed to boot from the
system.img, vendor.img, ramdisk.img, kernel and data.img files from the windows partition
with ntfs via refind. As the experience of the android x86 project shows, this option is
still possible for newer versions of android. If you implemented this loading method, it
would be convenient for many users.
--
Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an email to
celadon-leave(a)lists.01.org
1:26 a.m.
I add superuser support from android x86 to celadon and disable trusty accordingly, switch
to permissive and a little system-core patch for it to work. Problems with VMware in
celadon 11 are related to the video driver judging by the logs and the lack of switching
to graphics mode with "Android" displaying.
I know about switching to the super section and improving security, but as the same
android x86 project shows, it is possible to build androids 10 and 11 without it within
the same system-root section. The absence of OTA in this case is not important, but it
becomes possible to quickly make some changes in the system partition without rebuilding -
which is very convenient for various experiments and debugging the project. For the
celadon project, this can be implemented as another mixin option, but unfortunately my
experience is not enough for this.
The data.img file, if the android is loaded from system.img, acts as a userdata section -
the user can select the size he needs, as well as change it in windows or linux.
Could you also comment on the situation with houdini for android 12. Of course, we can
continue "hacking" chromeos, but nothing seems to prevent the intel from adding
them as executable files to the celadon project.
3:23 a.m.
Hi,
On Houdini, it is a separate s/w product and there is a license to be signed
with Intel before it can be used in commercial products.
Please contact local Intel team to understand more about it.
Let me see if I can connect.
Regards,
Yogesh.
> -----Original Message-----
> From: fguy2002(a)yandex.ru <fguy2002(a)yandex.ru>
> Sent: Tuesday, October 12, 2021 1:57 PM
> To: celadon(a)lists.01.org
> Subject: [01.org Celadon] Re: Android 12 caas
>
> I add superuser support from android x86 to celadon and disable trusty
> accordingly, switch to permissive and a little system-core patch for it to work.
> Problems with VMware in celadon 11 are related to the video driver judging
> by the logs and the lack of switching to graphics mode with "Android"
> displaying.
> I know about switching to the super section and improving security, but as
> the same android x86 project shows, it is possible to build androids 10 and 11
> without it within the same system-root section. The absence of OTA in this
> case is not important, but it becomes possible to quickly make some changes
> in the system partition without rebuilding - which is very convenient for
> various experiments and debugging the project. For the celadon project, this
> can be implemented as another mixin option, but unfortunately my
> experience is not enough for this.
> The data.img file, if the android is loaded from system.img, acts as a userdata
> section - the user can select the size he needs, as well as change it in
> windows or linux.
> Could you also comment on the situation with houdini for android 12. Of
> course, we can continue "hacking" chromeos, but nothing seems to prevent
> the intel from adding them as executable files to the celadon project.
> --
> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an email to
> celadon-leave(a)lists.01.org
4:51 a.m.
Hi Yogesh.
You misunderstood me - I do not create some kind of commercial product based on celadon. I
suggest intel enable houdini in celadon 12 to expand its capabilities. Support for houdini
integration is already partially implemented in the mixin. This would greatly increase the
popularity of the celadon project, of course, provided that Intel wants to make this
project interesting for end users. If Intel offers houdini only as a commercial product,
then my proposal loses its meaning.
For androids 9 and 11, houdini files are available from chromeos - those who need it can
add them to android without any problems. I just propose to solve this issue legally with
the observance of licensing rights, etc.
6:23 a.m.
Thanks for the suggestion.
This is just initial release of Celadon 12 (it is first Android 12 on x86!) and there
would be version dependencies to be considered here as well. We'll keep the list
posted if there are any changes in future.
Regards,
Yogesh.
> -----Original Message-----
> From: fguy2002(a)yandex.ru <fguy2002(a)yandex.ru>
> Sent: Tuesday, October 12, 2021 5:21 PM
> To: celadon(a)lists.01.org
> Subject: [01.org Celadon] Re: Android 12 caas
>
> Hi Yogesh.
> You misunderstood me - I do not create some kind of commercial product
> based on celadon. I suggest intel enable houdini in celadon 12 to expand its
> capabilities. Support for houdini integration is already partially implemented
> in the mixin. This would greatly increase the popularity of the celadon
> project, of course, provided that Intel wants to make this project interesting
> for end users. If Intel offers houdini only as a commercial product, then my
> proposal loses its meaning.
> For androids 9 and 11, houdini files are available from chromeos - those who
> need it can add them to android without any problems. I just propose to
> solve this issue legally with the observance of licensing rights, etc.
> --
> Celadon mailing list -- mailto:celadon@lists.01.org To unsubscribe send an email to
> mailto:celadon-leave@lists.01.org
9:20 p.m.
Hi Yogesh,
We have contacted the local Intel team to get Houdini translator license, but the local
support team mentions that Houdini is not continued support by Intel.
Does this information correct?
8:03 p.m.
No that's not right, in fact the license application process is more streamlined now.
I will check with the local team.
Regards,
Yogesh.
> -----Original Message-----
> From: rickchu(a)flytech.com.tw <rickchu(a)flytech.com.tw>
> Sent: Friday, December 17, 2021 9:51 AM
> To: celadon(a)lists.01.org
> Subject: [01.org Celadon] Re: Android 12 caas
>
> Hi Yogesh,
>
> We have contacted the local Intel team to get Houdini translator license, but the
> local support team mentions that Houdini is not continued support by Intel.
> Does this information correct?
> --
> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an email to
> celadon-leave(a)lists.01.org
159
days inactive
229
days old
8 comments
4 participants
participants (4)
-
Chen, Luhai -
fguy2002＠yandex.ru -
Marathe, Yogesh -
rickchu＠flytech.com.tw