From: "Christopher R. Johnson" <cjohnson@gcctech.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Sergey Urvanov <abs@dts.ru>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: ioperm
Date: Tue, 27 Apr 2004 14:55:33 -0400 [thread overview]
Message-ID: <408EACA5.8090005@gcctech.com> (raw)
In-Reply-To: 20040427164405.B19C9C109F@atlas.denx.de
Normally I would agree, except that he's getting link errors with
ioperm, inb and outb - he's not even running the code. As to whether
the code will work, you have an excellent point. Maybe we're both
right, so beers all around!
Wolfgang Denk wrote:
>In message <408E8346.9070202@gcctech.com> you wrote:
>
>>I've seen that also - if I remember correctly, it was an issue with the
>>toolchain. I don't use eldk however, I roll my own. Check your include
>>
>
>I bet a few beer that this is not a toolchain issue.
>
>>>I'm getting it while trying to compile for a ppc405EP based board,
>>>
>...
>
>>>#define BASEPORT 0x378
>>>
>
>That smells like x86 PC code. It cannot run on a PowerPC.
>
>
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering: Embedded and Realtime Systems, Embedded Linux
>Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
>I've got a bad feeling about this.
>
>
--
Christopher R. Johnson
Principal Software Engineer
GCC Printers
(781)276-8763
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-27 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 9:25 ioperm Sergey Urvanov
2004-04-27 15:59 ` ioperm Christopher R. Johnson
2004-04-27 16:44 ` ioperm Wolfgang Denk
2004-04-27 18:55 ` Christopher R. Johnson [this message]
2004-04-27 19:33 ` ioperm Tom Rini
2004-04-27 19:50 ` ioperm Wolfgang Denk
2004-04-28 16:04 ` ioperm Christopher R. Johnson
-- strict thread matches above, loose matches on Subject: below --
2004-04-27 9:49 ioperm Fillod Stephane
2004-04-27 7:51 ioperm Sergey Urvanov
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=408EACA5.8090005@gcctech.com \
--to=cjohnson@gcctech.com \
--cc=abs@dts.ru \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).