linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Barisa Kisku" <barisa.kisku@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: which data structure keep IO information.
Date: Wed, 30 Jan 2008 09:12:48 +0530	[thread overview]
Message-ID: <80bb1bc60801291942w7f1e3bb4g70142e78eadbce28@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

Hi,
I have to port one customised layer 2 protocol stack and  read, write system
call to access devices in linux-2.4.
At the moment  this is ported in UNIX SVR2/4 operating system.this protocol
uses some common data structure,
i.e "user" in unix srv2/4, which keeps information such as
      u_error = return errorn code
      u_base = base address for I/O
     u_count = bytes remaining for I/O
     u_arg = argument to current system call etc.

so i need to store these information in linux-2.4 implementation for
implementing read/write system calls.so what is/are
corresponding structure in linux-2.4.i went through task_struct, fs_struct,
files_struct etc., but couldn't relate it properly.

Please help me on this .

thanks and regards,
Barisa Kisku

[-- Attachment #2: Type: text/html, Size: 941 bytes --]

                 reply	other threads:[~2008-01-30  3:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=80bb1bc60801291942w7f1e3bb4g70142e78eadbce28@mail.gmail.com \
    --to=barisa.kisku@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).