Hello Daniel,
On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof wrote:
> Hi,
>
> On Mon, 21 Aug 2017, Misha Komarovskiy wrote:
>
>> On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof
>> wrote:
>>>
>>> On Mon, 14 Aug 2017, msuchanek wrote:
>>>
On Sat,
Hi,
Am 18.11.2017 um 09:42 schrieb Alexander Graf:
> Am 17.11.2017 um 23:46 schrieb Stefan Brüns :
>> currently config.sh creates several SoC specific files ad-hoc (i.e. using
>> echo). This has several drawbacks:
>>
>> - it bloats config.sh (e.g 840 lines for the
Hi,
Am 17.11.2017 um 23:46 schrieb Stefan Brüns:
> currently config.sh creates several SoC specific files ad-hoc (i.e. using
> echo). This has several drawbacks:
>
> - it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/
> asound.state)
[snip]
Agree that this config in
Hello Guillaume,
On Sat, Nov 18, 2017 at 12:41 PM, Guillaume Gardet
wrote:
>
>
> Le 17/11/2017 à 20:55, Misha Komarovskiy a écrit :
>>
>> Hello Guillaume,
>>
>> On Fri, Nov 17, 2017 at 4:32 PM, Guillaume Gardet
>> wrote:
>>>
>>> Hi,
>>>
>>> I
Le 17/11/2017 à 20:55, Misha Komarovskiy a écrit :
Hello Guillaume,
On Fri, Nov 17, 2017 at 4:32 PM, Guillaume Gardet
wrote:
Hi,
I did not tested Chromebook for a while... and it was quite broken.
I fixed our JeOS image boot, and now, I am working on graphic
Hi Stefan,
> Am 17.11.2017 um 23:46 schrieb Stefan Brüns :
>
> Hi,
>
> currently config.sh creates several SoC specific files ad-hoc (i.e. using
> echo). This has several drawbacks:
>
> - it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/
>