All of lore.kernel.org
 help / color / mirror / Atom feed
From: "s.rawat" <imsaurabhrawat@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Regarding generic_buffer.c Application for Android
Date: Fri, 10 Apr 2015 09:48:56 +0530	[thread overview]
Message-ID: <CALwa49st7A1zSdCmy8Sq8KgAMXiGJySdpoxALTUNEubgvXqyWg@mail.gmail.com> (raw)
In-Reply-To: <5526BD63.3080509@kernel.org>

On Thu, Apr 9, 2015 at 11:26 PM, Jonathan Cameron <jic23@kernel.org> wrote:
> Not as such. However it is certainly curious that you have them missing.
> These provide direct sysfs access to the accelerations.
>
> We did at one point make it a requirement for the iio_chan_spec to explicitly include the IIO_CHAN_INFO_RAW bit
> rather than using the prior separate callbacks for that.  Perhaps it is missing in your driver?
>
> What is the actual driver in question?
The acutal driver is accel,gyro and magn.OK,i agree this is not a
mandatory requirement for the generic_buffer app to work.
The illegal termination of the application is due to the changes I
have done in the build_channel_array for function  seekdir(dp, 0).I
found that I can compile/test the app safely using arm tool chain or
gcc but when I am trying to compile the application using ndk(native
android tool chain ) I get errors for undefined references for these
functions below :
seekdir()
be16toh()
le16toh()
Are these functions portable?
and on cross-compiling with x86 tool chain for x86 32 bit platform I
get errors for missing headers unistd.h ,dirent.h,etc. I guess
unistd.h are the part of libc which may not be present in the tool
chain I am using.Is that the reason?

  reply	other threads:[~2015-04-10  4:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALwa49vRGN_VaJ147PVF8Cf+8vnBotWVh7hmxLj=jaAba5QTTw@mail.gmail.com>
2015-04-09 17:56 ` Regarding generic_buffer.c Application for Android Jonathan Cameron
2015-04-10  4:18   ` s.rawat [this message]
2015-04-10  6:19     ` Jonathan Cameron
2015-04-13  3:40       ` s.rawat
2015-04-13  6:26         ` Jonathan Cameron
2015-04-13  9:49           ` s.rawat
2015-04-13  9:51           ` s.rawat
2015-04-13 10:05           ` s.rawat
2015-04-20 10:34             ` s.rawat
2015-06-09  4:09               ` s.rawat

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=CALwa49st7A1zSdCmy8Sq8KgAMXiGJySdpoxALTUNEubgvXqyWg@mail.gmail.com \
    --to=imsaurabhrawat@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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.