From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: George Staikos <staikos@kde.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: New TiPB - PCMCIA settings
Date: 19 Nov 2002 10:18:13 +0100 [thread overview]
Message-ID: <1037697493.1624.140.camel@zion> (raw)
In-Reply-To: <1037695549.3241.479.camel@thor>
On Tue, 2002-11-19 at 09:45, Michel Dänzer wrote:
>
> On Die, 2002-11-19 at 00:29, George Staikos wrote:
> >
> > What doesn't work right now:
> > - dmasound is aweful (lots of clicking and sounds bad)
>
> With a current benh kernel? Do the latest TiBooks have different sound
> hardware again?
According to the device-tree, it seems to be a snapper (tas3004),
maybe we don't set some i2s registers properly, I don't know.
The device-tree also imply that it supports 2 sample rates,
it's possible that the sample rate or format on i2s side doesn't
match what is configured in the texas chip.
> > - video issues in XFree86 and fbdev, along with sleeping
> > - closing the screen causes lots of garbling on the screen.
>
> Sleep doesn't even work with the 7500 Mobility yet, let alone the 9000
> Mobility. Otherwise, people have reported moderate success with radeonfb
> from the current benh tree and my DRI snapshot Debian packages.
The remaining problem seem to be the same as desktop r9000's with ADC
connector, that is a palette issue. According to Ani, the DACs are
physical (that is, regardless of CRTC1 or 2 usage, the DACs for each
output is fixed, and we may not be configuring the palette in the
proper one).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-19 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 8:45 New TiPB - PCMCIA settings Michel Dänzer
2002-11-19 9:18 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 23:29 George Staikos
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=1037697493.1624.140.camel@zion \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
--cc=staikos@kde.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).