All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik van Asselt <e.van.asselt@planet.nl>
To: Douglas Gilbert <dgilbert@interlog.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: problems compiling scsi_ioctl on kernels later 2.4.1
Date: Sat, 17 Mar 2001 17:02:21 +0100	[thread overview]
Message-ID: <3AB38A8D.6F96086@planet.nl> (raw)
In-Reply-To: <3AB2F378.10D22DA5@interlog.com> <3AB35BE8.2E0EC8FA@planet.nl> <3AB36699.74AF1349@interlog.com>

i don't understand how it got corrupted but it looks like i'm missing a lot of things if
i compare it to your scsi_ioctl file
I will use your scsi_ioctl or i will untar kernel  2.4.2 again without patch pre4
i hope it will work

Erik


Douglas Gilbert schreef:

> Erik van Asselt wrote:
> >
> > I did link the usr/include/scsi to usr/srs/linux/include/scsi
> > isn't that the right way for compiling the new kernel?
>
> That link may be useful for running various apps but it
> is not recommended. It shouldn't make any difference to
> building a kernel.
>
> My scsi_ioctl.h file for lk 2.4.2 is attached.
>
> Doug Gilbert
>
> > Erik
> >
> > Douglas Gilbert schreef:
> >
> > > Erik,
> > > It looks like you are missing (or have a corrupted)
> > > include/scsi/scsi_ioctl.h header file. It contains
> > > the definition of the struct Scsi_Ioctl_Command .
> > >
> > > Doug Gilbert
>
>   ------------------------------------------------------------------------
> #ifndef _SCSI_IOCTL_H
> #define _SCSI_IOCTL_H
>
> #define SCSI_IOCTL_SEND_COMMAND 1
> #define SCSI_IOCTL_TEST_UNIT_READY 2
> #define SCSI_IOCTL_BENCHMARK_COMMAND 3
> #define SCSI_IOCTL_SYNC 4                       /* Request synchronous parameters */
> #define SCSI_IOCTL_START_UNIT 5
> #define SCSI_IOCTL_STOP_UNIT 6
> /* The door lock/unlock constants are compatible with Sun constants for
>    the cdrom */
> #define SCSI_IOCTL_DOORLOCK 0x5380              /* lock the eject mechanism */
> #define SCSI_IOCTL_DOORUNLOCK 0x5381            /* unlock the mechanism   */
>
> #define SCSI_REMOVAL_PREVENT    1
> #define SCSI_REMOVAL_ALLOW      0
>
> #ifdef __KERNEL__
>
> /*
>  * Structures used for scsi_ioctl et al.
>  */
>
> typedef struct scsi_ioctl_command {
>         unsigned int inlen;
>         unsigned int outlen;
>         unsigned char data[0];
> } Scsi_Ioctl_Command;
>
> typedef struct scsi_idlun {
>         __u32 dev_id;
>         __u32 host_unique_id;
> } Scsi_Idlun;
>
> /* Fibre Channel WWN, port_id struct */
> typedef struct scsi_fctargaddress
> {
>         __u32 host_port_id;
>         unsigned char host_wwn[8]; // include NULL term.
> } Scsi_FCTargAddress;
>
> extern int scsi_ioctl (Scsi_Device *dev, int cmd, void *arg);
> extern int kernel_scsi_ioctl (Scsi_Device *dev, int cmd, void *arg);
> extern int scsi_ioctl_send_command(Scsi_Device *dev,
>                                    Scsi_Ioctl_Command *arg);
>
> #endif
>
> #endif


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AB2F378.10D22DA5@interlog.com>
2001-03-17 12:43 ` problems compiling scsi_ioctl on kernels later 2.4.1 Erik van Asselt
     [not found]   ` <3AB36699.74AF1349@interlog.com>
2001-03-17 16:02     ` Erik van Asselt [this message]
2001-03-16 17:48 Erik van Asselt

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=3AB38A8D.6F96086@planet.nl \
    --to=e.van.asselt@planet.nl \
    --cc=dgilbert@interlog.com \
    --cc=linux-kernel@vger.kernel.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 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.