linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tim Moloney <moloney@mrsl.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: Eugene Surovegin <ebs@innocent.com>, geert@linux-m68k.org
Subject: Re: Location for Linux kernel module support files
Date: Tue, 01 Oct 2002 15:06:03 -0400	[thread overview]
Message-ID: <3D99F21B.5090408@mrsl.com> (raw)
In-Reply-To: 5.1.0.14.2.20021001100707.02dbfb50@mail.attbi.com


Tim Moloney wrote:

> The file the device driver needs is an FPGA program file that
> - is data that I don't want compiled into the driver wasting space
> - will initially be specified when the driver is loaded via rc script
> - that can be reloaded by a program to customize it for a particular
>   application
>
> I know that this isn't a a typical situation and I have only seen one
> other device driver like this.  It is a 1553 driver that creates a
> /usr/lib/<module_name> directory for its configuration file.  Is there
> a better location?

Eugene Surovegin wrote:

> For similar situation (I also need to load FPGA on our custom board) I just
> coded
> a simple "char" device (e.g. /dev/fpga).
> User mode program or simple script writes into this device and
> the driver sends this data to the PLD chip.
>
> For debugging I use something like
>     # cp fpga.bin /dev/fpga
>
> With this design driver itself doesn't have any knowledge about particular
> location of
> the FPGA program.

Geert Uytterhoeven wrote:

 > So your kernel driver should create a /proc entry where the rc script
 > can write the FPGA program file to after insmod.
 >
 > If the FPGA program file is to be reloaded by the application, it can
 > just write the new data to the same /proc entry.

I do something like this now but neither of these answer *where* to put
the file that is being copied to the /proc entry.

I want to distribute a standard FPGA program file with the module and
have it loaded at system boot time.  I can create an rc script to copy
this file to the /proc entry.  I can package the module, rc script, and
FPGA file in an RPM.  I just need to determine a reasonable location for
the FPGA file (since I know where to put the module and rc script).

The custom FPGA files can be distributed with their respective
applications and can be packaged in RPMs.

Perhaps there is no good answer to this.  I thought that this situation
happened enough that people had found a reasonable location for support
files.

--
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road                             \     /
Sarasota, FL  34232                     .________\(O)/________.
(941) 377-6775 x208                        '  '  O(.)O  '  '

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

  reply	other threads:[~2002-10-01 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 17:07 Location for Linux kernel module support files Eugene Surovegin
2002-10-01 19:06 ` Tim Moloney [this message]
2002-10-02  3:25   ` Michael Heironimus
2002-10-02  7:54   ` Ethan Benson
2002-10-02  8:06   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2002-09-30 15:46 Tim Moloney
2002-10-01  0:32 ` David Gibson
2002-10-01 14:33   ` Tim Moloney
2002-10-01 16:25     ` Geert Uytterhoeven

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=3D99F21B.5090408@mrsl.com \
    --to=moloney@mrsl.com \
    --cc=ebs@innocent.com \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.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).