-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I think I was being a bit pessimistic / too careful here. We're close to getting the docs publicly released, but that doesn't help anyone wanting access right now, which is why I mentioned the other route. IBM's committed to getting the documentation released, they're just making sure that what they release is actually correct for the products it covers.
It might make sense to get our "working group" together over the next few weeks, by which time the documentation should be available in public form.
Are you interested in joining? :-)
On 05/03/2018 11:40 AM, ron minnich wrote:
"There is no legal issue that we are aware of with using them to develop a libre firmware solution like coreboot; IBM just doesn't want the detailed register manuals distributed verbatim online at this time."
This is worrisome. Intel docs used to be the same way in 1999, otherwise LinuxBIOS might never have happened. Then the walls were built. I've worked with IBM Power off and on for 30+ years. IBM can give, and IBM has in the past taken away, and it's caused real trouble for projects I've worked on.
I think we need a clear statement on distribution policies for Power docs. "There is no legal issue that we are aware of" is not enough. I don't want to find out in two years that this information is now locked down.
This has been my continuing problem with Power, and it's why I've focused more on RISC-V. There's just too much uncertainty from the Open Power organization. With luck you can fix it, but it needs to be fixed.
ron
On Thu, May 3, 2018 at 5:48 AM <echelon@free.fr mailto:echelon@free.fr> wrote:
+1 Same for me, I would gladly help with the port of coreboot to Talos II (even if I am not a coreboot expert, I do have some background in firmware development..), but there are 2 problems : - the time : I will be able to spend my free time on coreboot development again only after june 2018; - the monies : I have no financial resources right now to pay myself a Talos development platform (4000$ is expensive.. and also I live in Europe and I'm concerned with the shipment of a so large and fragile item from US to Europe) I will attend the coreboot conference in september and like Jonathan said, I'm really interested by a POWER9 session at this conference. Best regards, Florentin Demetrescu ----- Mail d'origine ----- De: Jonathan Neuschäfer <j.neuschaefer@gmx.net <mailto:j.neuschaefer@gmx.net>> À: Timothy Pearson <tpearson@raptorengineering.com <mailto:tpearson@raptorengineering.com>> Cc: Kyösti Mälkki <kyosti.malkki@gmail.com <mailto:kyosti.malkki@gmail.com>>, Coreboot <coreboot@coreboot.org <mailto:coreboot@coreboot.org>> Envoyé: Thu, 03 May 2018 14:06:22 +0200 (CEST) Objet: Re: [coreboot] POWER9 / Talos II coreboot support? On Thu, May 03, 2018 at 06:32:29AM -0500, Timothy Pearson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 05/03/2018 03:44 AM, Kyösti Mälkki wrote: > > On Wed, May 2, 2018 at 9:22 PM, Timothy Pearson > > <tpearson@raptorengineering.com <mailto:tpearson@raptorengineering.com>> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> We've been kicking around the idea for some time of getting a coreboot > >> port to the POWER9 Talos II systems going. We don't have the resources > >> available / free at the moment to work on this independently, but it > >> might be possible to get something going if there are other community > >> members interested in helping out. > > > > Count me in, I am getting sick and tired of x86 vendors ;) > > > > Kyösti > > Sounds great, glad to have you on board! Any other volunteers? I am interested, but I can't commit time to this at the moment. Is there going to be a POWER9 session at the Open Source Firmware Conference[1] in September? I'd be happy to attend. Jonathan Neuschäfer [1]: https://osfc.io/ -- coreboot mailing list: coreboot@coreboot.org <mailto:coreboot@coreboot.org> https://mail.coreboot.org/mailman/listinfo/coreboot
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
On Thu, May 3, 2018 at 1:20 PM Timothy Pearson < tpearson@raptorengineering.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I think I was being a bit pessimistic / too careful here. We're close to getting the docs publicly released, but that doesn't help anyone wanting access right now, which is why I mentioned the other route. IBM's committed to getting the documentation released, they're just making sure that what they release is actually correct for the products it covers.
It might make sense to get our "working group" together over the next few weeks, by which time the documentation should be available in public form.
Are you interested in joining? :-)
of course, but not until those docs are freed up.
Context: I've been trying for 2 years now to get OPAL released under dual gpl2 licensing with the current apache2 license, apache2 and gpl2 are not compatible, so we'd be in a bit of a mess should we use OPAL code in coreboot, and it would be easiest if we were able to use some of that code.
The first response from IBM was "why do you think you need coreboot?" I worked through that, and there was agreement in the end it ought to happen, said agreement reached about 2 years ago. Stuff Would Happen, I was told. After that, silence.
This is pretty much par for the course with Power. In 1990 I spent two years getting an agreement that would allow me to .... get more agreements.
So close doesn't count. Once I see the kind of docs I need to see, not requiring a clickwrap, and covering all aspects of every chip on your board, I'm in: I'll order a board. Until then, I can't really do much.
Thanks for your efforts on Power!
ron