linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@teamlog.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] IBM GPIO driver for PowerPC 4xx is back from the dead
Date: Fri, 29 Sep 2006 09:42:45 -0700	[thread overview]
Message-ID: <20060929164245.GA17656@gate.ebshome.net> (raw)
In-Reply-To: <1159515965.5613.4.camel@jb-portable>

On Fri, Sep 29, 2006 at 09:46:04AM +0200, Jean-Baptiste Maneyrol wrote:
> Here is a patch for linux 2.6.18 that makes come back the old ibm gpio
> driver from 2.6.10.
> 
> It is mainly useful for compatibility with old linux 2.4 from Montavista
> I think, because direct memory access seems the new way to go.

In my opinion it should stay dead. And no, direct memory access isn't 
a way to go - how are you gonna provide synchronization in this case? 
Think about different processes mucking with GPIO registers.

I think such low-level functionality should never be exported to the 
user-space in the first place. If your user-space needs such access 
make it explicit through procfs/sysfs (e.g. 
/proc/sys/dev/my_board/reset_that_device for GPIO pin wired to some 
chip reset) or just make a specific driver for your hardware.

-- 
Eugene

  reply	other threads:[~2006-09-29 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  7:46 [PATCH] IBM GPIO driver for PowerPC 4xx is back from the dead Jean-Baptiste Maneyrol
2006-09-29 16:42 ` Eugene Surovegin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-29  8:29 Jean-Baptiste Maneyrol
2006-09-29  9:06 ` Arnd Bergmann
2006-09-29 16:46   ` Eugene Surovegin

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=20060929164245.GA17656@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=jean-baptiste.maneyrol@teamlog.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 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).