linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: cjohnson@gcctech.com
Cc: Sergey Urvanov <abs@dts.ru>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: ioperm
Date: Tue, 27 Apr 2004 21:50:53 +0200	[thread overview]
Message-ID: <20040427195058.E7E89C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 27 Apr 2004 14:55:33 EDT." <408EACA5.8090005@gcctech.com>


In message <408EACA5.8090005@gcctech.com> you wrote:
> 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!

He's on a PowerPC system. Quoting "arch/ppc/kernel/syscalls.c":

int sys_ioperm(unsigned long from, unsigned long num, int on)
{
	printk(KERN_ERR "sys_ioperm()\n");
	return -EIO;
}

Guess what?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
If you think the problem is bad now, just wait until we've solved it.
                                                        Epstein's Law

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-04-27 19:50 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     ` ioperm Christopher R. Johnson
2004-04-27 19:33       ` ioperm Tom Rini
2004-04-27 19:50       ` Wolfgang Denk [this message]
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=20040427195058.E7E89C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=abs@dts.ru \
    --cc=cjohnson@gcctech.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).