All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bodireddy, Vikram" <vikram.bodireddy@linux.intel.com>
To: Adriana Kobylak <anoo@linux.ibm.com>,
	openbmc@lists.ozlabs.org, joel@jms.id.au, andrew@aj.id.au
Cc: suryakanth.sekar@linux.intel.com,
	richard.marian.thomaiyar@linux.intel.com
Subject: Re: openBMC eMMC image support
Date: Thu, 28 May 2020 22:15:28 +0530	[thread overview]
Message-ID: <48aa2966-cca6-342c-32f3-13493cfd9399@linux.intel.com> (raw)
In-Reply-To: <b8407f3ebaa1e5d24750551f4ad4f3aa@linux.vnet.ibm.com>

Thanks Adriana.

I will ping you on IRC. Can you please add me and Surya to all of the 
eMMC reviews.

Do we have any document on the image build changes that needed for eMMC?

On 27-05-2020 20:06, Adriana Kobylak wrote:
> Hi Vikram,
>
> On 2020-05-27 09:03, Bodireddy, Vikram wrote:
>> +Richard
>>
>> On 25-05-2020 15:29, Bodireddy, Vikram wrote:
>>> Hi Andriana,
>>>
>>> We are working on enabling OpenBMC eMMC support for Intel platforms.
>>>
>>> I see that you had started on it, and enabling it for ibm platforms.
>>>
>>> We would like to co-work with you to get to know eMMC support status 
>>> and  to contribute further to complete it.
>
> Great!
>
>>>
>>> Can you please help with the current status of OpenBMC eMMC support?
>
> For code update support, I’ll be pushing changes to gerrit for 
> phosphor-bmc-code-mgmt today/tomorrow to support eMMC.
> On the build side, there are a few WIP changes that I’ll be refreshing 
> this week as well, will tag them as ‘mmc’ on gerrit to be able to find 
> them, some previous commits have the topic ‘wic’ and ‘mmc’ already but 
> are in Abandoned or WIP, will be cleaning them up this week.
> Updates to the emmc doc: 
> https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/28443
>
>>>
>>> Also can you let us know your availability this week for a sync 
>>> meeting on the same?
>
> Ping me on IRC, any time during the day CST time, or if it's later at 
> night like 8/9pm CST time we can have Joel/Andrew J join us as well.
>
>>>
>>> Thanks
>>>
>>> Vikram
>>>

  reply	other threads:[~2020-05-28 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c2d7ecb8-b0b8-c5a3-12e7-7201fbd86b1a@linux.intel.com>
     [not found] ` <b13a0e82-4f88-f35b-0d3f-8f7d6a91351b@linux.intel.com>
2020-05-27 14:36   ` openBMC eMMC image support Adriana Kobylak
2020-05-28 16:45     ` Bodireddy, Vikram [this message]
2020-05-28 20:50       ` Adriana Kobylak

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=48aa2966-cca6-342c-32f3-13493cfd9399@linux.intel.com \
    --to=vikram.bodireddy@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=anoo@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=richard.marian.thomaiyar@linux.intel.com \
    --cc=suryakanth.sekar@linux.intel.com \
    /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.