Re: [coreboot] GRUB boot menu is not showing GRUB2

[Dhanasekar Jaganathan]

Hi Zoran,

Below, I have provided the details,

*[1] ls -al /boot*

[*root@ACCTON-b1-31 ~]# ls -al /boot
  *
*total 56751
  *
*dr-xr-xr-x.  4 root root 1024 May 20  2016 .
 *
*drwxr-xr-x. 19 root root 4096 Dec 25 20:00 ..
  *
*-rw-r--r--.  1 root root   131847 Dec  5  2013
config-3.11.10-301.fc20.x86_64   *
*drwxr-xr-x.  6 root root 1024 Dec 26  2009 grub2
 *
*-rw---.  1 root root 34688326 May 20  2016
initramfs-0-rescue-16fa681cc2da4g*
*-rw---.  1 root root 10081375 May 20  2016
initramfs-3.11.10-301.fc20.x86_6g*
*-rw-r--r--.  1 root root   211746 May 20  2016 initrd-plymouth.img
 *
*drwx--.  2 root root12288 May 20  2016 lost+found
  *
*-rw---.  1 root root  2686629 Dec  5  2013
System.map-3.11.10-301.fc20.x86_4*
*-rwxr-xr-x.  1 root root  5139320 May 20  2016
vmlinuz-0-rescue-16fa681cc2da40c2*
*-rwxr-xr-x.  1 root root  5139320 Dec  5  2013
vmlinuz-3.11.10-301.fc20.x86_64  *
*-rw-r--r--.  1 root root  168 Dec  5  2013
.vmlinuz-3.11.10-301.fc20.x86_64c*

*[2] What value GRUB_TIMEOUT do you see in: /boot/grub2/grub.cfg (maybe you
can try to play with this value)?*

*GRUB_TIMEOUT = 5 (set timeout = 5).*

*First I have tried GRUB_TIMEOUT = -1 and after that, I**[1] ls -al
/boot** have
changed it to  GRUB_TIMEOUT = 5. When ever I modified in /etc/default/boot,
it is getting reflected in boot/grub2/grub.cfg. *

*I am thinking that there may be problem with GRUB2 which I am using or I
may be done mistake in GRUB2 integration with coreboot. Because, GRUB2 is
not consider the values in /etc/default/boot and booting to OS directly
without displaying bootmenu. *

Please correct me, if I am wrong.

Thanks,
Dhanasekar

On Tue, Jun 6, 2017 at 10:16 PM, Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:

> Hello Dhanasekar,
>
> When you do boot into the Fedora (which one version?), could you, please,
> display for me the following:
> [1] ls -al /boot
> [2] What value *GRUB_TIMEOUT *do you see in: /boot/grub2/grub.cfg (maybe
> you can try to play with this value)?
>
> Thank you,
> Zoran
>
> On Tue, Jun 6, 2017 at 4:53 PM, Dhanasekar Jaganathan <
> jdhanasekar...@gmail.com> wrote:
>
>> Hi All,
>>
>> I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by Coreboot.
>> I am using *GRUB2 *as a Payload.
>>
>> In menuconfig, I have selected,
>>
>> Add a payload - *GRUB2*
>> GRUB2 Version - *HEAD*.
>>
>> My mSata has two fedora OS. When I boot the system, I am not seeing GRUB
>> boot load menu. System straightly booted to one of Fedora OS.
>>
>> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which
>> stops the system indefinitely at boot menu in GRUB2). Still system is not
>> stopping at boot menu.
>>
>> With other vendor BIOS on my board, I am seeing boot menu. I have
>> observed they were using GRUB 2.02_Beta version.
>>
>> So, I have checked out GRUB 2.02_Beta and complied the source which
>> produced *grub2.elf*.
>> And, I have modified Payload as * Add a Payload* = *An ELF executable
>> payload *and given the path of *grub2.elf*.
>>
>> After flashing this BIOS on my board, I am seeing error message,
>>
>> *lzma: Decodeing error = 1*
>> *Payload not loaded.*
>>
>> FYR, I have attached my *.config* file, Please view it.
>>
>> Can you please help me to solve this issue?.
>>
>> Thanks,
>> Dhanasekar
>>
>> --
>> coreboot mailing list: coreboot@coreboot.org
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>>
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] GRUB boot menu is not showing GRUB2

[Zoran Stojsavljevic]

Dhanasekar,

> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops
the system indefinitely at boot menu in GRUB2). Still system is not
stopping at boot menu.

I admit, you really managed to confuse me: should be* /etc/default/grub* !?

In addition what Marius suggested, the useful pointer:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_over_a_Serial_Console.html

It is Red Hat, thus applies to Fedora.

Please, let us know if this all helps.

Zoran

On Tue, Jun 6, 2017 at 10:49 PM, Mariusz Szafrański via coreboot <
coreboot@coreboot.org> wrote:

> Hi,
>
> I`m guessing you are on second serial port (ttyS1) on Fedora. If yes try
> reconfigure GRUB to use second serial port also.
> Mariusz
>
> W dniu 06.06.2017 o 16:53, Dhanasekar Jaganathan pisze:
>
> Hi All,
>
> I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by Coreboot. I
> am using *GRUB2 *as a Payload.
>
> In menuconfig, I have selected,
>
> Add a payload - *GRUB2*
> GRUB2 Version - *HEAD*.
>
> My mSata has two fedora OS. When I boot the system, I am not seeing GRUB
> boot load menu. System straightly booted to one of Fedora OS.
>
> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops
> the system indefinitely at boot menu in GRUB2). Still system is not
> stopping at boot menu.
>
> With other vendor BIOS on my board, I am seeing boot menu. I have observed
> they were using GRUB 2.02_Beta version.
>
> So, I have checked out GRUB 2.02_Beta and complied the source which
> produced *grub2.elf*.
> And, I have modified Payload as * Add a Payload* = *An ELF executable
> payload *and given the path of *grub2.elf*.
>
> After flashing this BIOS on my board, I am seeing error message,
>
> *lzma: Decodeing error = 1*
> *Payload not loaded.*
>
> FYR, I have attached my *.config* file, Please view it.
>
> Can you please help me to solve this issue?.
>
> Thanks,
> Dhanasekar
>
>
>
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] GRUB boot menu is not showing GRUB2

[Mariusz Szafrański via coreboot]

Hi,

I`m guessing you are on second serial port (ttyS1) on Fedora. If yes try 
reconfigure GRUB to use second serial port also.


Mariusz

W dniu 06.06.2017 o 16:53, Dhanasekar Jaganathan pisze:

Hi All,

I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by 
Coreboot. I am using *GRUB2 *as a Payload.


In menuconfig, I have selected,

Add a payload - *GRUB2*
GRUB2 Version - *HEAD*.

My mSata has two fedora OS. When I boot the system, I am not seeing 
GRUB boot load menu. System straightly booted to one of Fedora OS.


In */boot/default/grub*, I have changed*GRUB_TIMEOUT = -1* ( which 
stops the system indefinitely at boot menu in GRUB2). Still system is 
not stopping at boot menu.


With other vendor BIOS on my board, I am seeing boot menu. I have 
observed they were using GRUB 2.02_Beta version.


So, I have checked out GRUB 2.02_Beta and complied the source which 
produced *grub2.elf*.
And, I have modified Payload as * Add a Payload* = *An ELF executable 
payload *and given the path of *grub2.elf*.


After flashing this BIOS on my board, I am seeing error message,

*lzma: Decodeing error = 1*
*Payload not loaded.*

FYR, I have attached my *.config* file, Please view it.

Can you please help me to solve this issue?.

Thanks,
Dhanasekar




-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] ASUS KFSN4-DRE Automated Test Failure [master]

[Timothy Pearson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/06/2017 01:30 PM, Nico Huber wrote:
> On 06.06.2017 19:28, Raptor Engineering Automated Coreboot Test Stand wrote:
>> The ASUS KFSN4-DRE fails verification for branch master as of commit 
>> 00b9f4c4b1cd95a6cafe2b1e66641ff0f113082e
>>
>> The following tests failed:
>> BOOT_FAILURE
>>
>> Commits since last successful test:
>> 00b9f4c mb/*/*/cmos.layout: Make multibyte options byte aligned
> 
> This might be the culprit. The position of `ecc_scrub_rate` in CMOS
> changed.
> 
> If this turns out to have caused a boot failure, may I ask, why is that
> an NVRAM option? and why are values allowed that can fail to boot?
> 
> Nico

It's an NVRAM option to allow for potentially unusual use cases, such as
an archive file server where data integrity may be more important than
overall system speed.  That being said, none of the allowed values
should cause a boot failure, and a boot failure due to this particular
NVRAM setting in isolation should be considered a bug.

I wonder if there are functional sanity checks on the values read from
NVRAM for this particular option or not?

- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJZNvZTAAoJEK+E3vEXDOFboIkH/RAdXrqSBzLDghlZMGcPkZFU
UTckiucV+5s/Ajue+t67oUlpBegw7cVYhx7iKlCVqzVGlinjgkqtiOrTvgB5EtB2
6VNm3uxMdFL+MV4q47t727+qHsiJUrQ5Cxy2S4pxGZcJlV/VRrCnGx2dx+gw9I3c
0DRtFEUZtZPqxXcDKI5PE1QDPjAlYRIpT3/48wE8/4aiDbaj6vVsmlL4zfFs/lxj
mgVh960CVf4sZQNPagjbUT+6ObDUBDItsaQW3Wu4k6n6Luwu5zGVoTJ6apl9ZXLj
v7DGPMeWkzcqr2A37HZSf2w6qnpkWElZLeujC3mQfO1luizK/HgzuCZo7qjplG8=
=c4fH
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] VT-d support

[Zoran Stojsavljevic]

> `src/northbridge/intel/sandybridge/iommu.c` and acpi_fill_dmar() in
> `src/northbridge/intel/sandybridge/acpi.c`.

I'll be back!  ;-)

Zoran

On Mon, Jun 5, 2017 at 8:22 PM, Nico Huber  wrote:

> On 05.06.2017 19:47, Zoran Stojsavljevic wrote:
> >> If you are lucky, you only need to add 20~30 lines to your chipset's
> code.
> >
> > Could you, please, show us an explicit example (of these 20 to 30 lines
> of
> > code)?!
>
> `src/northbridge/intel/sandybridge/iommu.c` and acpi_fill_dmar() in
> `src/northbridge/intel/sandybridge/acpi.c`.
>
> Nico
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] ASUS KFSN4-DRE Automated Test Failure [master]

[Nico Huber]

On 06.06.2017 19:28, Raptor Engineering Automated Coreboot Test Stand wrote:
> The ASUS KFSN4-DRE fails verification for branch master as of commit 
> 00b9f4c4b1cd95a6cafe2b1e66641ff0f113082e
> 
> The following tests failed:
> BOOT_FAILURE
> 
> Commits since last successful test:
> 00b9f4c mb/*/*/cmos.layout: Make multibyte options byte aligned

This might be the culprit. The position of `ecc_scrub_rate` in CMOS
changed.

If this turns out to have caused a boot failure, may I ask, why is that
an NVRAM option? and why are values allowed that can fail to boot?

Nico

> b40e5c7 Documentation: Describe libgfxinit hook-up
> 
> See attached log for details
> 
> This message was automatically generated from Raptor Engineering's ASUS 
> KFSN4-DRE test stand
> Want to test on your own equipment?  Check out 
> https://www.raptorengineering.com/content/REACTS/intro.html
> 
> Raptor Engineering also offers coreboot consulting services!  Please visit 
> https://www.raptorengineering.com for more information
> 
> Please contact Timothy Pearson at Raptor Engineering 
>  regarding any issues stemming from this 
> notification
> 
> 
> 


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] ASUS KFSN4-DRE Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The ASUS KFSN4-DRE fails verification for branch master as of commit 
00b9f4c4b1cd95a6cafe2b1e66641ff0f113082e

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
00b9f4c mb/*/*/cmos.layout: Make multibyte options byte aligned
b40e5c7 Documentation: Describe libgfxinit hook-up

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS 
KFSN4-DRE test stand
Want to test on your own equipment?  Check out 
https://www.raptorengineering.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit 
https://www.raptorengineering.com for more information

Please contact Timothy Pearson at Raptor Engineering 
 regarding any issues stemming from this 
notification


1496770087-0-automaster.log.bz2
Description: application/bzip2
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] GRUB boot menu is not showing GRUB2

[Zoran Stojsavljevic]

Hello Dhanasekar,

When you do boot into the Fedora (which one version?), could you, please,
display for me the following:
[1] ls -al /boot
[2] What value *GRUB_TIMEOUT *do you see in: /boot/grub2/grub.cfg (maybe
you can try to play with this value)?

Thank you,
Zoran

On Tue, Jun 6, 2017 at 4:53 PM, Dhanasekar Jaganathan <
jdhanasekar...@gmail.com> wrote:

> Hi All,
>
> I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by Coreboot. I
> am using *GRUB2 *as a Payload.
>
> In menuconfig, I have selected,
>
> Add a payload - *GRUB2*
> GRUB2 Version - *HEAD*.
>
> My mSata has two fedora OS. When I boot the system, I am not seeing GRUB
> boot load menu. System straightly booted to one of Fedora OS.
>
> In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops
> the system indefinitely at boot menu in GRUB2). Still system is not
> stopping at boot menu.
>
> With other vendor BIOS on my board, I am seeing boot menu. I have observed
> they were using GRUB 2.02_Beta version.
>
> So, I have checked out GRUB 2.02_Beta and complied the source which
> produced *grub2.elf*.
> And, I have modified Payload as * Add a Payload* = *An ELF executable
> payload *and given the path of *grub2.elf*.
>
> After flashing this BIOS on my board, I am seeing error message,
>
> *lzma: Decodeing error = 1*
> *Payload not loaded.*
>
> FYR, I have attached my *.config* file, Please view it.
>
> Can you please help me to solve this issue?.
>
> Thanks,
> Dhanasekar
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] GRUB boot menu is not showing GRUB2

[Dhanasekar Jaganathan]

Hi All,

I am trying to boot *Intel Rangeley CPU/ Mohon Peak *board by Coreboot. I
am using *GRUB2 *as a Payload.

In menuconfig, I have selected,

Add a payload - *GRUB2*
GRUB2 Version - *HEAD*.

My mSata has two fedora OS. When I boot the system, I am not seeing GRUB
boot load menu. System straightly booted to one of Fedora OS.

In */boot/default/grub*, I have changed* GRUB_TIMEOUT = -1* ( which stops
the system indefinitely at boot menu in GRUB2). Still system is not
stopping at boot menu.

With other vendor BIOS on my board, I am seeing boot menu. I have observed
they were using GRUB 2.02_Beta version.

So, I have checked out GRUB 2.02_Beta and complied the source which
produced *grub2.elf*.
And, I have modified Payload as * Add a Payload* = *An ELF executable
payload *and given the path of *grub2.elf*.

After flashing this BIOS on my board, I am seeing error message,

*lzma: Decodeing error = 1*
*Payload not loaded.*

FYR, I have attached my *.config* file, Please view it.

Can you please help me to solve this issue?.

Thanks,
Dhanasekar


.config
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] DediProg EM100Pro with Apollo Lake

[Urs Ritzmann]

Hi,

> W25Q128FW, also 1.8v. What application do you use to drive em100?
> Official one from Dediprog or the open linux one? Also, what em100
> firmware# you have, perhaps yours is old?

As far as I know, I used the most recent ones:
MCU Version: 2.27
FPGA: 0.084 (1.8V)
HW Version: 5
Type: EM100PRO

I tried both, the Windows GUI (4.2.28), but also the open linux tool (master) 
and had similar issues.

Urs

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] ThinkPad X230 force battery discharge?

[Marek Behun]

Hello,
so I have found here
https://wej.k.vu/coreboot/coreboot_on_the_lenovo_thinkpad_x220/ that I
can set battery thresholds on X230 via ectool (or are the addresses
for X220 only?). Is there a way to force discharge on the battery even
when on AC adapter?
Does someone have the information about all the settings in the EC ram
on x230?

Thank you.

Marek


pgpZKmX4Avzwl.pgp
Description: OpenPGP digital signature
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] BUG : riscv register address is incorrect

[王翔]

I tried using spike to debug the coreboot code. But encountered a problem: 
**mcounteren/smcounteren** address is not correct.


The bug code is in `src/arch/riscv/virtual_memory.c`
```
313 // Enable all user/supervisor-mode counters using
314 // v1.9.1 register addresses.
315 // They moved from the earlier spec.
316 // Until we trust our toolchain use the hardcoded constants.
317 // These were in flux and people who get the older toolchain
318 // will have difficult-to-debug failures.
319 write_csr(/*mcounteren*/0x320, 7);   //this address shoud fix to 
0x306
320 write_csr(/*scounteren*/0x321, 7);//this address shoud fix to 
0x106

```
I have already submitted a patch.
https://review.coreboot.org/#/c/20043/





--



王翔

安全研究员

广州市腾御安信息科技有限公司





广州市天河区珠江新城华穗路406号保利克洛维二期中景A座1020-1024-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Current, BLOB free laptop available Europe?

[Paul Kocialkowski]

Hey,

Le lundi 05 juin 2017 à 18:20 +0300, Mike Banon a écrit :
> actually Lenovo G505S has more freedom in some relations, if compared
> to Chromebook R13 : for example, G505S does not require blobs for WiFi
> and Bluetooth if you replace its' preinstalled Broadcom half size mini
> PCI-e card with Atheros AR9462 (which has 2.4 GHz + 5 GHz + Bluetooth
> and is top-of-the-line ath9k card) and its' price is just $8-$10 with
> free shipping included ;)

Well, I don't think that Wi-Fi is really a big deal compared to having
coprocessors that can only run proprietary software, in addition to proprietary
graphics init along with a proprietary EC.

You can easily use an external ath9k_htc USB dongle on CrOS devices instead of
the internal one, which solves the Wi-Fi situation easily.

There's hope for the G505s though and I truly hope it can get close to the
current freedom status of ARM CrOS devices! (And I'm still working hard to
improve the EC situation.)

>  also there are some great technical
> opportunities which chromebooks do not have - e.g. you could replace
> WiFi mini pci-e card with double SATA ports RAID card, or you can
> install 16 GB of RAM because G505S RAM is not soldered ! Still could
> get G505S in good condition at many USA / European markets, e.g.
> yesterday at eBay I saw G505S based at USA which costs just $95, also
> UK-based in nearly mint condition ;) Also there are a lot of spare
> parts available, which helps to ensure the long lifetime of this great
> performance quad core laptop ( Chromebook is not even close at
> performance, as far as I know )

Yeah, those are definitely nice technical features (but they're not freedom-
related)! I also have a bit of a hard time with devices I can't replace broken
parts for, because they're all soldered onto the same board!

Cheers,

Paul

> On Wed, May 31, 2017 at 11:03 AM, Paul Kocialkowski  wrote:
> > Hi,
> > 
> > Le mardi 23 mai 2017 à 08:54 +0200, Paul Menzel a écrit :
> > > I am looking for a new portable device available in Europe.
> > > 
> > > Is it true, that the Acer Chromebook R 13 [1], is the only current BLOB
> > > free device? The device currently costs 400 €. Is MediaTek “a good
> > > citizen”, that means, do they provide datasheets and work on drivers?
> > 
> > The Chromebook R13 (elm) is very close to being able to boot without non-
> > free
> > blobs. The only remaining blobs are the MT8173 PCM firmwares[0] in ARM
> > Trusted
> > Firmware. I am working hard to liberate them and I'm very confident that it
> > will
> > happen pretty soon.
> > 
> > However, note that the kernel will require blobs for features such as:
> > * hardware video decoding
> > * Wi-Fi and bluetooth
> > * GPU support
> > 
> > I'm also not sure about the status of the PD (USB type-C controller) chip.
> > It
> > might also be running a proprietary firmware (maybe someone from the CrOS
> > team
> > can clarify this).
> > 
> > Also, note that as usual with laptops, there are lots of other non-free
> > components around that are preinstalled on the device, such as the webcam
> > firmware.
> > 
> > Note that ARMv7 CrOS devices (mainly RK3288 and Tegra K1) can also boot
> > blobless
> > and generally require less kernel blobs too. They also have much better
> > upstream
> > Linux support than the ARMv8 ones (which are more recent). For instance, I'm
> > running a mainline kernel on the Tegra K1 nyans, which is quite usable
> > despite
> > some issues that I have left to fix. There's also a very high chance that
> > the
> > GPU will work with nouveau and free firmwares eventually (I'll be working
> > with
> > nouveau developers to try and make this happen).
> > 
> > > The Samsung Chromebook Plus/Pro with RK3399 [2] are only available in
> > > the USA, right?
> > 
> > I am not aware of it being available in Europe. However, if you're fine with
> > a
> > qwerty layout, they work just as well in Europe ;)
> > 
> > RK3399 can currently already boot blobless but also requires kernel blobs.
> > However, it seems that the boot is currently broken with coreboot master and
> > ToT
> > depthcharge and vboot (I'll be investigating this soon).
> > 
> > Also, the Chromebook Plus (kevin) does have a free software PD firmware.
> > 
> > Finally, note that the Chromebook Pro is an Intel x86 device, so probably
> > not
> > very interesting given what you're looking for.
> > 
> > Cheers,
> > 
> > [0]: https://github.com/ARM-software/arm-trusted-firmware/blob/master/plat/m
> > ediatek/mt8173/drivers/spm/spm_mcdi.c
> > 
> > --
> > Paul Kocialkowski, developer of free digital technology and hardware support
> > 
> > Website: https://www.paulk.fr/
> > Coding blog: https://code.paulk.fr/
> > Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
> > --
> > coreboot mailing list: coreboot@coreboot.org
> > https://mail.coreboot.org/mailman/listinfo/coreboot
-- 
Paul Kocialkowski, developer of free digital technology and hardware support

Website: