From: David Henningsson <david.henningsson@canonical.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: hda-compiler, was: hda-verb, hda-analyzer, hda-emu and codecgraph
Date: Tue, 27 Jul 2010 17:33:32 +0200 [thread overview]
Message-ID: <4C4EFC4C.40707@canonical.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007271622510.4068@eeebox2.perex-int.cz>
2010-07-27 16:57, Jaroslav Kysela skrev:
> A little off topic: hda-compiler . I'm playing with an idea to have the
> hda-intel driver behaviour description (patches) in a firmware file.
There seem to be more than one thought in that area. Recently there has
been some discussion (at least on Ubuntu Developer Summit) whether the
device-tree[1] structure could be used in this area as well.
Since we would then have separate device-tree files, we could update
them independent of the kernel.
I'll go to plumbers in November, could this be something to discuss at
that conference?
[1] http://www.devicetree.org
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-07-27 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 11:31 hda-verb, hda-analyzer, hda-emu and codecgraph David Henningsson
2010-07-27 13:14 ` Takashi Iwai
2010-07-27 14:07 ` Jaroslav Kysela
2010-07-27 14:15 ` Takashi Iwai
2010-07-27 14:57 ` Jaroslav Kysela
2010-07-27 15:31 ` Takashi Iwai
2010-07-27 15:33 ` David Henningsson [this message]
2010-07-27 15:47 ` hda-compiler, was: " Takashi Iwai
2010-07-27 16:33 ` David Henningsson
2010-07-27 20:51 ` Takashi Iwai
2010-07-27 21:22 ` Jaroslav Kysela
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=4C4EFC4C.40707@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 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.