Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 30 May 2019 08:58:33 +0200
From:   =?utf-8?Q?Micha=C5=82?= Lowas-Rzechonek 
        <michal.lowas-rzechonek@silvair.com>
To:     Brian Gix <brian.gix@intel.com>
Cc:     linux-bluetooth@vger.kernel.org, inga.stotland@intel.com,
        marcel@holtmann.org, johan.hedberg@gmail.com, denkenz@gmail.com
Subject: Re: [PATCH BlueZ 0/1] mesh: Convert all crypto to ELL
Message-ID: <20190530065833.acnzga3knthhh3nk@scytale>
Mail-Followup-To: Brian Gix <brian.gix@intel.com>,
        linux-bluetooth@vger.kernel.org, inga.stotland@intel.com,
        marcel@holtmann.org, johan.hedberg@gmail.com, denkenz@gmail.com
References: <20190529172818.8844-1-brian.gix@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190529172818.8844-1-brian.gix@intel.com>
User-Agent: NeoMutt/20180716
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi,

On 05/29, Brian Gix wrote:
> This will have one major side effect in that it will no longer support
> kernels older than v4.9 (I am personally using v5.0.17).  I am told
> that (some?) Freescale platforms also will have problems regardless of
> kernel version.

Alright, so I agree that it would be up to the vendor (i.e. me ;) to
provide a patch for older kernels.

I think the most sensible option would be to patch ELL to use userspace
fallback, instead of patching bluez. So if you could just make sure that
an appropriate unit test exists within ELL, I have no objections.

-- 
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND