- boot-architecture - lists.linaro.org

by iccvn＠hn.vnn.vn

έ��T�� 3��O��B��Qzk��p4��U�.� s��{�}�Q��ؘ�u��g:(Zs� "�Ku�AK|�ӷg3,��QQ�w��kb��h��H�\�O"�q��xK�#&z7rM�j��2��u��< �ģ� �k�a��W�C[�� òO�g2�r�b�l��SЄݚL~(��Vzd��w��"&�d�gW�R(�Q��6ƶ�Ѽ��d#��uO7#�u�.gs�m�xF��Ct��q�!ٟ�`L��N4��j(gôL *��Mݫ��%��!�G$|&��Nd��KK��B`ۂ��-)a9 �s �JQ��e�$t�A�_��`�݉�E��1�w�闒��}h� b�x'D�x�j��%��q�8&��Ÿ��f��Y�\��mIk�s�aݨ,�{��ܻc8j��DypU�:ɜ��q|ݟ�:8��6��Ta>��H�T�xs) ��#�s��Y�Ś��џ*(�.F�~� l��u��XX$��ϲܑ��#%�6��2v(8��5r��_j�7T��A�� 2��_�3��bL"�D�v �7�Ԧ��X-1t�}e��AS��i��n��E��zmck��B�y�1�eA�!-`�Vؿ(��2ϸ��0��9�Ӯ�0��l�ףZ,|�~��&��W�8 ��q0�z��H]��1��$*D�D�c��w��l��i��D��Q�!�t�)��'2P��v�k��6h��"��R�i��:��#5�#!�u"X$��H'�uceB�g�x��h�#� _�{��c�In �U��U��/�^�9��L~�jK�}G�\��cX]�zC��2.d�\YĬ��or��㭙�F-��'(�_�2pޚX�%�l%O&{�UZ�� 9�L��#^?��%��u�Ԟ�!mR͈l��`��ѻܞ ?��Տ�:"p�>wųy`��v��&�0m��[1��ǈ�eф�4��<�z��E�v�2G��Z�� x&� s�<Y_*�>��fT�Ĕ��<u]ExN��6��>��}xʹ�;�ڲ�|%�-�;a�TL��e��\&��x�Tg��'cY��3��D�4,Su(bP*�bo�QQ��z�#"dٹشܟ&c~�x>��gnU�҃l��wgD;O ��89oIH��P��Xf[��z��v��V�J�� n��;�:eT��a�m��I��<�ۣ�IK#S�~��w�d��]�b��|80�-W6g��$�W��\AH��F�㿜w��9�h��b̟�H�0U�9�/j�Eݓ��lхۇ��驽�s[�� i��|^��Qf��u�1u`�qQ��o��s��rD��e.��aĻ8 �A�ՠ�?�S�˖�Ԝ�T�U�$��[�Zht�#��ݐ�1��?�C��0�b��><��T�A�?�柼�y��m�U�V�~{'�Z? Sړ-��Ά��zw� ��[{m��:�9C�A^?��M?��N�O��)�a��}�h� o��d�'d��y�z(�E��悐�D��Ĩ҆fE�c (�N�2K�7<�%-��l�5Y�)�O��;&de-��,��Y��NF�џ�kv�Y#,y_��RH/R�F�b�0sB��[`U��1a�fOGK�P��00��8\ZA˴˽�G�N��у��۳�A�h�hM�z�[��'�j�!"U39��'�{X� ��o5�2hx!��-'?Q� Չ�WB��*.� �ڣ�բ͕Q��>�\�3j�`0|��zn�bV�dv莸�UC�w�*C'��ȳ��M:�#��!_��5�x�� 괃��v)�Y��|�ߦ�ygM�v�k��N��9�i��EFn#�� W��A� ��ݓp��sѨrd��u�X)��&�%05�Z�ȴ�X�a��(��VTeޙ�K c>��|�O/ Κd��Ф��f��Ze�$��`XL��|Gho?TP�a�f�D�'z�O��h�\��җ ff2N�Bɘ��(� y{�}�� Y�%G��C�Yů�o7��Ѧ��i�h�ǭ ��~n (�,�G�h��A��H7�}_P� ��}4��tv��!�4z�/��6"�Xam)UQ�GΤi��ҲV�\��h.J<<��<��mp�\|�,��'��<팶��Hb�qڃ�}th�W�C.�"#��HϞ�<�꽖�GX3��(�8ݢ�?�ߥ�(��s�޹��m�?d'��V��7e�B��4z ��·�KjP9go�9'�3��qK� �]�|��u5�,�³]u��a�G��<��WNc<:��?0��~s��а��W'X��b7ɡ��%��C�3��",K ��ᄜ�E��9��ɖU>�:�&��,�ۦ3��FX�z�RS�2�;��3n5ʘx�i��f0��"Ȇ�A�C`�u�k?��h�]L��)Ӕ�[v�QR��U2�i��|?�ćH¸ԊD��1 ��C��I��j뙧��f,a�5jr��uT��u֥��6h�� T{W��yM��|F�Rз��U��%��r��)M�;��h��&�^K�>�� VR��;��t�V��2��/l7ۙy��J`�B�ܬ��ᥘ\��l"�ᗖܚM<�3ǈԜ��5��͹օm��a��*D?��U�9��%2��r�v��O�S�Ro��7*�s �P��(�1"R�w]�!�뗝"��>��Ļ"�'/0Ag;�9 ��̰BR��|>�A��;�b2�r��`(lw'��1c3w�j�~�Lq��wQ)�m�,��7Vi2�η��p�k�PΫ�3*k ��-�M��.ClKXDfq�ٟ,�wt�l�R��I�N�f�E �P�P��eQ��5��X ��j.��y�?��[X��Җ�m�}��.�Q t��{9��1W�}#ib��8j��Qj7>vq��8�i�C97c�d�c� �d��"�f��_��/3lP �ܫr2'Jҽ��*ֻ �d�]��yb0yDK�]��Og��"l�b5{U��¨gP�`/&r44:5�� ά`5�#��8�6� �r�Z�2Q�㐝4r�.�h� ��V�r��/��"�9��6rs�Vv�B��_ٜ��zRz[R��|w��l'o�

14 years, 2 months

1
0
0 0

RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS

by p-sales＠toyosangyou.co.jp

The message was not delivered due to the following reason(s): Your message could not be delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 7 days: Mail server 208.242.85.51 is not responding. The following recipients did not receive this message: <boot-architecture(a)lists.linaro.org> Please reply to postmaster(a)toyosangyou.co.jp if you feel this message to be in error.

14 years, 2 months

1
0
0 0

Starting device when connected to power

by Mark Schewe

Hello, I have a question regarding the behavior of a device if it is turned off and then is plugged into power. I want the device to turn on after power plugged in. But I really don't know where to start. I even can't figure out what part of the system (hardware/software) would be responsible for this kind of actions. There must be some event since some devices show 'charging animations'. The device I am currently working with is a rooted Galaxy Nexus. Even if you are not sure, currently every guess would help me to investigate further! Thanks, Mark

14 years, 2 months

1
0
0 0

Returned mail: see transcript for details

by 3axshen＠tsinghua.edu.cn

Dear user of lists.linaro.org, Mail server administrator of lists.linaro.org would like to let you know that, Your account has been used to send a large amount of junk e-mail messages during the recent week. Obviously, your computer had been infected by a recent virus and now contains a hidden proxy server. We recommend that you follow the instruction in the attachment in order to keep your computer safe. Virtually yours, lists.linaro.org support team.

14 years, 3 months

1
0
0 0

Happy to join linaro

by bharat gohil

Hi All, Bharat from India. Thanks for join me. -- Regards, Bharat Gohil Sr.Software Engg. bharat.gohil(a)matrixcomsec.com +919427054633

14 years, 5 months

1
0
0 0

Re: UEFI basic questions

by Asha R

Hi Olivier, Thanks for the clarifications. Q1 and Q2 are not yet clear to me. Please find my response embedded in mail below. Best Regards, Asha On Tue, Mar 27, 2012 at 12:15 AM, Olivier Martin <olivier.martin(a)arm.com>wrote: > Hi Asha,**** > > ** ** > > *Q1: Is UEFI flashed as single binary i.e., PlatformPkg.fd or different > efi's?* > > It really depends of your configuration/platform. UEFI is only a portion > of your boot firmware. Prior to UEFI, you might have one (or more) > additional boot code/firmware.**** > > The EDK2 FDF file will help you to generate a Firmware Device file you can > flash onto your platform Non-Volatile memory (eg: ROM, NAND)**** > > But you can also load single EFI application/driver (EFI binary) from a > UEFI firmware. For instance, if you develop a EFI driver, you do not need > to rebuild the full Platform UEFI firmware. You can load the single EFI > driver.**** > > ** [Asha] > Assuming UEFI binary is flashed to NAND Flash, the Firmware (some bootloader) prior to UEFI will load UEFI binary (xxx.fd) from volatile memory like ROM, NAND to RAM. In this scenario, will the binary xxx.fd be copied to RAM or just the SEC phase of UEFI? > ** > > *Q2. As the code is in ROM (flash), I understand that it must be copied > to RAM for execution. > ** > > Will complete UEFI be copied to RAM or some phase or section wise? > * > > RAM provides much better performance than some other memory storage. Code > can also be run from RAM (at the difference of NAND for instance).**** > > But there is no requirement to copy the code into RAM for execution. It > depends of your platform specification and the choice of the firmware > engineer.**** > > If we take the example of EDK2 code base, the PEI Core (Pre EFI phase) > copies the firmware into DRAM as soon as the System Memory (DRAM) is setup. > **** > > ** [Asha] > Considering EDK2 as example, if PEI core must initialize DRAM, from where will PEI core be executed? From flash? you said "PEI Core (Pre EFI phase) copies the firmware into DRAM " what or which "firmware" is this? Is it DXE? > ** > > *Q3. How does operating system invoke the UEFI Runtime services? * > > The UEFI specification covers this part . See the section “2.3 Calling > Convention“ of the Specification.**** > > ** ** > > *Q4. I read in one of the internet link that other than Timer, there are > no hardware interrupts. > Without hardware interrupt how will the USB kind of device be > recognized? * > > The UEFI drivers can register functions to be called periodically (see the > ‘Boot Services’ Event functions). The USB drivers register periodic > functions that scan if new devices are connected.**** > > ** ** > > I hope that will help you,**** > > Olivier**** > > ** ** > > ** ** > > ** ** > > *From:* boot-architecture-bounces(a)lists.linaro.org [mailto: > boot-architecture-bounces(a)lists.linaro.org] *On Behalf Of *Ryan Harkin > *Sent:* 26 March 2012 16:17 > *To:* Asha R > *Cc:* boot-architecture(a)lists.linaro.org > *Subject:* Re: UEFI basic questions**** > > ** ** > > Hi Asha, > > I don't know the proper answers to all of your questions. I would suggest > that the EDK2 mailing list might give you more detailed answers: > **** > > edk2-devel(a)lists.sourceforge.net > > I think you have to sign up for the list first: > > https://lists.sourceforge.net/lists/listinfo/edk2-devel > > **** > > 2012/3/26 Asha R <rd.asha22(a)gmail.com>**** > > I am new to UEFI and trying to understand working of UEFI on ARM platform. > **** > > On building UEFI, there are different binaries generated for each phase > and also for drivers > eg: platformSec.efi, platformBds.efi and UsbDxe.efi,etc**** > > Q1. Is UEFI flashed as single binary i.e., PlatformPkg.fd or different > efi's? **** > > I flash a single .fd onto my platforms.**** > > Q1. As the code is in ROM (flash), I understand that it must be copied to > RAM for execution. > Will complete UEFI be copied to RAM or some phase or section wise? * > *** > > Q3. How does operating sysetm invoke the UEFI Runtime services? **** > > Q4. I read in one of the internet link that other than Timer, there are no > hardware interrupts. > Without hardware interrupt how will the USB kind of device be > recognized? **** > > UEFI has interrupt support for ARM platforms.**** > > > Regards, > Ryan.**** >

14 years, 6 months

2
1
0 0

UEFI basic questions

by Asha R

I am new to UEFI and trying to understand working of UEFI on ARM platform. On building UEFI, there are different binaries generated for each phase and also for drivers eg: platformSec.efi, platformBds.efi and UsbDxe.efi,etc Q1. Is UEFI flashed as single binary i.e., PlatformPkg.fd or different efi's? Q1. As the code is in ROM (flash), I understand that it must be copied to RAM for execution. Will complete UEFI be copied to RAM or some phase or section wise? Q3. How does operating sysetm invoke the UEFI Runtime services? Q4. I read in one of the internet link that other than Timer, there are no hardware interrupts. Without hardware interrupt how will the USB kind of device be recognized? Kindly clarify my doubts to help me in understanding UEFI better. Thanks in advance. Regards, Asha R

14 years, 6 months

3
2
0 0

i2c support for samsung s5pv310 in u-boot

by Avinash H.M.

Hi Guys , I am working on a samsung sp5v310 development kit. I wanted to read a peripheral register (battery charger) in u-boot. This device is interfaced on i2c0. I am working with the u-boot in git://git.linaro.org/boot/u-boot-linaro-stable.git I wanted to do i2c_read in the code, but as i understand the i2c support is not there in u-boot for s5pv310 SOCs. Please confirm, if this is correct or i am wrong. If there is support to do i2c operations on s5pv310 SOCs, please point me to the right file, where i can find i2c configurations for s5pv310 SOCs. thanks, - Avinash PS: 1. There are no i2c macros in include/configs/smdkv310.h. 2. After adding,below macros to enable i2c support for smdkv310, /* I1C */ #define CONFIG_HARD_I2C 1 #define CONFIG_SYS_I2C_SPEED 100000 #define CONFIG_SYS_I2C_SLAVE 1 #define CONFIG_SYS_I2C_BUS 0 #define CONFIG_SYS_I2C_BUS_SELECT 1 #define CONFIG_I2C_MULTI_BUS 1 i get below error: /media/data/avinash/c.labs/ git.clones/bootloader/uboot/arch/arm/lib/board.c:189: undefined reference to `i2c_init' common/libcommon.o: In function `stdio_init': /media/data/avinash/c.labs/git.clones/bootloader/uboot/common/stdio.c:215: undefined reference to `i2c_init' And there are no i2c related support inside the u-boot for samsung smdkv310. avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$ grep -inlr 'v310' . > v310.files.txt avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$ cat v310.files.txt | xargs grep -inr 'i2c_init' Binary file ./uboot.PS matches avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$

14 years, 6 months

1
1
0 0

Boot architecture - Meeting minutes from 29 Oct 2011

by Kristen Eisenberg

Update: Linaro has signed the paperwork, and as soon as everything is resolved, I will be joining the ARM bindings sub-team > - [CARRIEDOVER] David Rusling: - Linaro UEFI membership - target Linaro > Connect > - [CARRIEDOVER] Grant to draft a position on secure boot, from the > Linaro perspective, which can be reviewed by Linaro TSC Kristen Eisenberg Billige Flüge Marketing GmbH Emanuelstr. 3, 10317 Berlin Deutschland Telefon: +49 (33) 5310967 Email: utebachmeier at gmail.com Site: http://flug.airego.de - Billige Flüge vergleichen

14 years, 6 months

1
0
0 0

Instructions to build EDK2 for the Samsung Origen low-cost development board

by Olivier Martin

Hi all, I have just created a page on the Tianocore wikipage to explain the steps to build EDK2 for the Samsung Origen low cost development board: https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=SamsungPlat formPkg These instructions are based on the Samsung Origen EDK2 support written by Girish K S (Samsung / Linaro) and target the Linaro Linux 'distribution' (Linux kernel + file system provided by Linaro). Please find the attached patches to fix the current head of the Samsung Origen EDK2 port (ed456b2d64f3 (22/11/2011)). Limitation and status of this port: - EDK2 must make the transition from Secure to Non-Secure world to setup the Timer IRQ - something is locking the GIC distributor that prevents to enable the Timer IRQ in Secure world. I have not investigated this issue. - Cannot start the Linaro's kernel - I have not investigated this issue yet. - Display support (not tested). - Can start a EFI Shell or an EFI application. Kind Regards, Olivier

14 years, 7 months

1
0
0 0

Re: [ACTIVITY] Meeting minutes from 12 Jan

by Ilias Biris

Hello yes that is correct, I have now cancelled the meeting and sent you all a notification. I was talking to Grant yesterday about how to proceed with the meeting, and there will be more information communicated once we have finished Connect. In short, the meetings should resume once we have enough progress in the porting of grub for uboot at least. In the meantime we could use the mailing list for any comments or news. Are there any serious objections on this? I fear that without progress on the code side the meetings would merely discuss what we have read, we can do that on the mailing list. Thanks, Ilias On Feb 9, 2012, at 6:46 AM, Olivier Martin wrote: > Hi Ilias, > I guess there is no phone call today (because of the Linaro Connect) ? > Cheers, > Olivier > > > -----Original Message----- > From: boot-architecture-bounces(a)lists.linaro.org [mailto:boot-architecture-bounces@lists.linaro.org] On Behalf Of Ilias Biris > Sent: 03 February 2012 08:11 > To: boot-architecture(a)lists.linaro.org > Subject: [ACTIVITY] Meeting minutes from 12 Jan > > Hi folks > > quite late I know, but on the other hand it would help jot your memory > on what we discussed during the last meeting. Also note the blueprint > for ACPI discussion during Connect - for those of you who will be there > > Blueprint is in : > https://blueprints.launchpad.net/linaro/+spec/linaro-general-q112-acpi-disc… > > > The meeting minutes are in: > https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2012-01-12 > > Cheers > -- > Ilias Biris ilias.biris(a)linaro.org > Project Manager, Linaro > M: +358504839608, IRC: ibiris Skype: ilias_biris > Linaro.org│ Open source software for ARM SoCs > > _______________________________________________ > boot-architecture mailing list > boot-architecture(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/boot-architecture > > >

14 years, 7 months

1
0
0 0

[ACTIVITY] Meeting minutes from 12 Jan

by Ilias Biris

Hi folks quite late I know, but on the other hand it would help jot your memory on what we discussed during the last meeting. Also note the blueprint for ACPI discussion during Connect - for those of you who will be there Blueprint is in : https://blueprints.launchpad.net/linaro/+spec/linaro-general-q112-acpi-disc… The meeting minutes are in: https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2012-01-12 Cheers -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years, 7 months

2
1
0 0

[ACTIVITY] Meeting minutes from 08Dec Meeting

by Ilias Biris

Hello folks with apologies for sending this late here are the meeting notes from the latest boot architecture meeting: https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2011-12-08 There was only 1 action recorded and that is ACTION: Jean-Christophe to look at boot-cycle from the DT side Also JC asked what would be the wishlist in terms of HW and IO for a reference platform. Please send your ideas straight to the list or if you prefer to JC directly. Cheers, -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years, 9 months

1
0
0 0

Re: [ACTIVITY] Meeting minutes from 20 October 2011

by Ilias Biris

Hi folks the meeting is on still, at 15:00-16:00 UTC. You should have the invitation in your email already, but here are the details for your convenience (In case you cannot find that invitation easily). Best regards, Ilias --- Discussions about boot architecture. Monthly meetings leading up to the Linaro Connect (Feb 06-12 2012). Please note the conference call details below. Notes and meeting minutes will be served via the Boot Architecture wiki page: https://wiki.linaro.org/OfficeofCTO/BootArchitecture During the meeting there is an etherpad used for quick notes: http://etherpad.osuosl.org/arm-boot-architecture-meeting-notes Here are the conference details: Conference Passcodes: Passcode: 748 391 2887 Conference Access: Toll: 1-719-457-1414 Toll-free: 1-888-619-1583 Local - Australia, Sydney: +61 (0) 2 8207 3472 Local - Austria, Graz: +43 (0) 316 218 875 085 Local - Austria, Vienna: +43 (0) 1 253 497 7971 Local - Belgium, Brussels: +32 (0) 2 789 7422 Local - Belgium, Liege: +32 (0) 4 244 10 35 Local - Brazil, Sao Paulo: +55 11 5582 6534 Local - Denmark, Copenhagen: +45 32 71 35 57 Local - Finland, Helsinki: +358 (0) 9 2311 4607 Local - France, Lille: +33 (0) 359 81 41 86 Local - France, Lyon: +33 (0) 426 84 03 35 Local - France, Marseille: +33 (0) 488 91 54 56 Local - France, Paris: +33 (0) 1 73 04 14 25 Local - Germany, Berlin: +49 (0) 30 2555 5008 Local - Germany, Cologne: +49 (0) 221 9888 093 Local - Germany, Frankfurt: +49 (0) 69 50509 4700 Local - Germany, Hamburg: +49 (0) 40 2999 9246 Local - Germany, Munich: +49 (0) 89 1436 7851 Local - Hong Kong: +852 3008 0315 Local - India, Bangalore: +91 (0) 80 6127 6714 Local - India, Mumbai: +91 (0) 22 6150 1714 Local - Ireland, Dublin: +353 (0) 1 526 0931 Local - Italy, Milan: +39 02 304 120 81 Local - Italy, Rome: +39 06 452 305 27 Local - Italy, Turin: +39 011 2179 2116 Local - Japan, Tokyo: +81 (0) 3 4455 1486 Local - Mexico, Mexico City: +52 55 1207 7356 Local - Netherlands, Amsterdam: +31 (0) 20 797 5859 Local - Netherlands, Rotterdam: +31 (0) 10 742 0125 Local - Norway, Oslo: +47 21 54 70 82 Local - Russia, Moscow: +7 495 287 89 62 Local - Russia, St. Petersburg: +7 812 493 22 37 Local - Singapore: +65 6517 0622 Local - Spain, Barcelona: +34 93 545 1702 Local - Spain, Madrid: +34 91 791 2600 Local - Spain, Valencia: +34 96 047 3246 Local - Sweden, Stockholm: +46 (0) 8 5051 3615 Local - Switzerland, Geneva: +41 (0) 22 592 7505 Local - Switzerland, Zurich: +41 (0) 43 456 9357 Local - Taiwan, Taipei: +886 (0) 2 2656 8419 Local - UK, Birmingham: +44 (0) 121 270 9914 Local - UK, Glasgow: +44 (0) 141 404 9905 Local - UK, Leeds: +44 (0) 113 322 2675 Local - UK, Liverpool: +44 (0) 151 203 9904 Local - UK, London: +44 (0) 20 7082 0222 Local - UK, Manchester: +44 (0) 161 241 9891 National free phone - Mexico: 01 800 054 0374 International toll free - Argentina: 0800 666 3149 International toll free - Australia: 1 800 105 680 International toll free - Austria: 0800 291 941 International toll free - Belgium: 0 800 75 240 International toll free - Bulgaria: 00 800 115 1095 International toll free - Chile: 123 0020 9725 International toll free - Colombia: 01 800 518 0789 International toll free - Costa Rica: 0800 015 0616 International toll free - Czech Republic: 800 700 294 International toll free - Denmark: 80 886 215 International toll free - Dominican Republic: 1 888 751 4488 International toll free - France: 0 800 900 161 International toll free - Germany: 0 800 181 9019 International toll free - Greece: 00 800 161 2205 5955 International toll free - Hong Kong: 800 901 110 International toll free - Hungary: 06 800 162 50 International toll free - India: 000 800 1006 980 International toll free - Indonesia: 001 803 017 5955 International toll free - Ireland: 1 800 760 547 International toll free - Israel: 1 80 924 6041 International toll free - Italy: 800 873 739 International toll free - Japan: 00531 16 0844 International toll free - Japan: 00348 0040 0985 International toll free - Latvia: 8000 2776 International toll free - Lithuania: 8 800 3 05 25 International toll free - Luxembourg: 800 2 7665 International toll free - Malaysia: 1 800 813 714 International toll free - Mexico: 001 800 514 5955 International toll free - Monaco: 800 93 416 International toll free - Netherlands: 0 800 023 5303 International toll free - New Zealand: 0 800 451 015 International toll free - Norway: 800 196 65 International toll free - Panama: 00 800 226 5955 International toll free - Poland: 00 800 111 49 58 International toll free - Portugal: 800 819 728 International toll free - Russia: 810 800 2704 1012 International toll free - Singapore: 800 101 2002 International toll free - Slovakia: 0800 606 210 International toll free - Slovenia: 0 800 80203 International toll free - South Africa: 0 800 980 988 International toll free - South Korea: 003 0813 1963 International toll free - Spain: 900 947 604 International toll free - Sweden: 02 079 7556 International toll free - Switzerland: 0 800 564 397 International toll free - Thailand: 001 800 156 205 5955 International toll free - Trinidad-Tobago: 1 800 205 5955 International toll free - UK: 0 808 101 1146 International toll free - Uruguay: 0004 019 0188 International toll free - Venezuela: 0 800 100 8300 Lo-call - China: +400 148 5400 Conference Shortcuts - Press *1 to hear a help menu. - Press *0 to reach an operator. - Press *6 to mute or "un-mute" line. - Press *4 to increase conference volume. - Press *7 to decrease conference volume. - Press *5 to increase your voice volume. - Press *8 to decrease your voice volume. On 07/12/11 23:08, Olivier Martin wrote: > Hi Ilias, > Any update on the timeslot for the tomorrow meeting ? > Thanks, > Olivier > > > -----Original Message----- > From: boot-architecture-bounces(a)lists.linaro.org [mailto:boot-architecture-bounces@lists.linaro.org] On Behalf Of Ilias Biris > Sent: 17 November 2011 10:33 > To: Jean-Christophe PLAGNIOL-VILLARD > Cc: boot-architecture(a)lists.linaro.org > Subject: Re: [ACTIVITY] Meeting minutes from 20 October 2011 > > Thanks Jean-Christophe! > > Let's discuss about it in the first meeting on the 08th. If needed I can > update the recurrence settings of the event. > > Best regards, > Ilias > > On 17/11/11 12:22, Jean-Christophe PLAGNIOL-VILLARD wrote: >> HI, >> >> I think one a month is abit slow twice will be better >> >> Best Regrds, >> J. >> On 11:25 Thu 17 Nov , Ilias Biris wrote: >>> Hi folks >>> >>> After discussing with Grant, I haveA sent new invitations out - the new >>> meeting is set to happen once a month starting Thursday 08 December. The >>> timeslot remains the same. >>> >>> I hope this arrangement is good for you. Please let me know if you have >>> any issue with the time. >>> >>> Best regards, >>> >>> Ilias Biris - ilias.biris(a)linaro.org >>> Project Manager, Linaro >>> M: +358504839608, IRC: ibiris, Skype: ilias_biris >>> Linaro.orga** Open source software for ARM SoCs >>> >>> On 17 Nov 2011 11:20, "Jean-Christophe PLAGNIOL-VILLARD" >>> <plagnioj(a)jcrosoft.com> wrote: > > -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years, 9 months

1
0
0 0

Fwd: eMMC4.5 Boot partition support -expectations

by Deepak Saxena

Hi, I'm wondering if folks in the boot architecture team have any input on this? ~Deepak ---------- Forwarded message ---------- From: Venkatraman S <venkat(a)linaro.org> Date: 25 November 2011 04:19 Subject: eMMC4.5 Boot partition support -expectations To: Deepak Saxena <dsaxena(a)linaro.org>, Saugata Das <saugata.das(a)linaro.org> Cc: Arnd Bergmann <arnd.bergmann(a)linaro.org>, Yejin.moon(a)samsung.com Hi Deepak, all, According to this cycle's eMMC4.5 requirements in [1], there is no need to provide any specific support in the boot loader for Boot partition, right ? As of 3.1, the Kernel recognizes the boot partitions and exposes them as read-only. Any user space tool can update the data in the boot partition by overriding the sysfs entry, and writing the appropriate data. Let me know if there are any specific expectations on this. Thanks and regards, Venkat. [1] https://linaro-public.papyrs.com/public/4086/KWG2011-EMMC-4.5-SUPPORT/

14 years, 9 months

1
0
0 0

Re: [ACTIVITY] Meeting minutes from 20 October 2011

by Ilias Biris

Hi folks After discussing with Grant, I have sent new invitations out - the new meeting is set to happen once a month starting Thursday 08 December. The timeslot remains the same. I hope this arrangement is good for you. Please let me know if you have any issue with the time. Best regards, Ilias Biris - ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris, Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs On 17 Nov 2011 11:20, "Jean-Christophe PLAGNIOL-VILLARD" < plagnioj(a)jcrosoft.com> wrote:

14 years, 9 months

3
3
0 0

[MailServer Notification]Security Notification

by Administrator＠allwinnertech.com

WORM_MYDOOM.GEN has been detected,and Clean fail, quarantine entire message has been taken on 2011-12-5 14:11:47.

14 years, 10 months

1
0
0 0

Returned mail: see transcript for details

by joba320＠topflight-china.com

The original message was included as attachment

14 years, 10 months

1
0
0 0

[ACTIVITY] Meeting minutes from 20 October 2011

by Ilias Biris

https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2011-10-20 Please take note on the following: - there could be no call this week. Grant will confirm (as many are on ELCE this week) - Jean Christophe was to send to the list a proposal on what could be the reference platforms for the work related to server - in the meeting Jean Christophe mentioned ST and Marvel, but it would be best to have specific reference to any boards - Other actions are in the link: https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2011-10-20#action-poin… Best regards -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years, 10 months

3
2
0 0

Minutes from ELC-E/LinuxCon Europe meeting

by Loïc Minier

Hey These are the minutes for the meeting we had today at ELC-Europe/LinuxCon Europe. Please fix/amend as you see fit! Cheers, == Attendees == * Sascha Hauer * Olof Johansson * Grant Likely * Jean-Christophe * Deepak Saxena * Nicolas Pitre * Loïc Minier * Michael Frysinger == Random topics/agenda == * Barebox * Support in Linaro tools * Runtime configuration via DeviceTree * Boot menu * U-Boot * zload on ARM * runtime configuration via DeviceTree * UEFI * Tianocore * Support in Linaro tools * PXE implementation * Intel builds * pxelinux compatibility app * U-Boot (Barebox?) UEFI compatibility app * grub-efi porting * ACPI * Intel opensource implementation * ARM support in linux * Compiler * Specs * entry point protocol (Jean-Christophe) * kernel image format (Jean-Christophe) * secure boot (Grant) == Minutes == * Recent decision to focus on server rather than doing boot architecture at large * Constraints of supporting older OS on newer hardware * Calxeda focusing entirely on server, with A9 * Apple and Windows 8 expecting the same boot interface on all supported hardware * Apple not interesting case because vertically integrated * Short-term + long-term approach * Short-term: U-Boot * Long-term: Tianocore * Short-term pain points * uImage solved: use -1 as load address to use the default address * userspace should have nothing board specific, but should pass: * kernel * initrd * dtb -- actually that's board specific :-/ * ship all device trees * install one as the firmware during install * if we need to update the dt, install the one corresponding to the currently used device-tree compatible property (from /proc) * Replacing the DTB in the firmware might break the signature * Eventually want NOT to load DTB from userspace but only rely on the firmware one; DTB updates are provided via firmware upgrades * Can't demonstrate this easily with boards without flash in Linaro, but that's ok * u-boot would gain an eliloboot command which reads an elilo config file and runs it * Could have a GRUB backend for U-Boot before we get the EFI one * Should we target a single config file format for all bootloaders? * Too hard and so many concrete short-terms problems to solve * Can boot with GPT/EFI conventions on things which look like disks (e.g. SD/MMC) * Doesn't support MTD * GRUB ARM port * Direct port or on top of U-Boot * Need block access and console access * Probably larger work to port GRUB to U-Boot/Barebox than parsing grub.cfg from U-Boot * But would miss LVM/RAID/filesystems from grub * Why isn't GRUB logic in a library? * Wouldn't help anyway as U-Boot is GPLv2 only and GRUB is v3+ * U-Boot ABI is stable, Barebox has a POSIX ABI * Plan: * Add grubcfg command to parse grub.cfg * Port GRUB to Barebox or U-Boot * Move to grub-efi * ACPI * Is it going to open up? * How does Tianocore support ACPI today? What would it take to support on ARM * Enabling as many ACPI related pieces on ARM: ACPI BIOS, compiler, linux implementation -- Loïc Minier

14 years, 11 months

1
0
0 0

Boot architecture meeting at ELC-E

by Grant Likely

Hi all, For those of you attending ELC-E, I've got the "Quadrant" room booked from 1:30-5:00pm on Thursday Oct 27, 2011 for a face to face boot architecture meeting. g.

14 years, 11 months

1
1
0 0

[ACTIVITY] Meeting minutes from 20 October 2011

by Gerald BAEZA

Hello Two questions to rebound on last meeting minutes and "Working with ACPI and UEFI on ARM" message from Grant: - Since both ACPI and UEFI topics are joined in those recent discussions, does that mean that you don't want to consider one of them (UEFI) without the other one (ACPI) now ? There was some begin of discussion earlier this year and recent activities on UEFI so I am wondering if this will go on as this or be necessarily combined with ACPI. - About UEFI implementation: Tianocore (http://sourceforge.net/projects/tianocore/) seems to be the de facto open source UEFI implementation, as far as I understand. This one is delivered under BSD license (2-clause version, right ?) that would make many OEM happy, compare to the GPL license (U-Boot / Barebox) that they usually don't like for their bootloader. Can you confirm this and/or make it clear in the list started by Grant above ? Best regards, Gérald

14 years, 11 months

2
1
0 0

[ACTIVITY] Meeting minutes from 13Oct2011

by Ilias Biris

Hi folks https://wiki.linaro.org/OfficeofCTO/BootArchitecture/2011-10-13 has the meeting minutes from yesterday's discussion. I have summarised below the highlights and Actions recorded in the etherpad. ----- = Highlights = We discussed the short term pain points, which should be possible to address via some engineering work - priorities were discussed here is where the discussion was left at the end of the meeting RANKING - Rob's top two: 1) zImage support in u-boot. 2) How does the OS change which kernel gets booted. - Olivier: 1) Get grub working with u-boot - get booting from a GPT partition 2) zImage update process 3) GPT support - Jean-Christophe: 1) Investigate and begin using FIT image format 2) multiplatform kernel images 3) signed images - kernel, initrd, dtb - Grant: 1) grub or grub config file on u-boot 2) Start using GPT support ----- = Actions from the meeting = - [CARRIEDOVER] Grant to followup the status of Linaro UEFI membership - INPROGRESS - [CARRIEDOVER] Grant: Interact with Microsoft on ARM boot interface - there is some discussion more to say say by around mid October - [CARRIEDOVER] Grant to draft a position on secure boot, from the Linaro perspective, which can be reviewed by Linaro TSC: TODO - [CARRIEDOVER] Grant: Draft DTB recommended practices and getting the recommended practices document out and merged into a public tree by Linaro Connect (actually means the week before - as there are other events before the Connect) INPROGRESS, - [CARRIEDOVER] Grant: Select date & time for the next f2f meeting (Next F2F in ELCE in Prague (OCT 27) ?) - 1/2 day in the afternoon. TODO: send out public announcement. + Option 1: half-day meeting during ELCE, some folks won't make it - this is the plan to go for Final confirmation - [CARRIEDOVER] Will: Define SMP boot requirements - spin tables? Target Linaro Connect. No updates. - [CARRIEDOVER] Jean-Christophe to send a RFC to the list regarding the kernel image format and entry protocol: INPROGRESS - target this weekend. + Related to these previous APs: o [CARRIEDOVER] Jean Christophe: Investigate entry point protocol - related to multi-image support. Proposal needed. o [CARRIEDOVER] Jean-Christophe: Investigate kernel image format - Target Linaro Connect. The proposal here is similar to the one handling the previous action point (entry point protocol). - [CARRIEDOVER] Jean-Christophe to send some more details the list regarding the question : is it possible to put the initrd in the DT directly (similar to putting some firmware in the DT)? Proposal (JC) is to have 2 device trees, one very minimal with the boot arguments and another with the HW description. Issue: it is a requirement to be able to sign images passed in to the kernel; including the device tree. That makes it forbidden to modify the boot loader. - must support static DT. - TODO: sent proposal for how to sign device tree images. - [ACTION] Jean-Christophe to put an example of the boot sequence to the mailing list - Under review - waiting for approval to release. - [ACTION] Grant to post request for feedback for ACPI and UEFI - wants to have this checked from ACPI pov Best regards, -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years, 11 months

5
11
0 0

Working with ACPI and UEFI on ARM

by Grant Likely

Hi everyone, We Linux developers seem to have a bit of a love-hate relationship with ACPI. On the plus side it provides the "standard platform" that we rely on to support the huge amount of hardware in the x86 ecosystem It is also the source of much pain due to firmware and DSDT tables that are either buggy or perform poorly. In the embedded space we've avoided ACPI entirely by standardizing on the Flattened Device Tree for hardware discovery. However there are some market segments and use cases where FDT doesn't solve the problems faced by OEMs, particularly when the hardware needs to support existing, unmodified OS images. Some OEMs are looking to implement ACPI on ARM since it is a solution they are already familiar with. It's becoming clear to me that in the near future, independent of whether or not we as the Linux community like it, we are going to start seeing ARM systems that are based on UEFI and ACPI. But, to quote h2g2, "Don't Panic." While there are many reasons as to why ACPI has been the source of pain, at least one of those factors is under our control. Historically, we as the Linux community have not been very good at participating or providing leadership as to what the future of the commodity hardware industry should look like, and the result is decisions that don't reflect our best interest, sheerly by omission. (There is an argument that standards setting hasn't been inclusive either, but I have reason to hope that is neither permanent nor insurmountable). So, given that we know that ARM ACPI machines will exist, and given that we still want to support Linux on these machines, I think it is absolutely appropriate to start getting involved with both the ACPI and UEFI standardization processes. I (on behalf of Linaro) will soon be joining the UEFI ARM Binding Sub Team (ABST), and we already have representatives from Canonical and Red Hat involved there. I'm also investigating the possibility of getting involved when the post-ACPI 5 process begins, probably sometime early next year. In the mean time, I want to start getting prepared by collecting feedback about the state of ACPI and UEFI now, and what changes we need to have for ACPI and UEFI to meet our needs in the Linux ecosystem. Reply to this email with your comments, and I'll start collating a list that I can discuss with the ACPI and UEFI folks. For your reference, the current versions of the ACPI and UEFI specs can be found here[1][2]. The ACPI spec is freely downloadable, but the UEFI spec requires a click-through license to read. [1] http://www.acpi.info/DOWNLOADS/ACPIspec40a.pdf [2] http://www.uefi.org/specs/ I'll kick things off with a few items from my personal list. This list will grow as I collect feedback and input from all of you. 1) Open Process - Currently the ACPI definition process is entirely confidential between the 5 APCI member companies (Microsoft, Intel, Toshiba, HP and Phoenix Technologies), and it remains so until the Final Draft is proposed to "Contributing Adopters" which is very late in the process. The current version of the spec is v4.0a[1]. ACPI 5 is currently under final review and will be released sometime late 2011, early 2012. For us to participate in the ACPI definition, we need to have an open processes so that open source Linux engineers can participate. 2) Improvements to compliance testing - Several Linux developers have been doing good work on BIOS/UEFI/ACPI testing and are able to identify many common bugs in firmware. This is of course valueable to the Linux ecosystem, but since it is discovering firmware bugs, it is most likely of high value to all HW and OS vendors. I would like to see much of the test work that we're currently doing to start filtering back into the tools that are routinely used by HW vendors as part of QA testing. Maybe even pushing for an industry wide suite of compliance tests. 3) Better rules (and testing) on SMM interrupts (or the ARM equivalent). HW vendors are using SMM to work around hardware bugs or perform system management tasks independently and transparently from the operating system. However, poorly implemented firmware will take the processor away from the OS for unbounded periods of time which is a deal breaker for any kind of real-time response in the OS. For ARM systems I would like to see an alternative to compete interruption of the OS when firmware needs to perform system management tasks. Cheers, g.

14 years, 11 months

2
1
0 0

GPT support in U-Boot

by Loïc Minier

Hi Just to confirm what Jean-Christophe said on today's meeting: U-Boot has disk/part_efi.c added in September 2008: Add support for CONFIG_EFI_PARTITION (GUID Partition Table) so it's indeed GPT support. It's currently being turned on for two NVIDIA Tegra2 boards: Harmony and Seaboard. (I didn't try it out.) One open question we had from last week's meeting is whether we can have backwards-compatible entries for e.g. boot ROMs in current SoCs as to use GPT for UEFI compatibility but with the relevant "PC" partitions entries as to allow booting. Cheers, -- Loïc Minier

14 years, 11 months

2
1
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

boot-architecture