linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Wade Maxfield" <wmaxfield@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: PPC beginner questions
Date: Mon, 21 Aug 2006 11:07:04 -0500	[thread overview]
Message-ID: <45a1b53e0608210907k6acec26ag94b0621273109532@mail.gmail.com> (raw)
In-Reply-To: <528646bc0608210838p4071f9eeie560fbba18ae2b3d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]

 OK.  I'm breaking my promise. :)  A couple more questions.

On 8/21/06, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> On 8/21/06, Wade Maxfield <wmaxfield@gmail.com> wrote:
> > Hi Grant,
> >
> >   Thanks!
> >
> >   in*
> >   out*
> >
> >   I'm assuming inb() outb(), inw() outw()??  I've been googling and have
> > come up short with info that makes sense. It is almost all x86 centric.
>
> in_8, in_be16, in_be32, out_8, out_be16, out_be32 for big-endian
> device registers
> in_8, in_le16, in_le32, out_8, out_le16, out_le32 for little endian
> device registers


-->Interesting.  Do these functions do 'eieio'  (Email, Internet, Electronic
Information Officer functions (southpark cartoon), err, or  Enforce In-Order
Execution of Input/Output) for me, or do I have to do that?  I'm still
confused as to that Old MacDonald function.


>
> >   We will not be porting these drivers, this is a captive box internal
> use
> > only, limited run (200 units or so), 10 to 20 year lifespan once it hits
> the
> > field.
> >
> >   So, the virtual address I get back can be used directly.  Can I cast
> to
> > short * and long * and char *?
>
> heh, yes you can; but if your writing new code why not use good
> practice from the start?  :)


--> Ok, you win.  How about ioread8() or inb() also?  Are they not coded in
PPC correctly? Or is the in_8() more modern?


>
> >    I apologize for the basic questions, but I expect this will be a
> final
> > question for quite some time.
>
> No worries; ask away!



--> is ioremap() equivalent to ioremap_nocache() on the PPC 405?


THANKS AGAIN!!!!
wade :)

Cheers,
> g.
>
>
> BTW, when on the mailing list, please use "reply to all" and put your
> comments below what you're commenting on.  This keeps the thread on
> the mailing list for others to see, and it makes it blatentely obvious
> what you're commenting on.  (just general list-etiquette)
>
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>

[-- Attachment #2: Type: text/html, Size: 3184 bytes --]

  reply	other threads:[~2006-08-21 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 13:51 PPC beginner questions Wade Maxfield
2006-08-21 14:14 ` Grant Likely
     [not found]   ` <45a1b53e0608210759p270c2f8dy694e91f409d57729@mail.gmail.com>
2006-08-21 15:38     ` Grant Likely
2006-08-21 16:07       ` Wade Maxfield [this message]
2006-08-21 16:24         ` Grant Likely
2006-08-22  8:53 ` David H. Lynch Jr.

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=45a1b53e0608210907k6acec26ag94b0621273109532@mail.gmail.com \
    --to=wmaxfield@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.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).