Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755100AbbFQGFr (ORCPT ); Wed, 17 Jun 2015 02:05:47 -0400 Received: from icp-osb-irony-out9.external.iinet.net.au ([203.59.1.226]:26519 "EHLO icp-osb-irony-out9.external.iinet.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751313AbbFQGFi (ORCPT ); Wed, 17 Jun 2015 02:05:38 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsgBAN8NgVWVhxBY/2dsb2JhbAANToNkX4MeqHABAQEBAQEGk3AOhXQCghoBAQEBAQGFLQEBAQMBAQIgVQEFCwsNAQoCAgUWCwICCQMCAQIBFi8GDQEHAQGIIxW2M3CWSgEBAQEBAQEBAQEBAQEBAQEBARqBIYR5hSqFBgeCaIFFBZNfhFKEK4N7QYZFC49UhDFdAQEBAYJDAQEB X-IronPort-AV: E=Sophos;i="5.13,631,1427731200"; d="scan'208";a="657692535" Message-ID: <55810E68.1020508@uclinux.org> Date: Wed, 17 Jun 2015 16:06:32 +1000 From: Greg Ungerer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Waldemar Brodkorb CC: uClinux development list , "linux-kernel@vger.kernel.org" Subject: Re: [uClinux-dev] m68k compile issue with 4.0.5 References: <20150615202357.GD11429@waldemar-brodkorb.de> <557FCA17.6000703@uclinux.org> <20150617054237.GF21686@waldemar-brodkorb.de> In-Reply-To: <20150617054237.GF21686@waldemar-brodkorb.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1794 Lines: 62 Hi Waldemar, On 17/06/15 15:42, Waldemar Brodkorb wrote: > Hi Greg, > Greg Ungerer wrote, >> >> I don't have any compile (or runtime) problems with m5208evb_defconfig >> on linux-4.0.5 either. That is close to what most people use with qemu. >> What .config are you using? > > Are you sure the defconfig creates a bootable image? Yes, on real M5208EVB hardware. That is what I ran it on. I didn't run it under QEMU. > I still need at least two patches. > > http://cgit.openadk.org/cgi/cgit/openadk.git/tree/target/m68k/qemu-m68k/patches/4.0.5/qemu-coldfire.patch > Without this one I get black screen. Better to use the fixes to QEMU instead of working around its problems in the linux kernel sources :-) This thread has the QEMU fixes: https://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg03224.html I have posted them a couple of times to the QEMU dev list, but no-one seems to pick them up. > http://cgit.openadk.org/cgi/cgit/openadk.git/tree/target/m68k/qemu-m68k/patches/4.0.5/m68k-coldfire-fec.patch > Without this one I get > qemu: hardware error: mcf_fec_read: Bad address 0x1c4 > ... > Abort Yes, you still need that. I haven't cleaned that up into a state that I am totally happy with yet. > Networking still does not work for me after booting with the two > patches applied: > fec fec.0 (unnamed net_device) (uninitialized): MDIO read timeout > fec: probe of fec.0 failed with error -5 > > Any idea? Hmm, no, haven't seen that one. I'll try a run with qemu and see if I can see what is going on. Regards Greg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/