From: Benjamin Herrenschmidt <bh40@calva.net>
To: Olaf Hering <olh@suse.de>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ThinkPad 850 Patches for 2.2.16
Date: Tue, 24 Oct 2000 21:22:20 +0200 [thread overview]
Message-ID: <19340918125404.28619@192.168.1.10> (raw)
In-Reply-To: <20001024200338.A908@suse.de>
>The sound stuff should be moved out of arch/ppc into the driver cs4232, you
>can't have it as a module right now. xmms works fine, but I have many
>dropouts. Any ideas how to finetune that?
>That sound-patch will proably break the other PReP machines, I will test
>it on the 43p 133 later. We need proably a _PREP_IBM_portable or so.
No please ;)
I beleive you must have a way to probe for the machine type and do the
right thing, don't you ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-24 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 18:03 ThinkPad 850 Patches for 2.2.16 Olaf Hering
2000-10-24 19:22 ` Benjamin Herrenschmidt [this message]
2000-10-24 19:29 ` Olaf Hering
2000-10-24 20:12 ` Hollis R Blanchard
2000-10-25 23:37 ` Olaf Hering
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=19340918125404.28619@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@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 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).