All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Soumya Desai <soumya@tejasnetworks.com>
Cc: gopi@tejasnetworks.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Accessing file from drivers (fwd)
Date: Fri, 16 Mar 2001 16:06:12 +0100	[thread overview]
Message-ID: <20010316150617.953CB281DB@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 16 Mar 2001 11:02:46 +0530." <3AB1A57E.669B3166@tejasnetworks.com>


Dear Soumya,

in message <3AB1A57E.669B3166@tejasnetworks.com> you wrote:
>
>      The exact problem that we're trying to solve, is to program an FPGA with a hex file
> which is in our file system.  But the problem is general is to have a way to write  a

I thought it was something like that. The conventional way  to  solve
this  is  implementing  an  ioctl() call for this function, and use a
user-space program to select the file and feed it into the driver.

> system  call  say 'sys_copy'  which will copy one file to another.  An user-mode
> application would read from one file and write back to another, which would result in
> copying  the data from the file driver ( kernel space ) to the user-space,  and again
> back to the kernel space.  We were curious as to whether a way existed by which we can
> do the read and write, sitting in the kernel space itself.  Of course adding our own

Why do you want to do that? Is this such atime-critical operation? Of
course it's possible to implement such a function, but I'm  not  sure
if it really makes sense.

> ioctl to the drivers will serve the purpose,  but we were looking for some way in which
> we would NOT need to modify the existing file system drivers.  I was wondering if it

Ummm... I don't understand this sentence. Adding an ioctl() for  YOUR
OWN  driver  to  accept  a  buffer with FPGA image date and load that
image into the FLGA does not mean you have to modify  anything  else.
You just have to write a small user application which opens the file,
reads or mmap()s it, and calls that ioctl().

> would be possible to bypass the read/write call themselves, but hack our way into the
> buffer caches of block drivers, to do this ?   Anyone tried something similar ?

Possible? Sure it's possible. But there is some effort involved,  and
your  resulting  solution  is  probably very restricted to a specific
setup. What do you want to save that you are willing to  pay  such  a
price for?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I have the simplest tastes.  I am always satisfied with the best.
                                                       -- Oscar Wilde

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

      parent reply	other threads:[~2001-03-16 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0103160943270.9927-100000@localhost.localdomain>
2001-03-16  5:32 ` Accessing file from drivers (fwd) Soumya Desai
2001-03-16  8:28   ` Stefano Coluccini
2001-03-16 15:06   ` Wolfgang Denk [this message]

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=20010316150617.953CB281DB@denx.denx.de \
    --to=wd@denx.de \
    --cc=gopi@tejasnetworks.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=soumya@tejasnetworks.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.