From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH/RFC 2.6.33-rc5 1/1] broadsheetfb: support storing
Date: Mon, 01 Feb 2010 22:09:32 +0000 [thread overview]
Message-ID: <20100201140932.26fbc1e6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1264395836-9892-1-git-send-email-jayakumar.lkml@gmail.com>
On Mon, 1 Feb 2010 18:35:08 +0800
Jaya Kumar <jayakumar.lkml@gmail.com> wrote:
> This patch adds the ability to store waveforms to broadsheetfb. It uses the
> firmware class to retrieve the waveform. The request to store the waveform
> is triggered from a driver sysfs entry called loadstore_waveform. I
> considered adding this to Documentation/ABI/testing/ but then decided against
> it. It is not something I would expect a user to ever interact with. It
> would be only useful for people doing platform bringup and other such dirty
> activities. Also, I noticed it is not (yet?) common practice to document
> sysfs entries for fbdev drivers in there. Please let me know your feedback.
>
> Thanks,
> jaya
>
> This patch adds waveform storing capability to broadsheetfb. It uses the
> firmware class to retrieve the waveform, and the request to initiate the
> waveform storing is done via a driver sysfs entry, loadstore_waveform.
Please educate me: broadsheet is a framebuffer device, is it not? What
does it mean to record a waveform into a framebuffer device? In what
way will a user observe the waveform? Is it audio? From the patch it
appears that this mysterious device has flash memory too?
Mystified!
next prev parent reply other threads:[~2010-02-01 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 5:03 [PATCH/RFC 2.6.33-rc5 1/1] broadsheetfb: add MMIO hooks Jaya Kumar
2010-02-01 10:35 ` [PATCH/RFC 2.6.33-rc5 1/1] broadsheetfb: support storing waveform Jaya Kumar
2010-02-01 22:09 ` Andrew Morton [this message]
2010-02-01 22:33 ` Jaya Kumar
2010-02-01 22:46 ` [PATCH/RFC 2.6.33-rc5 1/1] broadsheetfb: support storing Andrew Morton
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=20100201140932.26fbc1e6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev@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.