From: Greg Ungerer <gerg@uclinux.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [uClinux-dev] m68k compile issue with 4.0.5
Date: Wed, 17 Jun 2015 16:06:32 +1000 [thread overview]
Message-ID: <55810E68.1020508@uclinux.org> (raw)
In-Reply-To: <20150617054237.GF21686@waldemar-brodkorb.de>
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
next prev parent reply other threads:[~2015-06-17 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 20:23 m68k compile issue with 4.0.5 Waldemar Brodkorb
2015-06-16 6:24 ` Geert Uytterhoeven
2015-06-16 7:02 ` [uClinux-dev] " Greg Ungerer
2015-06-17 5:42 ` Waldemar Brodkorb
2015-06-17 6:06 ` Greg Ungerer [this message]
2015-06-18 14:13 ` Greg Ungerer
2015-06-17 5:28 ` Waldemar Brodkorb
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=55810E68.1020508@uclinux.org \
--to=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=wbx@openadk.org \
/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