linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Muaddi, Cecilia" <cecilia.muaddi@alloptic.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: access memory mapped registers
Date: Fri, 10 Jan 2003 02:12:49 +0100	[thread overview]
Message-ID: <20030110011254.76017C608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 09 Jan 2003 16:27:47 PST." <885489B3B89FB6449F93E525DF78777F064541@srvnt506.ALLOPTIC.COM>


In message <885489B3B89FB6449F93E525DF78777F064541@srvnt506.ALLOPTIC.COM> you wrote:
>
> Given that, do you know what is the convention if I need to address the GPIO
> pins in
> the 860?   I have some FPGA which require me to download the FPGA code
> and they are controlled via JTAG from my GPIO pins out of 860.  I can use
> mmap to map the ppc 860 internal memory (the quick dirty way just to see if
> works), or is there a driver already provided which will allow me to control
> the GPIO pins from user application?

There is no such driver, and there cannot be any such generic driver,
as the usage of the port pins is different for  each  board.  And  it
would  be  a  very  bad idea to allow any user to mess with important
things. You can even ruin hardware that way.

Do yourself a favour and write a device driver that does  what  needs
to be done.

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
There is nothing in this world constant but inconstancy.      - Swift

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

  reply	other threads:[~2003-01-10  1:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10  0:27 access memory mapped registers Muaddi, Cecilia
2003-01-10  1:12 ` Wolfgang Denk [this message]
2003-01-10  8:19 ` AW: " Georg Klug
     [not found] <885489B3B89FB6449F93E525DF78777F064542@srvnt506.ALLOPTIC.COM>
2003-01-10  1:20 ` Wolfgang Denk
2003-01-13 15:14 ` Kenneth Johansson
     [not found] <885489B3B89FB6449F93E525DF78777F06453E@srvnt506.ALLOPTIC.COM>
2003-01-10  0:25 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10  0:18 Kerl, John
2003-01-09 22:00 Muaddi, Cecilia
2003-01-09 23:14 ` 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=20030110011254.76017C608E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=cecilia.muaddi@alloptic.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).