Bug 103853

Created attachment 135679 [details]
DMR SSH public key

Let me introduce myself

hopefully all this works out just fine.. ;-)

Got Laptop with VIA P4M900 hardware / 8237A etc..

hopefully we can make this driver usable for linux kernels, as we know it was long time totally broken, and now as well on Ubuntu Studio 16.04.3 HWE when manually installed (openchrome gives me black screen on this one)

Too bad, as I think VIA has had good features at P4M900 at that point in time

As an old Amiga freak, I love hardware

(got also Atari ST, C64, ZX Spectrum etc on a waiting list for a lab gear usage)

Best,

Mario

(In reply to dubrovnikdreamcoder@gmail.com from comment #3)

Hi Mario,

Several things.

1) You will need to change this request's "Product" to "freedesktop.org" and "Component" to "New Accounts"

https://www.freedesktop.org/wiki/AccountRequests/


2) If I recall it correctly, you may have to post a useful patch before the commit privilege is granted. 
If you post a useful patch, I will commit it for you on your behalf.


3) Familiarize yourself with the OpenChrome Project status.
I have been working on this for almost two years already.

https://www.x.org/wiki/Events/XDC2017/Program/#kevin_brace

I certainly will not claim the code to be anywhere near perfect, but it is not "totally broken" either.
I have made many important fixes and several feature additions to the code (DDX) in the past two years.


4) Parallelize the development

I have been in charge of DDX's mode setting code, and have also been fixing issues with the DRM lately.
It will not make much sense to work on what I work on already, so you will like to pick something a little different than what I do.
Towards the end of the OpenChrome presentation I made in September 2017, there is TODO sort of a list, so you may want to pick something from there.
I will say that EXA (2D) acceleration with OpenChrome DRM should be something of a high priority.
3D acceleration for Chrome9 engine with Gallium3D will also be nice.
Both involve the new OpenChrome DRM still in development, so you will need to get used to compiling Linux kernel regularly.


> Got Laptop with VIA P4M900 hardware / 8237A etc..
> 
> hopefully we can make this driver usable for linux kernels, as we know it
> was long time totally broken, and now as well on Ubuntu Studio 16.04.3 HWE
> when manually installed (openchrome gives me black screen on this one)
> 
> Too bad, as I think VIA has had good features at P4M900 at that point in time
> 
> As an old Amiga freak, I love hardware
> 
> (got also Atari ST, C64, ZX Spectrum etc on a waiting list for a lab gear
> usage)
> 
> Best,
> 
> Mario

Agreed

(1,2 can do, was following the protocol mentioned at https://www.freedesktop.org/wiki/AccountRequests/  on Getting the Account..

"<!-- Requesting a New Account

What you do

    go to http://bugs.freedesktop.org
    Create a bug asking for an account. Select the Product that corresponds to the Project for which you are requesting access. If there's no product in bugzilla for the project in question, file it against the freedesktop.org product, in the New Accounts component.. --!> "


However, fine for me either way - changing it to freedesktop / new account now

4. yes parallelize would be perfect.. later, honing in on details

Cheers,

Mario

Oh I see,

sorry for "totally broken" - was not a personal reference to "you" or your work at all, just on the contrary, I am happy to see you took over a stalled and forgotten driver (which, by a natural progress of changing kernels in Linux became obsolete)

I can merely notice that, all the time at this particular P4M900 machine configuration, as of Ubuntu 9+, nothing was working out of the box, and here is an opportunity to dev/test/research on this particular hardware implementation (I have got my screwdriver/USB microscope ready for teardown as well).

Speaking of peculiarities - even some windows XP variant of drivers exhibited s3 standby resume freeze, and random GPU/OS lockup. To my experience,only One version of windows XP driver (and there were at least six versions) was rock-solid.

Win/win for all

Cheers,
Mario

Hi Dubravko,

We do not create accounts for contributors who have not contributed anything yet. Please get familiar with the project, get some patches accepted, then Kevin will have enough information to actually grant you the right to push to the official repo.

Sorry this was not clear-enough in the instructions.

Martin

Created attachment 135799 [details]
attachment-19926-0.html

Understood.

My mission statement and the rest will be clearly written with the first
set of patches for my target platforms P4M900 (and AMD RS690, if still
necessary) IGP chipsets.


Best,


On Nov 29, 2017 01:55, <bugzilla-daemon@freedesktop.org> wrote:

> Martin Peres <martin.peres@free.fr> changed bug 103853
> <https://bugs.freedesktop.org/show_bug.cgi?id=103853>
> What Removed Added
> Status NEW RESOLVED
> Resolution --- INVALID
>
> *Comment # 7 <https://bugs.freedesktop.org/show_bug.cgi?id=103853#c7> on
> bug 103853 <https://bugs.freedesktop.org/show_bug.cgi?id=103853> from
> Martin Peres <martin.peres@free.fr> *
>
> Hi Dubravko,
>
> We do not create accounts for contributors who have not contributed anything
> yet. Please get familiar with the project, get some patches accepted, then
> Kevin will have enough information to actually grant you the right to push to
> the official repo.
>
> Sorry this was not clear-enough in the instructions.
>
> Martin
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>

(In reply to dubrovnikdreamcoder@gmail.com from comment #6)

Hi Mario,

> Oh I see,
> 
> sorry for "totally broken" - was not a personal reference to "you" or your
> work at all, just on the contrary, I am happy to see you took over a stalled
> and forgotten driver (which, by a natural progress of changing kernels in
> Linux became obsolete)
> 

Since you clarified your comments, I am not offended by your comments.
I am pretty much the only developer who works on legacy hardware device driver development.


> I can merely notice that, all the time at this particular P4M900 machine
> configuration, as of Ubuntu 9+, nothing was working out of the box, and here
> is an opportunity to dev/test/research on this particular hardware
> implementation (I have got my screwdriver/USB microscope ready for teardown
> as well).
> 

I think most display detections issues that affect P4M900 / VN896 / CN896 chipset should be resolved by OpenChrome Version 0.7 that will be available in a few months.
OpenChrome Version 0.6 fixed several issues related to P4M900 / VN896 / CN896 chipset (i.e., PCIe WLAN regression that happened with Version 0.5), but it will did not support 24-bit FP interface too well.
The code to fix this is already in the upstream repository, so Version 0.7 will have it.


> Speaking of peculiarities - even some windows XP variant of drivers
> exhibited s3 standby resume freeze, and random GPU/OS lockup. To my
> experience,only One version of windows XP driver (and there were at least
> six versions) was rock-solid.
> 
> Win/win for all
> 
> Cheers,
> Mario

I cannot speak of how P4M900 chipset performs on Windows, although generally speaking, Windows graphics device drivers have to obtain WHQL logo before you can expect it to be able to sell one's silicon to Tier 1 vendors like HP, Lenovo, Dell, ASUS, etc. . . .
I assume all Windows graphics device drivers have to pass ACPI S3 State resume test in order to obtain the WHQL logo.
That being said, I will assume VIA did not really devote enough resources to graphics stack development, and this tends to affect the user experience (i.e., device driver QA issues).
Although it does not happen too often, you may not be able to rule out hardware issues.
Electrical components degrade over time, and this can be causes of your issues.
As for the hardware I own, I can get my HP 2133 mini-note (VN896 chipset) to come out of ACPI S3 State almost always on Xubuntu (for both OpenChrome DDX without DRM and OpenChrome DDX + OpenChrome DRM), and if there are any issues, it tends to be my SSD failing to get recognized after standby resume once in a while.

(In reply to dubrovnikdreamcoder@gmail.com from comment #8)
> 

Hi Mario,

> Understood.
> 
> My mission statement and the rest will be clearly written with the first
> set of patches for my target platforms P4M900 (and AMD RS690, if still
> necessary) IGP chipsets.
> 
> 
> Best,
> 
> 

You do not really need a mission statement, but you do need to pick an area you will like to work on.
Working on 2D (EXA), 3D (Gallium3D), and video acceleration are the areas I have not had the time to devote so far, so it is more available for other contributors to explore.
Of course, all of these assume the use of still in development OpenChrome DRM.
Many Linux distributions have dropped non-KMS (Kernel Mode Setting) DDX from their default (automatic) installation when you install the OS (you can still install them in many cases, but requires an additional package installation), hence, getting OpenChrome DRM mainlined inside Linux kernel tree is my No. 1 priority at this point.
The code to support EXA is in the DDX, but it is currently disabled when OpenChrome DRM is in use.
I will also like to support 3D acceleration someday, and previous developer (James Simmons) started very early work on it more than 2 years ago, but he abandoned it shortly after.

https://cgit.freedesktop.org/openchrome/mesa-openchrome/log/?qt=author&q=James+Simmons

We can take this conversation offline to openchrome-devel mailing list.
After you post one or two useful patches on the openchrome-devel mailing list, I can recommend you to obtain OpenChrome upstream repository commit privilege from an x.org administrator.
I was able to get another developer to obtain commit privilege back in 2016, so it is possible.

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

(In reply to Kevin Brace from comment #10)
> (In reply to dubrovnikdreamcoder@gmail.com from comment #8)
> > 
> 
> Hi Mario,
> 
> > Understood.
> > 
> > My mission statement and the rest will be clearly written with the first
> > set of patches for my target platforms P4M900 (and AMD RS690, if still
> > necessary) IGP chipsets.
> > 
> > 
> > Best,
> > 
> > 
> 
> You do not really need a mission statement, but you do need to pick an area
> you will like to work on.
> Working on 2D (EXA), 3D (Gallium3D), and video acceleration are the areas I
> have not had the time to devote so far, so it is more available for other
> contributors to explore.
> Of course, all of these assume the use of still in development OpenChrome
> DRM.
> Many Linux distributions have dropped non-KMS (Kernel Mode Setting) DDX from
> their default (automatic) installation when you install the OS (you can
> still install them in many cases, but requires an additional package
> installation), hence, getting OpenChrome DRM mainlined inside Linux kernel
> tree is my No. 1 priority at this point.
> The code to support EXA is in the DDX, but it is currently disabled when
> OpenChrome DRM is in use.
> I will also like to support 3D acceleration someday, and previous developer
> (James Simmons) started very early work on it more than 2 years ago, but he
> abandoned it shortly after.
> 
> https://cgit.freedesktop.org/openchrome/mesa-openchrome/log/
> ?qt=author&q=James+Simmons
> 
> We can take this conversation offline to openchrome-devel mailing list.
> After you post one or two useful patches on the openchrome-devel mailing
> list, I can recommend you to obtain OpenChrome upstream repository commit
> privilege from an x.org administrator.

Please indeed move the discussion to emails, and not to this bug report.

> I was able to get another developer to obtain commit privilege back in 2016,
> so it is possible.
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=94853

Yes, just come back here whenever Kevin tells you you are ready ;)

Created attachment 135877 [details]
attachment-3655-0.html

Awesome, thanks!

On Dec 1, 2017 15:55, <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 11 <https://bugs.freedesktop.org/show_bug.cgi?id=103853#c11> on
> bug 103853 <https://bugs.freedesktop.org/show_bug.cgi?id=103853> from
> Martin Peres <martin.peres@free.fr> *
>
> (In reply to Kevin Brace from comment #10 <https://bugs.freedesktop.org/show_bug.cgi?id=103853#c10>)> (In reply to dubrovnikdreamcoder@gmail.com from comment #8 <https://bugs.freedesktop.org/show_bug.cgi?id=103853#c8>)
> > >
> >
> > Hi Mario,
> >
> > > Understood.
> > >
> > > My mission statement and the rest will be clearly written with the first
> > > set of patches for my target platforms P4M900 (and AMD RS690, if still
> > > necessary) IGP chipsets.
> > >
> > >
> > > Best,
> > >
> > >
> >
> > You do not really need a mission statement, but you do need to pick an area
> > you will like to work on.
> > Working on 2D (EXA), 3D (Gallium3D), and video acceleration are the areas I
> > have not had the time to devote so far, so it is more available for other
> > contributors to explore.
> > Of course, all of these assume the use of still in development OpenChrome
> > DRM.
> > Many Linux distributions have dropped non-KMS (Kernel Mode Setting) DDX from
> > their default (automatic) installation when you install the OS (you can
> > still install them in many cases, but requires an additional package
> > installation), hence, getting OpenChrome DRM mainlined inside Linux kernel
> > tree is my No. 1 priority at this point.
> > The code to support EXA is in the DDX, but it is currently disabled when
> > OpenChrome DRM is in use.
> > I will also like to support 3D acceleration someday, and previous developer
> > (James Simmons) started very early work on it more than 2 years ago, but he
> > abandoned it shortly after.
> >
> > https://cgit.freedesktop.org/openchrome/mesa-openchrome/log/
> > ?qt=author&q=James+Simmons
> >
> > We can take this conversation offline to openchrome-devel mailing list.
> > After you post one or two useful patches on the openchrome-devel mailing
> > list, I can recommend you to obtain OpenChrome upstream repository commit
> > privilege from an x.org administrator.
>
> Please indeed move the discussion to emails, and not to this bug report.
> > I was able to get another developer to obtain commit privilege back in 2016,
> > so it is possible.
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=94853
>
> Yes, just come back here whenever Kevin tells you you are ready ;)
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>