All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: Bruce_Leonard@selinc.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Endian problem when accessing internel regs on 8347
Date: Thu, 17 Jan 2008 13:25:43 -0500	[thread overview]
Message-ID: <478F9DA7.6060501@gmail.com> (raw)
In-Reply-To: <OF5F228537.B04EB840-ON882573D3.00628576-882573D3.0062FB1E@selinc.com>

Bruce_Leonard@selinc.com wrote:
> Ben Warren <biggerbadderben@gmail.com> wrote on 01/17/2008 07:01:10 AM:
>
>   
>> I've attached a poorly-written-yet-functional GPIO driver that I wrote a 
>>     
>
>   
>> while ago for the MPC8349 (same as what you have for all intents and 
>> purposes). It uses in_be32() and out_be32().
>>
>>     
> Ben,
>
> Thanks for the answer.  Hummmm, at first glance it looks like you're doing 
> the same thing I am.  Only difference I can see is you use get_immrbase() 
> to figure out the address to ask for and I've got it hardcoded.  Other 
> than that we're both using request_mem_region() in in/out_be32().  Yet 
> your's works for you and mine doesn't.  Well, I'll take a closer look 
> tonight and see if there's something you're doing that I missed. 
> Unfortunately, I've gotten a higher level interrupt this morning and it 
> may ba a day or so before I get back to this and can give you any 
> feedback.  Thanks again.
>
> See 'ya!
>
> Bruce
>
>   
Something else to consider is that I've never tried this beyond 2.6.19. 
Maybe things have changed since then.

Anyway, glad to help if I can.

cheers,
Ben

  reply	other threads:[~2008-01-17 18:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17  6:26 Endian problem when accessing internel regs on 8347 Bruce_Leonard
2008-01-17 15:01 ` Ben Warren
2008-01-17 18:01   ` Bruce_Leonard
2008-01-17 18:25     ` Ben Warren [this message]
2008-01-17 17:39 ` Scott Wood
2008-01-17 18:38   ` Bruce_Leonard
2008-01-17 22:18     ` Scott Wood
2008-01-21  7:21       ` Bruce_Leonard
2008-01-21 15:16         ` Ben Warren
2008-01-21 16:40         ` Scott Wood
2008-01-22  5:33           ` Bruce_Leonard

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=478F9DA7.6060501@gmail.com \
    --to=biggerbadderben@gmail.com \
    --cc=Bruce_Leonard@selinc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.