All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@csgraf.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot/EBBR plugfest at ELC-EU?
Date: Mon, 8 Jul 2019 15:19:54 +0200	[thread overview]
Message-ID: <cf663ecb-8384-93a7-2c1b-6b310b3d96fc@csgraf.de> (raw)
In-Reply-To: <20190708101307.qn5z3y6qrgkfyjpf@tomti.i.net-space.pl>


On 08.07.19 12:13, Daniel Kiper wrote:
> Sorry for late reply but I am busy...
>
> On Fri, Jun 28, 2019 at 11:42:06AM +0100, Leif Lindholm wrote:
>> On Fri, Jun 28, 2019 at 12:17:54PM +0200, Alexander Graf wrote:
>>> On 28.06.19 12:03, Heinrich Schuchardt wrote:
>>>> I would be interested in joining. I hope that for the plugfest no ELC conference ticket will be needed.
>>> The easiest option for that would be to submit a talk to ELC-E. IIRC the CfP
>>> is still open until July 1st. You could easily give one on "Progress in UEFI
>>> support on U-Boot" or "What it takes to run the edk2 Shell outside of edk2"
>>> or whatever :). You have plenty content to pull from.
>>>
>>> If the talk goes in, that helps visibility and gets you free ticket - maybe
>>> even travel sponsorship! :)
>>>
>>>> The problems with booting Linux via U-Boot UEFI I know of are on
>>>> 32bit ARM systems.  It could be helpful to have GRUB developers
>>>> joining.
>>> Let's make sure Daniel and Leif are on CC then :).
>>>
>>> Daniel, Leif, would you be available?
>> I don't know yet - UEFI Asia plugfest date hasn't been decided yet,
>> and is likely to end up around the same time. And actually another
>> unrelated event too.
>>
>> Certainly, Lyon is a quite convenient train journey from here :)
>>
>> But I'm also happy to look into GRUB issues on 32-bit systems remotely
>> if someone could point me at them.
> I am not planning to be at ELC-E but I can help remotely if it is
> needed. However, there is another option. There is pretty good chance
> that I will get a MC slot at LPC. I am looking for people who want to
> talk. The overall plan is to devote this MC for boot stuff with focus
> on security. So, this maybe good place to discuss this. However, I am
> not ARM expert, so, I would like to see Leif and/or Alex or somebody
> else familiar with ARM stuff there too.


I'll have to see if I can make it between OSFC the week before and other 
duties :)

Alex

  parent reply	other threads:[~2019-07-08 13:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  8:19 [U-Boot] U-Boot/EBBR plugfest at ELC-EU? Grant Likely
2019-06-28 10:03 ` Heinrich Schuchardt
2019-06-28 10:17   ` Alexander Graf
2019-06-28 10:42     ` Leif Lindholm
2019-07-08 10:13       ` Daniel Kiper
2019-07-08 10:18         ` Leif Lindholm
2019-07-08 10:26           ` Daniel Kiper
2019-07-08 13:27           ` Steve McIntyre
2019-07-24 13:39             ` [U-Boot] (Offlist) " Daniel Kiper
2019-07-30 15:33               ` Grant Likely
2019-07-31  7:14                 ` Matthias Brugger
2019-07-31 19:16                 ` Daniel Kiper
2019-08-08 11:02                   ` Grant Likely
2019-07-08 13:19         ` Alexander Graf [this message]
2019-06-28 13:14 ` [U-Boot] " Neil Armstrong
2019-07-08 12:22   ` Peter Robinson
2019-07-08 12:23 ` Peter Robinson
2019-08-08 11:06 ` Grant Likely
2019-08-13  8:35   ` Neil Armstrong
2019-08-21 10:38   ` Da Xue

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cf663ecb-8384-93a7-2c1b-6b310b3d96fc@csgraf.de \
    --to=agraf@csgraf.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.