From: Johannes Berg <johannes@sipsolutions.net>
To: debian-powerpc <debian-powerpc@lists.debian.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: [snd-aoa] more layout IDs
Date: Tue, 06 Jun 2006 22:19:12 +0200 [thread overview]
Message-ID: <1149625152.32002.38.camel@johannes> (raw)
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
I have tentatively added support for these layout-IDs to snd-aoa:
36 tas
47 48 onyx/topaz
49 50 onyx/topaz
56 57 onyx/topaz
62 onyx/topaz on a single bus
66 67 onyx/topaz
76 tas/topaz on a single bus
90 tas
94 onyx
96 onyx
98 toonie
100 onyx/topaz on a single bus
If you have one of those, please test :) I based the info on the
Info.plist from Apple (thanks to xsltproc & python), so this should be
all possible layout IDs that Apple ever had.
Again, to find your layout-id:
find /proc/device-tree -name layout-id | xargs hexdump -e '1/4 "%d\n"'
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
reply other threads:[~2006-06-07 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1149625152.32002.38.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=debian-powerpc@lists.debian.org \
--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).