From: Pete Popov <ppopov@embeddedalley.com>
To: Rodolfo Giometti <giometti@linux.it>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: Support for (au1100) 64-bit physical address space broken on 2.6.12?
Date: Mon, 18 Jul 2005 09:30:05 -0700 [thread overview]
Message-ID: <1121704205.4903.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20050718161949.GB28995@enneenne.com>
On Mon, 2005-07-18 at 18:19 +0200, Rodolfo Giometti wrote:
> On Sat, Jul 16, 2005 at 08:42:55AM -0700, Pete Popov wrote:
> > I fixed this is the latest tree a couple of days ago.
>
> Something is still wrong... I just downloaded the whole linux-mips
> tree from the CVS (to avoid conflics with my local reporitory) and
> after the commands:
>
> # make pb1100_defconfig
> # make
>
> I get:
>
> arch/mips/mm/ioremap.c: In function `__ioremap':
> include/asm-mips/mach-au1x00/ioremap.h:15: sorry, unimplemented: inlining failed in call to '__fixup_bigphys_addr': function body not available
> arch/mips/mm/ioremap.c:28: sorry, unimplemented: called from here
> make[1]: *** [arch/mips/mm/ioremap.o] Error 1
> make: *** [arch/mips/mm] Error 2
Oh, pb boards ... I haven't done any maintenance on the Pb boards in
2.6. AMD wasn't interested in moving them forward and I don't have time
to build and test kernels for so many boards, so I'm not sure what to do
with them. The db1500/1550 should build just fine. Take a look at the
kernel support for those boards, and it shouldn't be too hard to update
the pb1100.
Thanks,
Pete
next prev parent reply other threads:[~2005-07-18 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 12:42 Support for (au1100) 64-bit physical address space broken on 2.6.12? Rodolfo Giometti
2005-07-16 15:42 ` Pete Popov
2005-07-17 10:58 ` Rodolfo Giometti
2005-07-17 16:22 ` Pete Popov
2005-07-18 7:54 ` Rodolfo Giometti
2005-07-18 16:19 ` Rodolfo Giometti
2005-07-18 16:30 ` Pete Popov [this message]
2005-07-18 16:34 ` Maciej W. Rozycki
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=1121704205.4903.59.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=giometti@linux.it \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.