Hi,
could you please drop the HWE enablement stack out of this?
HWE kernels were long provided before we started doing X/graphics
stack. And they are there to enable new/latest hardware only.
HWE kernels are needed on servers & clouds, it's not just desktop =)
Also, whilst there are still tiny
Hello,
Any change that desyncs things across architectures is active work and effort.
If i386 desktop images are produced, they will be produced exactly the
same way they were produced to date.
Spinning up point releases with or without hwe stack, was not per
architecture so far, but could be
On Tue, Feb 2, 2016 at 1:28 PM, Dimitri John Ledkov wrote:
> Hi,
>
> could you please drop the HWE enablement stack out of this?
Hmm.. Let me make it clearer and drop a lot of it.
> The cost of: testing, validation, release, and bandwidth to mirror it
> is IMHO large. And costs
> Kernel support is a separate vector. E.g. in Debian it is common to
> install 32-bit userspace with the 64-bit kernel. Thus using all the
> CPU/kernel features, access all the memory, yet have lower memory
> utilisation.
Right, but depending on what we decide it will also impact how tested
the
On Tue, Feb 2, 2016 at 6:27 AM, Jean-Baptiste Lallement
wrote:
> Hi,
>
> On 02/02/2016 08:58, Stefan Bader wrote:
>>>
>>> >My guess is that: all currently shipped hardware, with enough support
>>> >to run full Unity (7) Desktop, is amd64. Tested with amd64