On 01.07.19 23:59, Rebecca N. Palmer wrote:
Hi,
>> So, installing an opencl-based package pulls in *all* cl driver stacks ?
>
> If we do the above, yes by default, but the user can prevent this by
> explicitly installing any one.
Ok, that's fine, as long as it doesn't cause the already
On Tue, 2019-07-02 at 16:40:14 +0200, Petter Reinholdtsen wrote:
> [Guillem Jover]
> > The closest thing I'm aware of is isenkram, but re-checking it now, it
> > looks it's now tailored for hot-plugged hardware? Its README contains
> > interesting information on alternatives and similar solutions.
Thank you for the heads up, I am not following debian-devel@ these days.
Please keep me on Cc.
[Guillem Jover]
> The closest thing I'm aware of is isenkram, but re-checking it now, it
> looks it's now tailored for hot-plugged hardware? Its README contains
> interesting information on
On Tue, 2019-07-02 at 14:29 +0200, Guillem Jover wrote:
[...]
> The closest thing I'm aware of is isenkram, but re-checking it now, it
> looks it's now tailored for hot-plugged hardware? Its README contains
> interesting information on alternatives and similar solutions. CCed
> Petter for further
Hi!
On Mon, 2019-07-01 at 22:59:51 +0100, Rebecca N. Palmer wrote:
> On 01/07/2019 18:10, Enrico Weigelt, metux IT consult wrote:
> > Please don't do that. This IMHO clearly belongs into the operator's
> > hands
>
> Do you mean "not as long as it would cause the above bugs" or "not ever"?
> If
On 01/07/2019 18:10, Enrico Weigelt, metux IT consult wrote:
On 19.06.19 09:09, Rebecca N. Palmer wrote:
I proposed [0] fixing this by creating a metapackage for "all OpenCL
drivers" (similar to the ones for graphics). However, having unusable
OpenCL drivers installed can trigger bugs: [1]
6 matches
Mail list logo
