From: Jeff Baitis <baitisj@evolution.com>
To: ppopov@mvista.com
Cc: linux-mips@linux-mips.org
Subject: fixup_bigphys_addr and DBAu1500 dev board
Date: Fri, 21 Feb 2003 12:25:16 -0800 [thread overview]
Message-ID: <20030221122515.E20129@luca.pas.lab> (raw)
In-Reply-To: <20030221.112456.41627052.nemoto@toshiba-tops.co.jp>; from anemo@mba.sphere.ne.jp on Fri, Feb 21, 2003 at 11:24:56AM +0900
Gentlemen:
I've just received a DBAu1500 development board, along with a Texas Instruments
PCI1510 CardBus bridge PCI card. As such, I believe that I'm interested in
addressing the full 36 bit physical address space on the board.
I've installed the cross-compiling toolchain from
{ftp://ftp.linux-mips.org/pub/linux/mips/redhat/7.3}. mipsel-linux-gcc reports
version 2.96, mipsel-linux-ld reports 2.13.90.0.16. I have successfully built
other kernels with this toolchain for my board.
I checked out the latest linux_2_4 as of yesterday, copied the default
config for my board (cp arch/mips/defconfig-db1500), did 'make oldconfig',
and then 'make dep && make vmlinux'.
At the final linking of the kernel, here's what happened:
mipsel-linux-ld -G 0 -static -T arch/mips/ld.script arch/mips/kernel/head.o arch/mips/kernel/init_task.o init/main.o init/version.o init/do_mounts.o \
--start-group \
arch/mips/kernel/kernel.o arch/mips/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/mips/math-emu/fpu_emulator.o \
drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/pcmcia/pcmcia.o drivers/net/wireless/wireless_net.o drivers/video/video.o drivers/usb/usbdrv.o drivers/input/inputdrv.o \
net/network.o \
arch/mips/lib/lib.a /home/baitisj/au_dev/mips_linux/linux/lib/lib.a arch/mips/au1000/db1x00/db1x00.o arch/mips/au1000/common/au1000.o \
--end-group \
-o vmlinux
arch/mips/au1000/db1x00/db1x00.o(.text.init+0x160): In function `au1x00_setup':
: undefined reference to `fixup_bigphys_addr'
arch/mips/au1000/db1x00/db1x00.o(.text.init+0x164): In function `au1x00_setup':
: undefined reference to `fixup_bigphys_addr'
make: *** [vmlinux] Error 1
I took a look at arch/mips/au1000/db1x00/setup.c, and it appears that I'm
running into issues with:
#if defined(CONFIG_64BIT_PHYS_ADDR) && defined(CONFIG_CPU_AU1500)
extern phys_t (*fixup_bigphys_addr)(phys_t phys_addr, phys_t size);
#endif
I recursively grepped through my kernel source and could find no other
references to 'fixup_bigphys_addr'.
I browsed the CVS log for setup.c, resulting in the following:
Revision 1.1.2.2 / Mon Dec 16 18:00:48 2002 UTC (2 months ago) by ppopov
Branch: linux_2_4
Changes since 1.1.2.1: +30 -0 lines
Diff to previous 1.1.2.1 to branchpoint 1.1
- cleaned up dead code
- updated the Db1x pci code to patch the Pb1500
- renamed __ioremap_fixup to fixup_bigphys_addr to match a new
36 bit address patch.
Revision 1.1.2.1 / Wed Dec 11 06:12:29 2002 UTC (2 months, 1 week ago) by
ppopov
Branch: linux_2_4
Changes since 1.1: +212 -0 lines
Diff to previous 1.1
Alchemy Au1x updates:
- better config options to separate CPU and boards specific options
- Added support for the Db1x boards
- fixed usbdev compile problems
- update to Pb1500 pci code
My next move was to cvs up -D "one month ago" my kernel_2_4 source. I cleaned,
and repeated the compiling procedure above, with the same result.
I'd love to know where this mystery fixup_bigphys_addr comes from!?
Thank you all for your hard work! I look forward to contributing in any
way that I can.
Best regards,
Jeff
--
Jeffrey Baitis - Associate Software Engineer
Evolution Robotics, Inc.
130 West Union Street
Pasadena CA 91103
tel: 626.535.2776 | fax: 626.535.2777 | baitisj@evolution.com
next prev parent reply other threads:[~2003-02-21 20:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 6:05 Ramdisk image on flash Krishnakumar. R
2003-02-20 18:27 ` Pete Popov
2003-02-20 19:30 ` Tibor Polgar
2003-02-20 19:41 ` Mark Salter
2003-02-20 20:01 ` Tibor Polgar
2003-02-20 20:16 ` Mark Salter
2003-02-20 20:35 ` Dan Malek
2003-02-20 20:44 ` Jun Sun
2003-02-20 20:57 ` Pete Popov
2003-02-20 21:24 ` Dan Malek
2003-02-20 20:37 ` Jun Sun
2003-02-20 21:08 ` Guido Guenther
2003-02-20 21:12 ` Alan Cox
2003-02-20 19:41 ` Pete Popov
2003-02-20 19:42 ` Brian Murphy
2003-02-20 20:59 ` Guido Guenther
2003-02-20 21:27 ` Dan Malek
2003-02-21 2:24 ` Atsushi Nemoto
2003-02-21 20:25 ` Jeff Baitis [this message]
2003-02-21 20:40 ` fixup_bigphys_addr and DBAu1500 dev board Dan Malek
2003-02-21 22:10 ` Pete Popov
2003-02-22 3:50 ` Jeff Baitis
2003-02-23 9:19 ` Geert Uytterhoeven
2003-02-24 17:46 ` Pete Popov
2003-02-25 21:54 ` Jeff Baitis
2003-02-25 22:05 ` Pete Popov
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=20030221122515.E20129@luca.pas.lab \
--to=baitisj@evolution.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.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