Hi,
On 05-11-18 12:41, Arend van Spriel wrote:
On 10/9/2018 2:47 PM, Hans de Goede wrote:
For x86 based machines, set the board_type used for nvram file selection
based on the DMI sys-vendor and product-name strings.
Since on some models these strings are too generic, this commit also adds
a
On 10/9/2018 2:47 PM, Hans de Goede wrote:
For x86 based machines, set the board_type used for nvram file selection
based on the DMI sys-vendor and product-name strings.
Since on some models these strings are too generic, this commit also adds
a quirk table overriding the strings for models
Hi,
On 10-10-18 10:15, Arend van Spriel wrote:
On 10/10/2018 9:59 AM, Hans de Goede wrote:
Any chance you could do a patch-review of this series?
Yup and test for regressions with some of the chipsets I have here.
Have you gotten around to review and testing this series yet?
it would be
On 10/10/2018 9:59 AM, Hans de Goede wrote:
Hi Arend,
On 10-10-18 09:52, Arend van Spriel wrote:
On 10/10/2018 9:28 AM, Hans de Goede wrote:
So how do you want to proceed with this, do you want me to just
put the full ISC text in the header for now as the rest of brcmfmac
does?
This is not
Hi,
On 10-10-18 09:57, Kalle Valo wrote:
Arend van Spriel writes:
On 10/10/2018 9:28 AM, Hans de Goede wrote:
So how do you want to proceed with this, do you want me to just
put the full ISC text in the header for now as the rest of brcmfmac
does?
This is not entirely true as far as I
Hi Arend,
On 10-10-18 09:52, Arend van Spriel wrote:
On 10/10/2018 9:28 AM, Hans de Goede wrote:
So how do you want to proceed with this, do you want me to just
put the full ISC text in the header for now as the rest of brcmfmac
does?
This is not entirely true as far as I know. I assume you
Arend van Spriel writes:
> On 10/10/2018 9:28 AM, Hans de Goede wrote:
>> So how do you want to proceed with this, do you want me to just
>> put the full ISC text in the header for now as the rest of brcmfmac
>> does?
>
> This is not entirely true as far as I know. I assume you are referring
>
On 10/10/2018 9:28 AM, Hans de Goede wrote:
So how do you want to proceed with this, do you want me to just
put the full ISC text in the header for now as the rest of brcmfmac
does?
This is not entirely true as far as I know. I assume you are referring
to this:
/*
* Copyright (c) 2010
Hans de Goede writes:
> Hi,
>
> On 10-10-18 09:09, Kalle Valo wrote:
>> Hans de Goede writes:
>>
>>> For x86 based machines, set the board_type used for nvram file selection
>>> based on the DMI sys-vendor and product-name strings.
>>>
>>> Since on some models these strings are too generic,
Hi,
On 10-10-18 09:09, Kalle Valo wrote:
Hans de Goede writes:
For x86 based machines, set the board_type used for nvram file selection
based on the DMI sys-vendor and product-name strings.
Since on some models these strings are too generic, this commit also adds
a quirk table overriding
Hans de Goede writes:
> For x86 based machines, set the board_type used for nvram file selection
> based on the DMI sys-vendor and product-name strings.
>
> Since on some models these strings are too generic, this commit also adds
> a quirk table overriding the strings for models listed in that
For x86 based machines, set the board_type used for nvram file selection
based on the DMI sys-vendor and product-name strings.
Since on some models these strings are too generic, this commit also adds
a quirk table overriding the strings for models listed in that table.
The board_type setting is
12 matches
Mail list logo