mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: socfpga: ethernet problem
Date: Tue, 27 Mar 2018 12:21:38 +0300	[thread overview]
Message-ID: <20180327122138.f276a11592e3fc167218af00@gmail.com> (raw)
In-Reply-To: <73in9it77y.fsf@pengutronix.de>

On Tue, 27 Mar 2018 07:31:29 +0200
Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote:

> 
> Hi,
> 
> Antony Pavlov <antonynpavlov@gmail.com> writes:
> 
> > Hi!
> >
> > Barebox for DE0-Nano-SoC succesfully starts on Terasic DE10-Nano board
> > but there is an ethernet issue.
> >
> > After `make ARCH=arm socfpga_defconfig` I see that the CONFIG_DRIVER_NET_DESIGNWARE_SOCFPGA
> > option is disabled.
> >
> >   #
> >   # Network drivers
> >   #
> >   ...
> >   CONFIG_DRIVER_NET_DESIGNWARE=y
> >   # CONFIG_DRIVER_NET_DESIGNWARE_GENERIC is not set
> >   # CONFIG_DRIVER_NET_DESIGNWARE_SOCFPGA is not set
> >
> > after enabling CONFIG_DRIVER_NET_DESIGNWARE_SOCFPGA I see 'Could not get sysmgr-syscon node'
> > error message:
> >
> >
> 
> Patch opportunity:
> 
> DRIVER_NET_DESIGNWARE_SOCFPGA is missing a
>     select MFD_SYSCON
> 
> and the defconfig should be regenerated with the socfpga driver instead.
> 

I made changes you suggest. Now ethernet works!

Many thanks!

Now I still have some minor issues with DE10-Nano:

  * socfpga-xload-2_defconfig does not work but socfpga-xload_defconfig does;
  * 'sleep 1' longs for 5 seconds.

I suppose that DE10-Nano is somewhat differ with DE0-Nano-SoC.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-03-27  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  7:20 Antony Pavlov
2018-03-27  5:31 ` Steffen Trumtrar
2018-03-27  9:21   ` Antony Pavlov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180327122138.f276a11592e3fc167218af00@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.trumtrar@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox