From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Eddy Petrişor" <eddy.petrisor@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Johannes Berg <johannes@sipsolutions.net>,
debian-powerpc <debian-powerpc@lists.debian.org>
Subject: Re: [snd] looking for layout-ids
Date: Sat, 27 May 2006 07:41:43 +1000 [thread overview]
Message-ID: <1148679703.8089.162.camel@localhost.localdomain> (raw)
In-Reply-To: <60381eeb0605260902p4420757ai3669aba711122014@mail.gmail.com>
On Fri, 2006-05-26 at 19:02 +0300, Eddy Petrişor wrote:
> On 5/25/06, Johannes Berg <johannes@sipsolutions.net> wrote:
> > Hey,
>
> Hi,
>
> > [1] to find your layout-id, execute the following:
> >
> > find /proc/device-tree/ -name layout-id | xargs hexdump -e '1/4 "0x%x\n"'
> >
> > If you get no output, you have no layout-id property. If you do get
>
> What are the plans for machines without layout-id, like the 5,2 model?
> Will there be any alsa/aoa support at some point?
There will be, but let's get the ones with layout-id first since
snd-powermac should work on the older ones.
Ben.
next prev parent reply other threads:[~2006-05-26 21:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 10:43 [snd] looking for layout-ids Johannes Berg
2006-05-25 12:33 ` Andreas Schwab
2006-05-25 12:37 ` Johannes Berg
[not found] ` <20060525123247.GA19308@deepthought.linux.bogus>
2006-05-25 12:41 ` Johannes Berg
[not found] ` <20060525221111.GB27181@deepthought.linux.bogus>
2006-05-25 22:24 ` Johannes Berg
[not found] ` <20060525224905.GA28647@deepthought.linux.bogus>
2006-05-25 23:02 ` Johannes Berg
2006-05-25 13:43 ` Paul Collins
2006-05-26 1:14 ` Benjamin Herrenschmidt
2006-05-26 1:17 ` Benjamin Herrenschmidt
2006-05-26 7:28 ` Johannes Berg
2006-05-26 7:59 ` Benjamin Herrenschmidt
2006-05-26 16:02 ` Eddy Petrişor
2006-05-26 21:41 ` Benjamin Herrenschmidt [this message]
2006-05-29 11:49 ` Michael Schmitz
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=1148679703.8089.162.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=eddy.petrisor@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).