From: Wolfgang Denk <wd@denx.de>
To: Fillod Stephane <stephane.fillod@thomson.net>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Cross compiling : problem linking
Date: Thu, 02 Oct 2003 23:26:40 +0200 [thread overview]
Message-ID: <20031002212645.2FC78C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 02 Oct 2003 18:34:19 +0200." <2C1BAF8F8E1DD611862B0002A5D4C3FC01BC068F@renexch3.rennes.thmulti.com>
Dear Stephane,
in message <2C1BAF8F8E1DD611862B0002A5D4C3FC01BC068F@renexch3.rennes.thmulti.com> you wrote:
>
> Wolfgang, you've got my agreement to put the following in the FAQ
> if it's not already.
AFAIK it's not.
> This code is for accessing hardware registers from *userland*.
> You need CAP_SYS_RAWIO and /dev/mem permissions.
Thanks!
Or do you want to add it yourself? All you have to do is registering
at http://www.denx.de/twiki/bin/view/TWiki/TWikiRegistration ...
Then you can edit / add to the U-Boot and Linux Guide at
http://www.denx.de/twiki/bin/view/DULG/WebHome yourself...
Hint: _anybody_ is welcome to contribute.
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
Never worry about theory as long as the machinery does what it's
supposed to do. - R. A. Heinlein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-02 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 16:34 Cross compiling : problem linking Fillod Stephane
2003-10-02 21:26 ` Wolfgang Denk [this message]
2003-10-03 8:26 ` Toni Van Remortel
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 13:09 Fillod Stephane
[not found] <1065104646.13376.8.camel@toni>
2003-10-02 15:01 ` Wolfgang Denk
2003-10-02 12:56 Toni Van Remortel
2003-10-02 13:26 ` Toni Van Remortel
2003-10-02 13:37 ` Wolfgang Denk
2003-10-02 13:35 ` Wolfgang Denk
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=20031002212645.2FC78C59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stephane.fillod@thomson.net \
/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).