All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: Mark Atwood <mra@pobox.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Module read a file?
Date: Thu, 11 Oct 2001 17:19:07 -0400	[thread overview]
Message-ID: <3BC60CCB.4F525A02@nortelnetworks.com> (raw)
In-Reply-To: <m38zehucml.fsf@flash.localdomain>

Mark Atwood wrote:
> 
> I'm modifying a PCMCIA driver module so that it can load new firmware
> into the card when it's inserted.
> 
> Rather than including the firmware inside the module's binary, I would
> much rather be able to read it out of the filesystem.
> 
> Are their any good examples of kernel code or kernel modules reading a
> file out of the filesystem that I could copy or at least look to for
> inspiration?

What about adding an ioctl() and making a userspace tool to pass the new
firmware down in a buffer?  This lets you do more complicated error-checking and
maybe some sort of validation of the firmware in userspace, saving on kernel
size.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  reply	other threads:[~2001-10-11 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 20:48 Module read a file? Mark Atwood
2001-10-11 21:19 ` Christopher Friesen [this message]
2001-10-11 21:25   ` Mark Atwood
2001-10-11 21:39     ` Christopher Friesen
2001-10-11 21:46     ` Greg KH
2001-10-12  8:12       ` Ian Stirling
2001-10-11 21:57     ` John Adams
2001-10-11 22:18     ` Alan Cox
2001-10-11 22:29       ` Mark Atwood
2001-10-12  4:43 ` T. A.

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=3BC60CCB.4F525A02@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mra@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.