[oi-dev] AMDgpu 1.1.2 and OpenChrome 0.5.159 drivers

Tue Sep 27 00:08:08 UTC 2016

Hi Martin,
Right. The sole objective proved we can compile these 'current' 2D drivers on OI-Hipster today with the existing Solaris X11 infrastructure. Getting everything else working properly requires stupendous mind-boggling mental energy and funds. Everyone has bills to pay...

~ Ken

    On Monday, September 26, 2016 2:50 PM, Мартин Бохниг <opensxce at mail.ru> wrote:

 p.s. Ken:

> We and not even Oracle cannot even port forward their China-Team created DRM/KMS module and i915 module 
> by 7 months from June 2013 level to February 2014 level for Broadwell cpu suppor

I had this plan in April.
And after 3 weeks and manually having merged 40k lines (40.000! not 40!) I came to the conclusion that it makes no sense.
Entire files disappear, others newly pop up.

The DRM's delta is meanwhile several 10 thousand lines per month, if that's enough.
Intel and AMD employ their own army of some of the most sophisticated kernel engineers and driver authors to keep that going.

Multibillion TOP500 corporations are moving hundreds of millions around.

I wish you good luck with your "second stage implementation phase".

%martin

 Понедельник, 26 сентября 2016, 21:32 UTC от Мартин Бохниг via oi-dev <oi-dev at openindiana.org>:

Now, with all respect Ken, but did you check first that on your calendar isn't April 1st?
Do you have the slightest clue what you are joking about?
This is like saying: 

A: I have a new palace as my house, huray!
Q: Wow, congrats, how did you get it?
A: Well, at this time I so far only have found the door handle on the street, but the remaining components are the next implementation phase...

And in reality this was not an exaggeragtion but still an understatement.

In case anybody ever asks you what would still be needed to get Radeon-KMS:

The Sad State Of GPU Drivers For BSD, Solaris
http://www.phoronix.com/scan.php?page=news_item&px=OTgzNA 

KMS For FreeBSD Is Still A Work In Progress
http://www.phoronix.com/scan.php?page=news_item&px=MTA1MzA 

OpenBSD Now Has AMD Radeon KMS Graphics
http://www.phoronix.com/scan.php?page=news_item&px=MTQzNjI

We and not even Oracle cannot even port forward their China-Team created DRM/KMS module and i915 module by 7 months from June 2013 level to February 2014 level for Broadwell cpu support, let alone porting in addition to that TTM memory management and radeon.
And you suggest we can have the eeeeeeeeentire world (aka TTM, Radeon, DRM/KMS, perhaps i915 also updated, then perhaps today's matching LinUX version) ?

Is it the Sun?
Did you ever have a short look at dri-devel's damounts of daily list traffic?

Then compare that to this list:

https://lists.freedesktop.org/archives/dri-devel/2016-September/date.html 

The *only* possible approach at all how a buch of hardcore-developers (*many!!!*) were able to get this done over a period of now 6 years is FreeBSD's linuxkpi.
As they say - it is easier to port a kernel to DRM/KMS, than vice versa.

I don't find the more sophisticated url but here their very humble looking small links collection:

The Graphics Stack on FreeBSD

    Links
    Graphics Stack Roadmap and Supported Hardware Matrix URL: 
https://wiki.freebsd.org/Graphics
    Ports Development Tree on GitHub URL: 
https://github.com/freebsd/freebsd-ports-graphics
    FreeBSD Graphics Team at FOSDEM 2016 URL: 
https://fosdem.org/2016/schedule/event/freebsd_graphic_stack/
    GSoC 2016: link /dev Entries to sysctl Nodes URL: 
https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_link_.2Fdev_entries_to_sysctl_nodes
    GSoC 2016: Redesign libdevq URL: 
https://wiki.freebsd.org/SummerOfCodeIdeas#Devices_management:_redesign_and_rewrite_libdevq
    Graphics Team Blog URL: http://planet.freebsd.org/graphics/

    Contact: FreeBSD Graphics team <freebsd-x11 at FreeBSD.org>

    The major news for this quarter is the update of the i915 driver in the
    kernel! The driver now matches Linux 3.8.13, so it includes initial
    Haswell support. Linux 3.8 is already three years old, but work
    continues to upgrade DRM further. In particular, work commenced to move
    to using the linuxkpi compatibility.

    In the Ports tree, Mesa was updated to 11.1.2. The next minor release,
    11.2.0, is ready for testing in our development tree. We also updated
    libclc to 0.2.0.20151006, a library used by Mesa to provide OpenCL
    support. Upstream patches were added to beignet so all these ports now
    use the same LLVM version.

    We attended FOSDEM 2016 in Brussels. Jean-Sébastien Pédron gave a talk
    to explain the work of the graphics team and show how people can
    contribute. It was well received and the presentation was followed by
    interesting discussions. FOSDEM was also a nice occasion to meet and
    talk again to the nice upstream developers of the graphics stack.

    For the first year, we added two ideas for GSoC 2016: one for a kernel
    task, one to redesign libdevq. Six students submitted proposals for
    those ideas; that was unexpected! We now need to decide which one we
    want to mentor and the choice is difficult.

    Our blog has moved to a new location (linked above).

p.s. Ken, I found this in https://lists.freebsd.org/pipermail/freebsd-current/2016-May/060964.html
MIND THE LENGTH.

We here have 0.1% as many resources compared to them.

So your message is a mystery to me.
The most funny part is that you didn't at least mention that KMS would hypothetically be needed for this.

Read your announcement:

https://openindiana.org/pipermail/oi-dev/2016-September/004869.html 

"""""Hello, We have updated and tested 32/64-bit 2D drivers for the AMDgpu 1.1.2 and Openchrome 0.5.159 
supported graphic adapters for OI-Hipster. The AMDgpu driver mainly support AMD Radeon R9 series graphic 
adapters (see: https://wiki.openindiana.org/oi/Graphics+Adapters). The OpenChrome 0.5.159 driver is a free 
and Open Source 2D video driver for the VIA/S3G UniChrome, UniChrome Pro and Chrome9 graphics chipsets: 
CLE266, KM400/KN400/KM400A/P4M800, CN400/PM800/PN800/PM880, K8M800, CN700/VM800/P4M800Pro, 
CX700, K8M890, P4M890, P4M900/VN896/CN896, VX800, VX855, VX900. We'll try to have everything included 
in the next snapshot release. Thanks, Ken"""""

You know, being optimistic versus pessimistic is certainly one thing to agree or disagree with and to discuss about.
But on the last day before defeat shouting "We soon win the war, yupee yaeh!" - Is that "optimism"?

best regards,
%martin bochnig

 Понедельник, 26 сентября 2016, 19:02 UTC от ken mays via oi-dev <oi-dev at openindiana.org>:

    Now that we are able to compile the drivers for phase 1 ... the kernel components are the next implementation phase...

I'd like to update all of the X11 2D video drivers when time permits.

~ Ken

On Monday, September 26, 2016 11:08 AM, Alexander Pyhalov <alp at rsu.ru> wrote:
> On Monday, September 26, 2016 10:37 AM, Alexander Pyhalov <alp at rsu.ru> 
> wrote:
> Hi.
> 
> 
> ken mays via oi-dev писал 26.09.2016 19:54:
>> Hello,
>> 
>> We have updated and tested 32/64-bit 2D drivers for the AMDgpu 1.1.2
>> and Openchrome 0.5.159 supported graphic adapters for OI-Hipster.
>> 
>> The AMDgpu driver mainly support AMD Radeon R9 series graphic adapters
>> (see: https://wiki.openindiana.org/oi/Graphics+Adapters).
>> 
>> The OpenChrome 0.5.159 driver is a free and Open Source 2D video
>> driver for the VIA/S3G UniChrome, UniChrome Pro and Chrome9 graphics
>> chipsets: CLE266, KM400/KN400/KM400A/P4M800, CN400/PM800/PN800/PM880,
>> K8M800, CN700/VM800/P4M800Pro, CX700, K8M890, P4M890,
>> P4M900/VN896/CN896, VX800, VX855, VX900.
>> 
> 
> Doesn't amdgpu require KMS?

ken mays писал 26.09.2016 20:47:
> Yes...

So how is it suposed to work on OI?

---
System Administrator of Southern Federal University Computer Center

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

 _______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20160927/bb15baf7/attachment-0005.html>