From: Xavier Bestel <xavier.bestel@free.fr>
To: Matt <madmatt@bits.bris.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can the kernel access /?
Date: 27 Apr 2001 17:15:03 +0200 [thread overview]
Message-ID: <988384505.4081.1.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.21.0104271521540.21006-100000@bits.bris.ac.uk>
In-Reply-To: <Pine.LNX.4.21.0104271521540.21006-100000@bits.bris.ac.uk>
Le 27 Apr 2001 15:28:04 +0100, Matt a écrit :
> I'm writing a device driver for a DSP card that requires some software
> loaded onto the card for it to function, currently I'm copying the
> software to the /dev node and the driver is doing the magic in it's
> write() handler.
>
> Can the driver pull the file from the filesystem if I were to pass the
> path of the file as an argument on loading the module?
It's generally considered a better idea to load your firmware with a
userspace app doing an ioctl or a mmap on your driver - no nasty races
to take care of, only proven codepaths used.
Xav
next prev parent reply other threads:[~2001-04-27 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 14:28 Can the kernel access /? Matt
2001-04-27 15:15 ` Xavier Bestel [this message]
2001-04-30 18:35 ` Alan Cox
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=988384505.4081.1.camel@nomade \
--to=xavier.bestel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=madmatt@bits.bris.ac.uk \
/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