[Sound-open-firmware] Reef, Minnowboard Max or Asus T100
Hello SOF Gurus,
This is Peter from ChromeOS@Google. I'm interested in the project and is trying to reproduce/ understanding from the main page https://www.alsa-project.org/main/index.php/Firmware. I noticed that in the instruction, the topic is reef w/ 4.8 kernel version. Since I'm quite a newbie in this area, wondering from a learning perspective, what would be recommended hardware for this purpose ?
Will it be a bit more complicated to build / debug it with Reef (like kernel need to sign after build), or ASUS T100 (an Windows platform).
Looking forward for reply, itsPeter
On Wed, 2017-11-29 at 22:55 +0800, Chun-ta Lin wrote:
Hello SOF Gurus,
This is Peter from ChromeOS@Google. I'm interested in the project and is trying to reproduce/ understanding from the main page. I noticed that in the instruction, the topic is reef w/ 4.8 kernel version. Since I'm quite a newbie in this area, wondering from a learning perspective, what would be recommended hardware for this purpose ?
The kernel is a little bit on flux atm, topic/sof-v4.14 is stable (but we are going to squash and rebase it soon in prep for upstreaming). Pierre is working on a new -next branch now though that will also include latest upstream too.
You should be able to run the code on any Baytrail, Cherrytrail or Braswell platform now.
Will it be a bit more complicated to build / debug it with Reef (like kernel need to sign after build), or ASUS T100 (an Windows platform).
The firmware code verification is not used on the above platforms so no need to sign an FW images.
Liam
Looking forward for reply, itsPeter
On 11/30/17 10:29 AM, Liam Girdwood wrote:
On Wed, 2017-11-29 at 22:55 +0800, Chun-ta Lin wrote:
Hello SOF Gurus,
This is Peter from ChromeOS@Google. I'm interested in the project and is trying to reproduce/ understanding from the main page. I noticed that in the instruction, the topic is reef w/ 4.8 kernel version. Since I'm quite a newbie in this area, wondering from a learning perspective, what would be recommended hardware for this purpose ?
The kernel is a little bit on flux atm, topic/sof-v4.14 is stable (but we are going to squash and rebase it soon in prep for upstreaming). Pierre is working on a new -next branch now though that will also include latest upstream too.
You should be able to run the code on any Baytrail, Cherrytrail or Braswell platform now.
To be more specific, I have sound on Lenovo 100s (orco) and Acer R11 (Cyan) - with a known bug on clock configuration for the latter.
Will it be a bit more complicated to build / debug it with Reef (like kernel need to sign after build), or ASUS T100 (an Windows platform).
The firmware code verification is not used on the above platforms so no need to sign an FW images.
Asus T100 has multiple versions,the TA and TAF which use different routing. With the old driver we have a dynamic run-time set of quirks that select the relevant I2S, it's not there in SOF yet. It's on my to-do list but at the moment I would not recommend this platform.
Liam
Looking forward for reply, itsPeter
Sorry for my late response on your kind replies.
Might I ask Liam, why is having the topic named "reef-xxx" ? Not really get what's the different on topics of "reef-xxx" and "sof-xxx".
Sounds like at least on ChromeOS side, none of you are developing on Reef related board at but on Cyan (Acer R11) instead ?
itsPeter
On Fri, Dec 1, 2017 at 12:33 AM, Pierre-Louis Bossart < pierre-louis.bossart@linux.intel.com> wrote:
On 11/30/17 10:29 AM, Liam Girdwood wrote:
On Wed, 2017-11-29 at 22:55 +0800, Chun-ta Lin wrote:
Hello SOF Gurus,
This is Peter from ChromeOS@Google. I'm interested in the project and is trying to reproduce/ understanding from the main page. I noticed that in the instruction, the topic is reef w/ 4.8 kernel version. Since I'm quite a newbie in this area, wondering from a learning perspective, what would be recommended hardware for this purpose ?
The kernel is a little bit on flux atm, topic/sof-v4.14 is stable (but
we are going to squash and rebase it soon in prep for upstreaming). Pierre is working on a new -next branch now though that will also include latest upstream too.
You should be able to run the code on any Baytrail, Cherrytrail or Braswell platform now.
To be more specific, I have sound on Lenovo 100s (orco) and Acer R11 (Cyan) - with a known bug on clock configuration for the latter.
Will it be a bit more complicated to build / debug it with Reef (like
kernel need to sign after build), or ASUS T100 (an Windows platform).
The firmware code verification is not used on the above platforms so no
need to sign an FW images.
Asus T100 has multiple versions,the TA and TAF which use different routing. With the old driver we have a dynamic run-time set of quirks that select the relevant I2S, it's not there in SOF yet. It's on my to-do list but at the moment I would not recommend this platform.
Liam
Looking forward for reply, itsPeter
On Sun, 2017-12-10 at 13:18 +0800, Chun-ta Lin wrote:
Sorry for my late response on your kind replies.
Might I ask Liam, why is having the topic named "reef-xxx" ? Not really get what's the different on topics of "reef-xxx" and "sof- xxx".
Yes, Reef was the old name for the firmware (REusable Embedded Firmware) and we did not know about the Chrome Reef board at the time. We changed the name to SOF for upstreaming to avoid confusion with th Reef Chrome board.
Sounds like at least on ChromeOS side, none of you are developing on Reef related board at but on Cyan (Acer R11) instead ?
No, I dont have that board atm.
Liam
itsPeter
Thanks. what a coincidence !
itsPeter
On Mon, Dec 11, 2017 at 6:22 PM, Liam Girdwood < liam.r.girdwood@linux.intel.com> wrote:
On Sun, 2017-12-10 at 13:18 +0800, Chun-ta Lin wrote:
Sorry for my late response on your kind replies.
Might I ask Liam, why is having the topic named "reef-xxx" ? Not really get what's the different on topics of "reef-xxx" and "sof- xxx".
Yes, Reef was the old name for the firmware (REusable Embedded Firmware) and we did not know about the Chrome Reef board at the time. We changed the name to SOF for upstreaming to avoid confusion with th Reef Chrome board.
Sounds like at least on ChromeOS side, none of you are developing on Reef related board at but on Cyan (Acer R11) instead ?
No, I dont have that board atm.
Liam
itsPeter
On Mon, Dec 11, 2017 at 2:22 AM, Liam Girdwood liam.r.girdwood@linux.intel.com wrote:
On Sun, 2017-12-10 at 13:18 +0800, Chun-ta Lin wrote:
Sorry for my late response on your kind replies.
Might I ask Liam, why is having the topic named "reef-xxx" ? Not really get what's the different on topics of "reef-xxx" and "sof- xxx".
Yes, Reef was the old name for the firmware (REusable Embedded Firmware) and we did not know about the Chrome Reef board at the time. We changed the name to SOF for upstreaming to avoid confusion with th Reef Chrome board.
Sounds like at least on ChromeOS side, none of you are developing on Reef related board at but on Cyan (Acer R11) instead ?
We've got both cyan (BDW) and gnawty(BYT) devices runnign in MTV. Either works.
Reef(APL) isn't quite running yet.
No, I dont have that board atm.
Liam
itsPeter
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
On Mon, Dec 11, 2017 at 10:15 AM, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com wrote:
Sounds like at least on ChromeOS side, none of you are developing on Reef related board at but on Cyan (Acer R11) instead ?
We've got both cyan (BDW) and gnawty(BYT) devices runnign in MTV. Either works.
nit-pick: I think you meant BSW.
Correct, thank you.
Reef(APL) isn't quite running yet.
participants (4)
-
Chun-ta Lin -
Dylan Reid -
Liam Girdwood -
Pierre-Louis Bossart