From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Daniel Santos <daniel.santos@pobox.com>,
Daniel Santos <danielfsantos@att.net>,
linux-gpio <linux-gpio@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: "Virtual" Interrupts -- Need help please
Date: Mon, 9 Sep 2013 12:02:57 +0100 [thread overview]
Message-ID: <20130909110257.GU29403@sirena.org.uk> (raw)
In-Reply-To: <522D17EC.3050908@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Sun, Sep 08, 2013 at 05:35:56PM -0700, Guenter Roeck wrote:
Please fix your mailer to word wrap within paragraphs, not doing this
makes your mail very hard to read. It looks like your mailer has also
reflowed Daniel's mail.
> On 09/08/2013 04:50 PM, Daniel Santos wrote:
> >Even better, thank you very much!! If this thing had more EEPROM
> >storage I would consider using the OF format for it's settings, but I
> >only have 256 bytes to play with so I'm using a custom
> >compression/encoding.
> You should really use devicetree anyway. How you get it loaded on
> demand is another question. Lack of storage is not a reason. Custom
> data will likely not be accepted upstream, if you had that in mind.
If it's embedded into the device that shouldn't be such a problem -
especially for something on a pluggable bus that could be used with any
architecture device tree is pretty much a secondary concern. Device
tree is far from universal and the main concern where it is used is
with avoiding static board files.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-09 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 0:19 Daniel Santos
2013-09-08 0:52 ` Guenter Roeck
2013-09-08 23:50 ` Daniel Santos
2013-09-09 0:35 ` Guenter Roeck
2013-09-09 11:02 ` Mark Brown [this message]
2013-09-09 11:18 ` Alexander Holler
2013-09-09 11:45 ` Guenter Roeck
2013-09-09 12:00 ` Alexander Holler
2013-09-09 13:45 ` Mark Brown
2013-09-09 14:21 ` Alexander Holler
2013-09-09 11:06 ` Mark Brown
2013-09-09 21:12 ` Daniel Santos
2013-09-10 18:01 ` Mark Brown
2013-09-11 17:59 ` Daniel Santos
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=20130909110257.GU29403@sirena.org.uk \
--to=broonie@kernel.org \
--cc=daniel.santos@pobox.com \
--cc=danielfsantos@att.net \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sameo@linux.intel.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome