All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Sasa Ostrouska <casaxa@gmail.com>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Jason Montleon" <jmontleo@redhat.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	lma@semihalf.com,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	stable@vger.kernel.org, "Takashi Iwai" <tiwai@suse.de>,
	"amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Tue, 31 Jan 2023 16:48:30 +0100	[thread overview]
Message-ID: <8aff3653-0d10-77ef-1eb7-b1d1fdef183e@intel.com> (raw)
In-Reply-To: <CALFERdwVzz5a7k7XjBkNyGKKd8+4Fez62Lq__6jOarqnBJQjJQ@mail.gmail.com>

On 2023-01-31 3:58 PM, Sasa Ostrouska wrote:
> On Tue, Jan 31, 2023 at 1:37 PM Cezary Rojewski
> <cezary.rojewski@intel.com> wrote:

...

> Hi Czarek,
>>
>> Could you provide us with the topology and firmware binary present on
>> your machine?
>>
> Sure, see below.
> 
>> Audio topology is located at /lib/firmware and named:
>>
>> 9d71-GOOGLE-EVEMAX-0-tplg.bin
> -rw-r--r--. 1 root root   37864 21 nov 20.18 9d71-GOOGLE-EVEMAX-0-tplg.bin
> 
> 
>> -or-
>> dfw_sst.bin
>>
>> Firmware on the other hand is found in /lib/firmware/intel/.
>> 'dsp_fw_kbl.bin' will lie there, it shall be a symlink pointing to an
>> actual AudioDSP firmware binary.
> 
> lrwxrwxrwx. 1 root root     23 23 gen 10.28 dsp_fw_kbl.bin.xz ->
> dsp_fw_kbl_v3402.bin.xz


I was hoping to receive the actual files. Names alone won't suffice. A 
bit of reverse engineering and I'll know exactly what topology I'm 
looking at.

  reply	other threads:[~2023-01-31 15:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 17:09 Google Pixelbook EVE, no sound in kernel 6.1.x Jason Montleon
2023-01-28 17:52 ` Greg KH
2023-01-29  0:23   ` Jason Montleon
2023-01-30  6:33     ` Jason Montleon
2023-01-30 11:27       ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-30 12:15         ` Cezary Rojewski
2023-01-30 12:22           ` Sasa Ostrouska
2023-01-31 12:36             ` Cezary Rojewski
2023-01-31 14:58               ` Sasa Ostrouska
2023-01-31 15:48                 ` Cezary Rojewski [this message]
2023-01-31 16:02                   ` Sasa Ostrouska
2023-01-31 15:16               ` Jason Montleon
2023-01-31 15:46                 ` Cezary Rojewski
2023-02-01 11:05                 ` Amadeusz Sławiński
2023-02-01 14:33                   ` Jason Montleon
2023-02-04 15:16                     ` Jason Montleon
2023-02-06  9:03                       ` Amadeusz Sławiński
2023-02-06 13:51                         ` Jason Montleon
2023-02-06 19:57                           ` Jason Montleon
2023-02-06 21:15                             ` Sasa Ostrouska
2023-02-09 16:13                             ` Jason Montleon
2023-02-09 19:22                               ` Jason Montleon
2023-02-10 13:09                               ` Cezary Rojewski
2023-02-10 14:56                                 ` Jason Montleon
2023-02-10 17:15                                   ` Sasa Ostrouska
2023-01-30 11:23 ` Linux kernel regression tracking (#update)
  -- strict thread matches above, loose matches on Subject: below --
2023-01-23 20:44 Sasa Ostrouska
2023-01-24  5:09 ` Greg KH
2023-01-24 10:18   ` Lukasz Majczak
2023-01-24 11:34     ` Sasa Ostrouska
2023-01-24 12:11       ` Lukasz Majczak
2023-01-24 14:31         ` Sasa Ostrouska
2023-01-24 21:38           ` Sasa Ostrouska
2023-01-25 15:48             ` Lukasz Majczak
2023-01-25 20:48               ` Sasa Ostrouska
2023-01-24 11:30   ` Sasa Ostrouska
2023-01-26 12:59 ` Linux kernel regression tracking (#adding)
2023-01-27 10:06   ` Sasa Ostrouska
2023-02-09 14:11     ` Sasa Ostrouska
2023-02-24  1:10       ` Sasa Ostrouska
2023-02-24 20:43         ` Sasa Ostrouska

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=8aff3653-0d10-77ef-1eb7-b1d1fdef183e@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=casaxa@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmontleo@redhat.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.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.