On Sat, 24 Jan 2015, Ville Syrjälä wrote:
> On Sat, Jan 24, 2015 at 12:58:19PM +0100, Daniel Vetter wrote:
>> On Fri, Jan 23, 2015 at 02:43:53PM -0800, Darren Hart wrote:
>> > +Jani
>> >
>> > Jani, I think this may have inadvertently undone the fix you made for
>> > us on the MinnowMax.
>>
>>
On Sat, Jan 24, 2015 at 12:58:19PM +0100, Daniel Vetter wrote:
> On Fri, Jan 23, 2015 at 02:43:53PM -0800, Darren Hart wrote:
> > +Jani
> >
> > Jani, I think this may have inadvertently undone the fix you made for
> > us on the MinnowMax.
>
> Do you still remember the patch? Some digging around d
On Fri, Jan 23, 2015 at 02:43:53PM -0800, Darren Hart wrote:
> +Jani
>
> Jani, I think this may have inadvertently undone the fix you made for
> us on the MinnowMax.
Do you still remember the patch? Some digging around didn't turn up
anything ...
-Daniel
>
> On Fri, Jan 23, 2015 at 1:44 PM, Olo
+Jani
Jani, I think this may have inadvertently undone the fix you made for
us on the MinnowMax.
On Fri, Jan 23, 2015 at 1:44 PM, Olof Johansson wrote:
> Hi Daniel, Mika,
>
> For the first time in a few days, -next was bootable last night. I
> noticed that my Minnowboard Max didn't actually boot
Hi Daniel, Mika,
For the first time in a few days, -next was bootable last night. I
noticed that my Minnowboard Max didn't actually boot though, it got
stuck shortly after or during DRM probing:
http://arm-soc.lixom.net/bootlogs/next/next-20150123/minnowmax-x86-minnowmax_defconfig.html
I bisecte
