From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jody Bruchon <jody@jodybruchon.com>
Subject: Re: /dev/eth error
Date: Sat, 4 Mar 2017 22:58:22 -0500
Message-ID: <c5ad7470-e3d2-c96b-90af-e744297f7359@jodybruchon.com>
References: <CAOv0vdnP2neaEoQ5947UAeyRf-WfmYZ5a+GWK934tPWRH+4HBA@mail.gmail.com>
 <CAOv0vdkksYn76W7oT7ao=EkjW+RWG-6QD+Q+BUgjhu=uLuqZog@mail.gmail.com>
 <CACpuWUkZyww7MEim_Nh3prN_BUOn9kf2Gpz1QjGbHu9Luza3fA@mail.gmail.com>
 <CAOv0vd=Et+PKY7no_FaXby9LZ+D0EZePiCc+swU5rx2iWwv5tw@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
In-Reply-To: <CAOv0vd=Et+PKY7no_FaXby9LZ+D0EZePiCc+swU5rx2iWwv5tw@mail.gmail.com>
Sender: linux-8086-owner@vger.kernel.org
List-ID: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: ELKS <linux-8086@vger.kernel.org>

On 2017-03-04 10:17 PM, Derek Johansen wrote:
> After pulling in all of todays changes, I see these errors again as
> described in original email.  Previously I had not enabled networking
> or the ne2k driver, and the problem was fixed when I enabled them
> during the ./build.sh script.  Now I enable them during the ./uild.sh
> script and when I start ELKS with sudo ./qemu.sh these errors are
> back.
I forgot to pull in config.h for the new ethernet init call. Fixed in 
the latest commit (commit 3e48ec5) and doesn't error out in QEMU anymore.