On 27/12/16 15:56, Björn Gerhart wrote:
Hi Phil,
Am 04.12.2016 um 21:02 schrieb Björn Gerhart :
Hi Phil,
I've built am updated package for EL7.3, that backports the i2c-i801 driver
from kernel-4.4.36, and includes support for the Braswell and Wildcat Point
IHC's not supported by the RHEL7
Hi Phil,
> Am 04.12.2016 um 21:02 schrieb Björn Gerhart :
>
> Hi Phil,
>
>> I've built am updated package for EL7.3, that backports the i2c-i801 driver
>> from kernel-4.4.36, and includes support for the Braswell and Wildcat Point
>> IHC's not supported by the RHEL7.3 kernel.
>>
>> The follo
Hi Phil,
> I've built am updated package for EL7.3, that backports the i2c-i801 driver
> from kernel-4.4.36, and includes support for the Braswell and Wildcat Point
> IHC's not supported by the RHEL7.3 kernel.
>
> The following package is syncing to the mirrors and should be available
> shortl
On 01/12/16 20:08, Phil Perry wrote:
On 01/12/16 14:32, Björn Gerhart wrote:
Am 27.11.2016 um 00:58 schrieb Phil Perry :
On 18/01/16 19:17, Phil Perry wrote:
On 18/01/16 08:43, Björn Gerhart wrote:
Am 16.01.2016 um 17:09 schrieb Phil Perry :
On 15/01/16 18:12, Phil Perry wrote:
On 15/
On 01/12/16 14:32, Björn Gerhart wrote:
Am 27.11.2016 um 00:58 schrieb Phil Perry :
On 18/01/16 19:17, Phil Perry wrote:
On 18/01/16 08:43, Björn Gerhart wrote:
Am 16.01.2016 um 17:09 schrieb Phil Perry :
On 15/01/16 18:12, Phil Perry wrote:
On 15/01/16 17:16, Akemi Yagi wrote:
On Fri,
> Am 27.11.2016 um 00:58 schrieb Phil Perry :
>
>> On 18/01/16 19:17, Phil Perry wrote:
>>> On 18/01/16 08:43, Björn Gerhart wrote:
>>>
> Am 16.01.2016 um 17:09 schrieb Phil Perry :
>
>> On 15/01/16 18:12, Phil Perry wrote:
>>> On 15/01/16 17:16, Akemi Yagi wrote:
>>> On Fr
On 26/11/16 23:58, Phil Perry wrote:
On 18/01/16 19:17, Phil Perry wrote:
On 18/01/16 08:43, Björn Gerhart wrote:
Am 16.01.2016 um 17:09 schrieb Phil Perry :
On 15/01/16 18:12, Phil Perry wrote:
On 15/01/16 17:16, Akemi Yagi wrote:
On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart
wrote:
H
On 18/01/16 19:17, Phil Perry wrote:
On 18/01/16 08:43, Björn Gerhart wrote:
Am 16.01.2016 um 17:09 schrieb Phil Perry :
On 15/01/16 18:12, Phil Perry wrote:
On 15/01/16 17:16, Akemi Yagi wrote:
On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
Hi folks,
afaik the el7 kernel yet doe
On 02/02/16 06:23, Björn Gerhart wrote:
>> Am 21.01.2016 um 17:27 schrieb Björn Gerhart :
>>
>>> Am 18.01.2016 um 20:17 schrieb Phil Perry :
>>>
>>> The elrepo standard where a module is backported from an upstream kernel
>>> is the use any internal module versioning if present or version 0.0 as
>>
> Am 21.01.2016 um 17:27 schrieb Björn Gerhart :
>
>> Am 18.01.2016 um 20:17 schrieb Phil Perry :
>>
>> The elrepo standard where a module is backported from an upstream kernel
>> is the use any internal module versioning if present or version 0.0 as
>> in this case if no versioning information i
On 21 January 2016 at 19:43, Björn Gerhart wrote:
>>
If you file a bug with Red Hat I'd appreciate if you could post a link
here so I may follow it. If we can get native support added to the RHEL
kernel then we can deprecate our kmod package.
>>> Ok, opened an issue on Red Hat’
>
>>> If you file a bug with Red Hat I'd appreciate if you could post a link
>>> here so I may follow it. If we can get native support added to the RHEL
>>> kernel then we can deprecate our kmod package.
>>>
>> Ok, opened an issue on Red Hat’s Bugzilla - although it’s a kind of change
>> request
On 21/01/16 16:27, Björn Gerhart wrote:
>> Am 18.01.2016 um 20:17 schrieb Phil Perry :
>>
>> The elrepo standard where a module is backported from an upstream kernel
>> is the use any internal module versioning if present or version 0.0 as
>> in this case if no versioning information is provided. T
> Am 18.01.2016 um 20:17 schrieb Phil Perry :
>
> The elrepo standard where a module is backported from an upstream kernel
> is the use any internal module versioning if present or version 0.0 as
> in this case if no versioning information is provided. Thus the version
> will never indicate the ke
On 18/01/16 08:43, Björn Gerhart wrote:
>
>> Am 16.01.2016 um 17:09 schrieb Phil Perry :
>>
>>> On 15/01/16 18:12, Phil Perry wrote:
On 15/01/16 17:16, Akemi Yagi wrote:
> On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
>
> Hi folks,
>
> afaik the el7 kernel yet doe
> Am 16.01.2016 um 17:09 schrieb Phil Perry :
>
>> On 15/01/16 18:12, Phil Perry wrote:
>>> On 15/01/16 17:16, Akemi Yagi wrote:
On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
Hi folks,
afaik the el7 kernel yet doesn't support the i2c host adapter of the
Br
On 15/01/16 18:12, Phil Perry wrote:
> On 15/01/16 17:16, Akemi Yagi wrote:
>> On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
>>
>>> Hi folks,
>>>
>>> afaik the el7 kernel yet doesn't support the i2c host adapter of the
>>> Braswell chipset by Intel. However, it's possible to simply compile
On 15/01/16 17:16, Akemi Yagi wrote:
> On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
>
>> Hi folks,
>>
>> afaik the el7 kernel yet doesn't support the i2c host adapter of the
>> Braswell chipset by Intel. However, it's possible to simply compile a newer
>> release (taken from 3.19) of the
On Fri, Jan 15, 2016 at 6:19 AM, Björn Gerhart wrote:
> Hi folks,
>
> afaik the el7 kernel yet doesn't support the i2c host adapter of the
> Braswell chipset by Intel. However, it's possible to simply compile a newer
> release (taken from 3.19) of the i2c-i801 source code against the el7
> kernel
Hi folks,
afaik the el7 kernel yet doesn't support the i2c host adapter of the Braswell
chipset by Intel. However, it's possible to simply compile a newer release
(taken from 3.19) of the i2c-i801 source code against the el7 kernel, and the
module seems to work properly.
Is anybody out there a
20 matches
Mail list logo
