-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/04/18 16:03, Ward Vandewege wrote:
> On Sat, Apr 07, 2018 at 02:25:19PM +0100, Leah Rowe wrote:
>> If you've got a D16 to submit reports on, that'd also be great.
>
> I just pushed one on the D16.
>
> Thanks, Ward.
>
thanks! :)
- --
>
> There's obviously a few people on this list using the Asus boards mentioned
> which is great. The issue we need to solve is getting more people to submit
> test results so that this isn't a problem in the future.
>
> Even if I didn't use mine for something important I am unable to submit
>
Thanks for everyone who has submitted status reports and now proved that
they work.
BTW the boards devices support ASPM so you can remove the pcie_aspm=off
in your kernel command line - I like to force it on myself with
pcie_aspm=force.
On 04/06/2018 09:54 PM, David Hendricks wrote:
> On Fri,
taii...@gmx.com schrieb am Sa., 7. Apr. 2018, 14:39:
> that doesn't mean boards that people
> know are functional should be removed from coreboot just because.
>
> I highly doubt these policies happen in a vacuum.
That particular policy was created because we consider it worse
On Sat, Apr 07, 2018 at 02:25:19PM +0100, Leah Rowe wrote:
> If you've got a D16 to submit reports on, that'd also be great.
I just pushed one on the D16.
Thanks,
Ward.
--
Ward Vandewege
GPG Key: 25F774AB
Do you use free software? Donate to join the FSF and support freedom at
On Sat, Apr 7, 2018 at 2:54 AM Leah Rowe wrote:
>
>
> I'll be really upset if D8/D16, or any libreboot-supported hardware,
> is removed from coreboot.git.
>
>
>
and as David has pointed, it never is or will be. It's always there. I
don't understand your point here.
On 07.04.2018 14:37, taii...@gmx.com wrote:
> Yeah x86 is dead freedomwise but that doesn't mean boards that people
> know are functional should be removed from coreboot just because.
If people knew that those boards are functional, they would not get
removed from git master.
Sorry, lots of
Leah Rowe wrote:
> I'll be really upset if D8/D16, or any libreboot-supported hardware,
> is removed from coreboot.git.
It's straightforward for you to avoid that: Contribute board status information.
Open source only works reliably for me when I accept that I am responsible
for my own needs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Daniel
On 07/04/18 14:13, Daniel Gröber wrote:
> Anyways, I figured it out now and uploadded the status report.
>
> --Daniel
>
Thanks :)
Can you also do this on a periodic basis?
If you've got a D16 to submit reports on, that'd also be
On Fri, Apr 06, 2018 at 07:14:47PM -0700, David Hendricks wrote:
> Which wiki? For commit rights, have you tried https://www.coreboot.org/Git#
> Register_with_gerrit ? I just updated the board status wiki to hopefully make
> that step
> easier to follow.
Ah, I was looking all over "Developer
On 04/06/2018 09:06 PM, ron minnich wrote:
> On Fri, Apr 6, 2018 at 5:45 PM Thierry Laurion
> wrote:
>
>> I agree. This is wrong.
>> Kgpe-d16 and alike are the last resorts for x86 blob free hardware.
>>
>> This NEEDS to be kept maintained and upstreamed.
> I like the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/04/18 01:43, Daniel Gröber wrote:
> I'd be happy to upload a board-status report if someone can give
> me (or tell me how to get) commit rights for the appropriate repo.
> I cannot for the life of me figure out what the proper procedure
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
sorry, i emailed the wrong person. i meant to email someone else
On 06/04/18 22:14, Leah Rowe wrote:
> hi,
>
> https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html
>
> please do all relevant tests and submit a "coreboot status"
On Fri, Apr 6, 2018 at 5:43 PM, Daniel Gröber wrote:
> I'd be happy to upload a board-status report if someone can give me
> (or tell me how to get) commit rights for the appropriate repo. I
> cannot for the life of me figure out what the proper procedure for
> that is just
On Fri, Apr 6, 2018 at 3:40 PM, taii...@gmx.com wrote:
> Like I have said before these types of policies are eventually going to
> result in coreboot only having unobtainable development boards in the
> tree (that are of course not owner controlled)
>
> It simply isn't right.
>
On Fri, Apr 6, 2018 at 5:45 PM Thierry Laurion
wrote:
> I agree. This is wrong.
> Kgpe-d16 and alike are the last resorts for x86 blob free hardware.
>
> This NEEDS to be kept maintained and upstreamed.
>
>
>
I like the board too. I have one. I have no time to keep it
I'd be happy to upload a board-status report if someone can give me
(or tell me how to get) commit rights for the appropriate repo. I
cannot for the life of me figure out what the proper procedure for
that is just from the wiki.
I just recently started playing around with my KCMA-D8 and coreboot,
I agree. This is wrong.
Kgpe-d16 and alike are the last resorts for x86 blob free hardware.
This NEEDS to be kept maintained and upstreamed.
Le ven. 6 avr. 2018 18:41, taii...@gmx.com a écrit :
> Like I have said before these types of policies are eventually going to
> result
Like I have said before these types of policies are eventually going to
result in coreboot only having unobtainable development boards in the
tree (that are of course not owner controlled)
It simply isn't right.
How can one learn firmware programming when all the available boards
have hardware
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I might be able to get a report in. Need to pull a machine out of
production though to do it, so it could be a bit (have to wait for a
maintainance window).
On 04/06/2018 04:18 PM, Felipe Sanches wrote:
> isn't git commit history forever?
>
>
isn't git commit history forever?
2018-04-06 18:14 GMT-03:00 Leah Rowe :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> hi,
>
> https://mail.coreboot.org/pipermail/coreboot/2018-April/086449.html
>
> please do all relevant tests and submit a "coreboot status" report
21 matches
Mail list logo