linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux C Programming <linux-c-programming@vger.kernel.org>
Subject: Re: usage of WIN_SMART
Date: Wed, 24 Nov 2004 13:10:36 +0100	[thread overview]
Message-ID: <20041124121036.GQ2067@lug-owl.de> (raw)
In-Reply-To: <1101293397.3787.34.camel@myLinux>

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

On Wed, 2004-11-24 16:19:57 +0530, Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
wrote in message <1101293397.3787.34.camel@myLinux>:
> Can someone help me with an explanation for the usage of WIN_SMART
> directive declared in hdreg.h in ioctl() function?

Just look at some users of WIN_SMART. Found these with Google:

Function ataReadSmartValues() in
http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/atacmds.c?rev=1.2

Function smart_read_values() in
http://www.linux-ide.org/smart/ide-smart.c

There are other examples, too.  Of course, you can only use code out of
these if your software is going to be available under GNU GPL ...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-24 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 10:49 usage of WIN_SMART Jagadeesh Bhaskar P
2004-11-24 12:10 ` Jan-Benedict Glaw [this message]
2004-11-25  4:27   ` Jagadeesh Bhaskar P
2004-11-25  7:08     ` Glynn Clements

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=20041124121036.GQ2067@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@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 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).