public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Travis B. Sawyer" <tsawyer+linuxppc@sandburst•com>
To: Matt Porter <mporter@kernel•crashing.org>
Cc: ppcembed <linuxppc-embedded@ozlabs•org>
Subject: Re: 2.6 4xx GPIO OCP driver?
Date: Fri, 25 Feb 2005 15:51:45 -0500	[thread overview]
Message-ID: <421F8FE1.6020102@sandburst.com> (raw)
In-Reply-To: <20050225133055.A28918@cox.net>

Matt Porter wrote:
> On Fri, Feb 25, 2005 at 03:25:04PM -0500, Travis B. Sawyer wrote:
> 
>>Steven Blakeslee wrote:
>>>>In 2.4 we used the drivers/char/ibm_ocp_gpio.c module.  I see 
>>>>no such support in 2.6.10.  I perused the archives, found 
>>>>nothing
>>>I see it.  Drivers/char/ibm_gpio.c in Linux 2.6.10-rc3.
>>
<SNIPPAGE above>
> I didn't bother merging it upstream at one time. It wasn't clear
> if the driver had any value over just mmaping /dev/mem to bang
> on the couple gpio registers directly.

Matt:

Good point, and that'll work for 2.4 also, which means I don't have to 
support different usercode btw the two versions of the kernel.

Thanx,

Travis

  reply	other threads:[~2005-02-25 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 19:40 2.6 4xx GPIO OCP driver? Steven Blakeslee
2005-02-25 20:25 ` Travis B. Sawyer
2005-02-25 20:30   ` Matt Porter
2005-02-25 20:51     ` Travis B. Sawyer [this message]
2005-02-25 21:19     ` Ralph Siemsen
2005-02-26  0:29       ` Matt Porter
2005-02-26 22:31         ` Travis Sawyer
2005-02-26 22:31         ` Travis B. Sawyer
  -- strict thread matches above, loose matches on Subject: below --
2005-02-25 17:17 Travis B. Sawyer

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=421F8FE1.6020102@sandburst.com \
    --to=tsawyer+linuxppc@sandburst$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=mporter@kernel$(echo .)crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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