From: gmane@reliableembeddedsystems.com
To: "Zubair Lutfullah :" <zubair.lutfullah@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Rob Mosher <nyt@countercultured.net>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
<robertcnelson@gmail.com>, Samuel Ortiz <sameo@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Felipe Balbi <balbi@ti.com>, <linux-iio@vger.kernel.org>,
<linux-input@vger.kernel.org>, Lee Jones <lee.jones@linaro.org>
Subject: Re: ti_am33x_adc sampling bugs
Date: Fri, 04 Apr 2014 08:41:32 -0500 [thread overview]
Message-ID: <4a1e407f0574ce0fc1f26e1d536f75b2@reliableembeddedsystems.com> (raw)
In-Reply-To: <20140401054158.GA3261@gmail.com>
Hi,
On 2014-04-01 00:42, Zubair Lutfullah : wrote:
> Sorry for taking this long to reply.
>
> The confusion here is due to vendor/mainline trees for the kernel.
>
> This discussion should have been carried out on
> https://github.com/beagleboard/kernel/issues
> instead of the kernel mailing lists.
Sorry for jumping in here.
I use a more recent kernel 3.13.x and currently try to move to 3.14.x.
The sampling seems to work, but I would like to use the generic_buffer
test [1].
The kernel used here [1] is a 3.13.6 stable plus those patches [2]
(from
Rob Nelson)
Can someone please tell me what's the status with beagle bone black and
iio (and maybe whom to talk to about it).
Regards,
Robert
[1] http://thread.gmane.org/gmane.linux.kernel.iio/11631
[2]
https://github.com/RobertBerger/meta-mainline/blob/dora-training-v3.13.x/beagle-bone-black-ml/recipes-kernel/linux/linux-yocto-custom/beagle-bone-black-ml-user-patches.scc
...do it-do it right-do it right now- Bobby Riggs
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
prev parent reply other threads:[~2014-04-04 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53379DF2.7050004@rznt.com>
[not found] ` <5337B3F4.30500@countercultured.net>
[not found] ` <CAExKytzRv4CT9zTor=-fc5Mfv+xG9uTjQP=LWosVnhEHsa9Y0A@mail.gmail.com>
2014-03-31 3:56 ` ti_am33x_adc sampling bugs Rob Mosher
2014-03-31 4:04 ` Rob Mosher
2014-03-31 8:17 ` Rob Mosher
2014-03-31 16:14 ` Jonathan Cameron
2014-03-31 16:47 ` Rob Mosher
2014-03-31 20:59 ` Jonathan Cameron
2014-03-31 21:03 ` Rob Mosher
2014-03-31 21:20 ` Jonathan Cameron
2014-04-01 5:42 ` Zubair Lutfullah :
2014-04-04 13:41 ` gmane [this message]
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=4a1e407f0574ce0fc1f26e1d536f75b2@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=nyt@countercultured.net \
--cc=robertcnelson@gmail.com \
--cc=sameo@linux.intel.com \
--cc=zubair.lutfullah@gmail.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