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
>
>
>
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
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
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/
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:
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
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
