Re: DRM/KMS

2023-07-06 Thread Mouse
> 4. And of course, GPU is hard. [...] This is true. I know someone who works on GPU support _with_ the benefit of NDAed documentation. He says typical GPUs have documentation errata lists substantially longer than the documentation itself (as in 400 pages of doc, 900 pages of errata). That sa

Re: DRM/KMS

2023-07-06 Thread Bruno Melo
> What is frightening me now, is that the impressive amount of work needed > to make the thing "work", and only temporarily, is a work that will > be lost because the code base will continue to evolve (not to say: > dissolve...). I think here is real problem. For these you need a team, not any tea

Re: DRM/KMS

2023-07-06 Thread tlaronde
Le Fri, Jul 07, 2023 at 01:05:03AM +0900, PHO a écrit : > On 7/6/23 20:32, tlaro...@polynum.com wrote: > > So I'm proposing to go back to the fork (for this part starting by > > identifying what is immune, orthogonal to the thing) when the Linux > > DRM way was taken and to eject the Linux DRM/KMS.

Re: DRM/KMS

2023-07-06 Thread PHO
On 7/6/23 20:32, tlaro...@polynum.com wrote: > So I'm proposing to go back to the fork (for this part starting by > identifying what is immune, orthogonal to the thing) when the Linux > DRM way was taken and to eject the Linux DRM/KMS. > > If DRM has to be addressed, it will be addressed after, bu

inetd(8) bugs

2023-07-06 Thread tlaronde
You will find attached an example of a configuration exercizing bugs in the current implementation of inetd(8). Emphasize: this is the current inetd(8) not my implementation. How it works: There is the possibility to set a default host address by specifying an address with a trailing ':' and not