public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wolfgang.grandegger@bluewin•ch>
To: Christophe.LINDHEIMER@fr•thalesgroup.com
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: Driver on Linux
Date: Fri, 27 Jun 2003 19:24:52 +0200	[thread overview]
Message-ID: <3EFC7DE4.8080402@bluewin.ch> (raw)
In-Reply-To: D96E2AFA0DF3D211B139009027454948034CBE5D@helios.gnv.tcc.thomson-csf.com


On 06/27/2003 07:10 PM Christophe.LINDHEIMER@fr•thalesgroup.com wrote:
> Hi.
>
> I am working on a PPC860.
>
> I have developped two drivers.
>
> The driver 2 needs to use functions that are in driver 1.
> driver 1 is /dev/visu.
>
> I thought I could make fd=open("/dev/visu", 0) in init of the driver 2 but I
> get ooops.

For file access within the kernel see for example:

  http://www.fenrus.demon.nl/kernel.html

> I also need to make

> I also need to make something like ioctl(fd, IO_Special... )but the function
> ioctl is unknown in the kernel.
>
> What is the right way to work when you need to do that ?

Using file access in the kernel is usually a bad thing. I think it's
easier and more straightforward to provide a small set of exported
kernel functions which the second (driver) module can use.

Hope it helps.

Wolfgang.


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

  reply	other threads:[~2003-06-27 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27 17:10 Driver on Linux Christophe.LINDHEIMER
2003-06-27 17:24 ` Wolfgang Grandegger [this message]
2003-06-30  7:00 ` Samuel Ortiz
  -- strict thread matches above, loose matches on Subject: below --
2003-06-27 17:18 Jean-Denis Boyer

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=3EFC7DE4.8080402@bluewin.ch \
    --to=wolfgang.grandegger@bluewin$(echo .)ch \
    --cc=Christophe.LINDHEIMER@fr$(echo .)thalesgroup.com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.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