New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 805651 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ textor@chromium.org
snanda@chromium.org
█ bhthompson@chromium.org
EstimatedDays: ----
NextAction: 2019-07-09
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add chipset family (BYT, APL, KBL etc) to feedback report metadata

Project Member Reported by kirtika@google.com, Jan 24 2018 
OS: R66

We go back and forth with Intel on what issues are restricted to what chipset family. Getting the right data to convince partners would be easier if we could include chipset family in the feedback reports. 
Otherwise, I can add a script that maps HWID to chipset family and add that extra step, each time we get our data.

Comment 1 by snanda@chromium.org, Jan 24 2018 

The board name should be included in the feedbacks I would think. Should be easier to go from that to the chipset than from the HWID.

Comment 2 by bhthompson@google.com, Jan 24 2018 

I was thinking the script would just be getting the board name from the HWID, but yea the board field is one step closer.

Comment 3 by benhenry@google.com, Jan 10

Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.
►

Sign in to add a comment