On 02/11/2018 02:30 PM, Philipp Rossak wrote:
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think
On 02/11/2018 02:30 PM, Philipp Rossak wrote:
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think
On 02/11/2018 02:30 PM, Philipp Rossak wrote:
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think
On 02/11/2018 02:30 PM, Philipp Rossak wrote:
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
> On 02/11/2018 01:07 AM, Philipp Rossak wrote:
> >
> >
> > On 10.02.2018 22:08, Sergey Suloev wrote:
> > > On 02/11/2018 12:01 AM, Philipp Rossak wrote:
> > > > Hey Sergey,
> > > >
> > > > Thanks for mentioning, but I think the
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
> On 02/11/2018 01:07 AM, Philipp Rossak wrote:
> >
> >
> > On 10.02.2018 22:08, Sergey Suloev wrote:
> > > On 02/11/2018 12:01 AM, Philipp Rossak wrote:
> > > > Hey Sergey,
> > > >
> > > > Thanks for mentioning, but I think the
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do
with those patches. I tested them with the v4.15.0 Kernel since this
is the
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do
with those patches. I tested them with the v4.15.0 Kernel since this
is the
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do
with those patches. I tested them with the v4.15.0 Kernel since this
is the
On 02/11/2018 01:07 AM, Philipp Rossak wrote:
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do
with those patches. I tested them with the v4.15.0 Kernel since this
is the
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the
On 10.02.2018 22:08, Sergey Suloev wrote:
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the merging window.
I tested the latest
On 02/11/2018 12:01 AM, Philipp Rossak wrote:
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the merging window.
I tested the latest
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the merging window.
I tested the latest mainline, without those patches and the kernel is
not
Hey Sergey,
Thanks for mentioning, but I think the problem has nothing to do with
those patches. I tested them with the v4.15.0 Kernel since this is the
last stable release and we are right now in the merging window.
I tested the latest mainline, without those patches and the kernel is
not
On 02/09/2018 08:52 PM, Philipp Rossak wrote:
This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
The first two patches update/improve the devicetree and the last patch adds
all missing regulators.
Regards,
Philipp
Philipp Rossak (3):
arm: dts: sun6i: a31s: bpi-m2:
On 02/09/2018 08:52 PM, Philipp Rossak wrote:
This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
The first two patches update/improve the devicetree and the last patch adds
all missing regulators.
Regards,
Philipp
Philipp Rossak (3):
arm: dts: sun6i: a31s: bpi-m2:
This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
The first two patches update/improve the devicetree and the last patch adds
all missing regulators.
Regards,
Philipp
Philipp Rossak (3):
arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes
arm: dts: sun6i: a31s:
This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
The first two patches update/improve the devicetree and the last patch adds
all missing regulators.
Regards,
Philipp
Philipp Rossak (3):
arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes
arm: dts: sun6i: a31s:
20 matches
Mail list logo