[Openchrome-devel] [Bug 106298] Everex NC 1502NC P4M900

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat May 5 05:31:51 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106298

--- Comment #10 from Kevin Brace <kevinbrace at gmx.com> ---
My motivation as a developer of OpenChrome graphics stack is to ensure that the
code I am involved in developing works with the broadest lineup of VIA Chrome
graphics hardware.
I am mainly interested in making sure that the latest upstream code works with
your hardware, and while I will like to see old releases of the code to work,
there are no fixes for older releases since the latest code can supersede older
releases (i.e., If you can compile and run Version 0.3.3, Version 0.6.174 can
replace it.).
It is still not clear to me if the latest upstream code works with at least one
OS platform, and I feel like I am getting dragged into what I consider
unrelated matters such as GRUB boot process.
I have no control over components that run prior to the OS boot process.
Similarly, I have no control over how Linux distributions / xBSD package
OpenChrome (or as you pointed out, not packaging at all).
Issues that arise from how the distribution packaged OpenChrome is that
particular distribution's issue, and you will have to ask them for help.
If you have other non-bug triage topics to discuss, you will like to post it
over at openchrome-users mailing list.


(In reply to Scott from comment #9)
> The ease of switching openchrome-git <=> openchrome in Arch32, is offset by
> the relatively small community/resources. It also introduces an extra level
> of complexity with systemd - nVidia/amdgpu users need to generate an
> initramfs that has the video module. 
> 
> The notebook dual-boots Arch32/NetBSD 7.1.2.  If you're not aware, NetBSD
> provides a monolithic xorg that still uses openchrome 0.3.3 and a modular
> xorg.  Modular xf86-video-openchrome is based on the latest release and does
> not bulk build (I have not tried myself).
> 
> NetBSD 7.1.2 is running fairly well and I suspect that Debian 8/Devuan
> testing will too.
> 
> What I'm mulling over is how much effort to put into future use.  The
> wikipedia entry for Via indicates that they are actively developing cpu's
> capable of competing with AMD for the Chinese market.  Interestingly, the
> Deepin package list does not even provide an openchrome driver
> 
> "•  xserver-common 2:1.19.3-2deepin 
>   •  xserver-xorg 1:7.7+19 
>   •  xserver-xorg-core 2:1.19.3-2deepin 
>   •  xserver-xorg-input-all 1:7.7+19 
>   •  xserver-xorg-input-libinput 0.23.0-2 
>   •  xserver-xorg-input-synaptics 1.9.0-3deepin 
>   •  xserver-xorg-input-wacom 0.34.0-1 
>   •  xserver-xorg-video-all 1:7.7+19 
>   •  xserver-xorg-video-amdgpu 1.3.0-1 
>   •  xserver-xorg-video-ati 1:7.9.0-1 
>   •  xserver-xorg-video-fbdev 1:0.4.4-1+b5 
>   •  xserver-xorg-video-intel 2:2.99.917+git20161206-1+deepin 
>   •  xserver-xorg-video-nouveau 1:1.0.15-2 
>   •  xserver-xorg-video-radeon 1:7.9.0-1 
>   •  xserver-xorg-video-vesa 1:2.3.4-1+b2 
>   •  xserver-xorg-video-vmware 1:13.2.1-1+b1"
> 
> IMHO, The Deepin developers should hire you after they get the latest driver
> spec's from Via ;)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20180505/e0bdcbc2/attachment.html>


More information about the openchrome-devel mailing list