[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] Add support for the NanoPiNeo



On Wed, Aug 23, 2017 at 08:23:52AM +0200, Karsten Merker wrote:
> On Tue, Aug 22, 2017 at 11:11:56PM -0400, Paul Tagliamonte wrote:

> > vagrantc added support for the NanoPi in u-boot in version
> > 2016.03~rc3+dfsg1-1, and i've been playing with it since. 
> > Finally, with Linux 4.13, the NanoPi emac driver has been
> > mainlined, and it (finally!) is starting to look sensible.
> > 
> > I've got my NanoPi booted and the eth looking happy, but I've
> > not completed an install yet.  Attached is a patch to
> > generate the firmware image.  I was able to test the
> > generated image, and it booted.
> > 
> > Attached is a patch against debian-installer/installer,
> > adding the NanoPiNeo to the u-boot-image-config.
[...]
> many thanks for the patch.  I will apply it to the d-i
> repository, but I would prefer to wait until we have have
> kernel 4.13 in unstable and can change the d-i kernel ABI
> setting accordingly.  Currently we build d-i based on kernel
> 4.12 which doesn't support the H3 EMAC, so a 4.12-based netboot
> image wouldn't be usable on a "plain" NanoPi Neo (i.e. without
> adding a USB-ethernet-adaptor).

Hello,

unfortunately some issues regarding the devicetree bindings for
the H3 EMAC driver couldn't be sorted out before the final
release of kernel 4.13.  As a result, the sunxi port maintainers
and the ARM-SoC maintainer have decided to revert the
corresponding patches and work on a proper solution during the
4.14 development cycle:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fabed5ad230a5ff8320b2928ec20a52e59a9bf60

I'll keep your patch on my todo list and revisit it again once
the H3 EMAC driver is completely upstream (hopefully in kernel
4.14).

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.


Reply to: