From: Tom Rini <trini@kernel.crashing.org>
To: Rod Boyce <rod_boyce@stratexnet.com>
Cc: Lokesh Kumar <kumar.lokesh@wrx-us.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: 2.6 kernel ppc tree
Date: Wed, 18 Feb 2004 12:03:17 -0700 [thread overview]
Message-ID: <20040218190317.GS16881@smtp.west.cox.net> (raw)
In-Reply-To: <A3240F62EF3C2749B1A25D3BC9548F41030A01@ExchWENZ02.wenz.global.vpn>
On Wed, Feb 18, 2004 at 02:13:21PM +1300, Rod Boyce wrote:
> Wow that was great I got a lot further once I copied the 2.5 kernel uart.c file across.
>
> I had to comment out both referances to ret_from_intercept in the head_8xx.S file I cannot see what is going on there. I then got to this:
> LD init/built-in.o
> LD .tmp_vmlinux1
> arch/ppc/kernel/built-in.o: In function `DoSyscall':
> arch/ppc/kernel/entry.S(.data+0x350): undefined reference to `sys_pciconfig_iobase'
> make: *** [.tmp_vmlinux1] Error 1
>
> I have not more time to spend on this and track down the PCI issues.
That issue in particular has been fixed in later versions. But
commenting out the ret_from_interrupt lines isn't quite enough to get
the platform booting :)
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-18 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 1:13 2.6 kernel ppc tree Rod Boyce
2004-02-18 19:03 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 19:08 Rod Boyce
2004-02-17 21:55 Rod Boyce
2004-02-17 21:30 Rod Boyce
2004-02-17 21:47 ` Mike Welliington
2004-02-17 22:19 ` Tom Rini
2004-02-18 17:53 ` Marcus Overhagen
2004-02-18 19:07 ` Dan Malek
2004-02-19 10:59 ` Marcus Overhagen
2004-02-19 17:46 ` Dan Malek
2004-02-17 21:22 Lokesh Kumar
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=20040218190317.GS16881@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=kumar.lokesh@wrx-us.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rod_boyce@stratexnet.com \
/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;
as well as URLs for NNTP newsgroup(s).