From: IHOLLO <ihollo@tom.com>
To: Yoichi Yuasa <yyuasa@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: ADM5120: MIPS-I or MIPS32? WAS(Re: ADM5120: linux-2.4.31-adm.diff.bz2 does not support PCI bus?)
Date: Wed, 13 Jul 2005 17:35:15 +0800 [thread overview]
Message-ID: <42D4E053.6020708@tom.com> (raw)
In-Reply-To: <4955666b05071223405849abf6@mail.gmail.com>
Thanks Yoichi, that is exactly what you suggested, turn on New PCI bus
code(CONFIG_PCI_NEW) then the kernel can be compiled now.
Here is another question: What CPU type should I choose to compile
applications for ADM5120? the spec says it is MIPS32, but I can not run
MIPS32 applications on my board while MIPS-I executable works just fine.
#file busybox (works fine. compiled as mips-I)
busybox: ELF 32-bit LSB MIPS-I executable, MIPS, version 1 (SYSV),
dynamically linked (uses shared libs), stripped
#file busybox (can not execute this program. compiled as mips32)
busybox: ELF 32-bit LSB executable, MIPS, version 1 (SYSV), dynamically
linked (uses shared libs), stripped
Yoichi Yuasa wrote:
>Hi,
>
>2005/7/13, IHOLLO <ihollo@tom.com>:
>
>
>>Hi,
>>
>>I am now working on a board with ADM5120 processor and want a kernel
>>newer than 2.4.18, so I tried the linux-2.4.31-adm.diff.bz2 patch
>>against vanilla 2.4.31 (http://www.linux-mips.org/wiki/ADMtek#Linux_2.4)
>>but failed to compile it with PCI Bus support (It compiles OK without
>>CONFIG_PCI). The compile error looks like this:
>>
>>
>
>Did you turn on New PCI bus code(CONFIG_PCI_NEW)?
>
>Yoichi
>
>
>
>
>
prev parent reply other threads:[~2005-07-13 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 2:20 ADM5120: linux-2.4.31-adm.diff.bz2 does not support PCI bus? IHOLLO
2005-07-13 6:40 ` Yoichi Yuasa
2005-07-13 9:35 ` IHOLLO [this message]
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=42D4E053.6020708@tom.com \
--to=ihollo@tom.com \
--cc=linux-mips@linux-mips.org \
--cc=yyuasa@gmail.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