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: Sat, 16 Jul 2005 08:42:55 -0700 [thread overview]
Message-ID: <1121528575.27121.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050716124205.GA26127@enneenne.com>
On Sat, 2005-07-16 at 14:42 +0200, Rodolfo Giometti wrote:
> Hello,
>
> switching from linux-mips 2.6.12-rc3 to 2.6.12 I notice that the
> following patch has been applied:
>
> http://www.linux-mips.org/archives/linux-mips/2005-06/msg00207.html
>
> But, on my system, recompiling the source I noticed that compilation
> stops with errors. Even downloading a clean version of source code
> from linux-mips's CVS and choosing, for instance, the board DB1100, I
> got the same result.
>
> The problem is that the above patch works well if the 64-bit physical
> address space support is disabled, but, if enabled, it breaks
> compilation stage.
I fixed this is the latest tree a couple of days ago.
Pete
> Here what I get after getting source form CVS and doing the commands:
>
> # make pb1100_defconfig (this board turn on CONFIG_64BIT_PHYS_ADDR option)
> # make
> ...
> include/asm-mips/mach-au1x00/ioremap.h:25: warning: static declaration of 'fixup_bigphys_addr' follows non-static declaration
> include/asm/pgtable.h:363: warning: 'fixup_bigphys_addr' declared inline after being called
> include/asm/pgtable.h:363: warning: previous declaration of 'fixup_bigphys_addr' was here
> include/asm-mips/mach-au1x00/ioremap.h: In function `fixup_bigphys_addr':
> include/asm-mips/mach-au1x00/ioremap.h:26: warning: implicit declaration of function `__fixup_bigphys_addr'
> arch/mips/au1000/common/setup.c: At top level:
> arch/mips/au1000/common/setup.c:159: error: conflicting types for '__fixup_bigphys_addr'
> include/asm-mips/mach-au1x00/ioremap.h:26: error: previous implicit declaration of '__fixup_bigphys_addr' was here
> arch/mips/au1000/common/setup.c: In function `__fixup_bigphys_addr':
> ...
>
> After a little job I implemented the attached patch
> (patch-64BIT_PHYS_ADDR) that works on my system on both settings
> (CONFIG_64BIT_PHYS_ADDR on or off).
>
> I don't know if it can resolve the above problem for others CPUs (I
> tested it on au1100) but, at least, on this processor the PCMCIA
> support now is functional. :)
>
> I also suggest to apply the second patch (patch-PCMCIA_Kconfig) who
> simply auto enable 64 bit support when choosing PCMCIA support.
>
> Ciao,
>
> Rodolfo
>
next prev parent reply other threads:[~2005-07-16 15:41 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 [this message]
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
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=1121528575.27121.3.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox