All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prashant Malani <pmalani@chromium.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: "Mr. Chromebox" <mrchromebox@gmail.com>,
	Benson Leung <bleung@google.com>,
	Benson Leung <bleung@chromium.org>,
	linux-kernel@vger.kernel.org,
	Tim Wawrzynczak <twawrzynczak@chromium.org>
Subject: Re: Null pointer dereference in cros-ec-typec
Date: Thu, 20 Jan 2022 23:51:28 +0000	[thread overview]
Message-ID: <Yen1gP6XB6bRo7OW@chromium.org> (raw)
In-Reply-To: <20220119203243.3zh6mcb2fauczn5k@eve>

Hey Alyssa,

On Jan 19 20:32, Alyssa Ross wrote:
> On Wed, Jan 19, 2022 at 12:44:06PM -0600, Mr. Chromebox wrote:
> > On Wed, Jan 19, 2022 at 12:24 PM Prashant Malani <pmalani@chromium.org> wrote:
> > >
> > > Thanks Alyssa,
> > >
> > > It looks like the right fix here should go in coreboot.
> > >
> > > I'll wait for a response from Matt regarding whether those EC commands
> > > are supported on the eve EC firmware image Mr.Chromebox releases.
> >
> > looking at Chrome-EC branch firmware-eve-9584.B,
> >
> > EC_CMD_GET_PD_PORT_CAPS is *not* supported
> > EC_CMD_USB_PD_PORTS is supported
> >
> > no difference in this regard between my updated EC firmware and the
> > latest stock EC firmware provided by Google for EVE
> >
> > > I have a fix but I can't test it since :
> > > - I am not sure how the Mr.Chromebox eve BIOS is compiled.
> >
> > same build system as upstream coreboot
> >
> > > - I don't have an eve.
> >
> > me neither :)
> 
> I'd be more than happy to test Coreboot patches on my eve and report
> back on anything that needs to be checked, if that helps?  I've built
> and installed it from source before.

Yes, this would be very helpful! Here is the link:
https://review.coreboot.org/c/coreboot/+/61262

Thanks a lot!

-Prashant


  reply	other threads:[~2022-01-20 23:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 16:37 Null pointer dereference in cros-ec-typec Alyssa Ross
2022-01-18 19:33 ` Benson Leung
2022-01-18 19:49   ` Prashant Malani
2022-01-18 20:12     ` Prashant Malani
2022-01-18 22:04       ` Mr. Chromebox
2022-01-18 22:16         ` Prashant Malani
2022-01-18 22:34           ` Mr. Chromebox
2022-01-19  0:35             ` Prashant Malani
2022-01-19  1:13               ` Mr. Chromebox
2022-01-19  2:37               ` Alyssa Ross
2022-01-19 18:24                 ` Prashant Malani
2022-01-19 18:44                   ` Mr. Chromebox
2022-01-19 20:32                     ` Alyssa Ross
2022-01-20 23:51                       ` Prashant Malani [this message]
2022-01-26 19:11                         ` Prashant Malani

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=Yen1gP6XB6bRo7OW@chromium.org \
    --to=pmalani@chromium.org \
    --cc=bleung@chromium.org \
    --cc=bleung@google.com \
    --cc=hi@alyssa.is \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrchromebox@gmail.com \
    --cc=twawrzynczak@chromium.org \
    /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.