Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: ±èµæÁß <djkim@adc.co.kr>
Cc: gdb@sources.redhat.com
Subject: Re: About struct bpp_transfer_params...
Date: Fri, 08 Jun 2001 07:43:00 -0000	[thread overview]
Message-ID: <3B20E3E3.C2788841@redhat.com> (raw)
In-Reply-To: <002c01c0eff5$092f61a0$4e0366d2@adc.co.kr>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

±èµæÁß wrote:
> 
> Hi..
> 
> i'm studying a gdb parallel port source that is gdb/rdi-share/ directory..
> 
> but, i dont know about struct bpp_transfer_parms..
> and i couldn't find any infomation about that..
> so., who tell me a method? or give me a infomation about struct bpp_transfer_parms..
> 
> Have a nice day!


bpp_transfer_parms  only exists on Sun machines.  It is either under
/usr/include/sys or /usr/include/sbusdev in a header file called
bpp_io.h


Note that you can figure this things out by yourself.  If you looked at
the start of that source file you would have seen:

#ifdef sun
# include <sys/ioccom.h>
# ifdef __svr4__
#  include <sys/bpp_io.h>
# else
#  include <sbusdev/bpp_io.h>
# endif
#endif


Always remember that there is no magic.  If the compiler did not
complain about a symbol and it was not defined in that source file, so
it must have been defined in something that it included -- probably in
the header files.

Also, if you look at the lines where it is used, like:

    struct bpp_transfer_parms tp;

    /*
     * we need to set the parallel port up for BUSY handshaking,
     * and select the timeout
     */
    if (ioctl(parpfd, BPPIOC_GETPARMS, &tp) < 0)

you can determine that it is associated with the ioctl() in some way, in
particular with parallel ports ad the operation BPPIOC_GETPARMS.


Good luck with your project.


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2001-06-08  7:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Daniel>
     [not found] ` <Vogel's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <Mon,>
     [not found]         ` <01>
     [not found]           ` <Nov>
     [not found]             ` <1999>
     [not found]               ` <14:25:01>
     [not found]                 ` <+0100>
     [not found]                   ` <381D94AD.B37EC167@grafzahl.de>
1999-11-08  8:54                     ` go32-nat.c compilation problem Pierre Muller
     [not found]       ` <Fri,>
     [not found]         ` <08>
     [not found]           ` <Jun>
     [not found]             ` <2001>
     [not found]               ` <10:06:51>
     [not found]                 ` <+0300>
2001-06-07 18:27                   ` Another RFC: regex in libiberty DJ Delorie
2001-06-07 18:31                     ` Ian Lance Taylor
2001-06-07 18:33                       ` DJ Delorie
2001-06-07 18:43                         ` Ian Lance Taylor
2001-06-08  0:11                     ` Eli Zaretskii
2001-06-08  9:18                       ` Mark Mitchell
2001-06-08  9:59                       ` Zack Weinberg
2001-06-08 10:05                         ` H . J . Lu
2001-06-08 10:31                           ` Eli Zaretskii
2001-06-08 10:39                             ` H . J . Lu
2001-06-08 10:37                         ` Eli Zaretskii
2001-06-11 22:49                       ` Jim Blandy
2001-06-11 23:51                         ` Randall R Schulz
2001-06-12  6:48                         ` Jim Blandy
2001-06-08  1:15                     ` Pierre Muller
2001-06-08  1:36                       ` About struct bpp_transfer_params ±èµæÁß
2001-06-08  7:43                         ` Fernando Nasser [this message]
2001-06-09 13:34                     ` Another RFC: regex in libiberty Andrew Cagney
     [not found] <Eli>

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=3B20E3E3.C2788841@redhat.com \
    --to=fnasser@redhat.com \
    --cc=djkim@adc.co.kr \
    --cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox