From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: debian-powerpc@lists.debian.org
Cc: michal.k.k.piotrowski@gmail.com, rbrito@gmail.com,
g <krh@redhat.com>,
linux-kernel@vger.kernel.org, rjw@sisk.pl,
linuxppc-dev@ozlabs.org,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-pm@lists.linux-foundation.org,
"Tim Teulings" <rael@edge.ping.de>
Subject: firewire in prebuilt kernel packages (was Re: Sleep problems with kernels >= 2.6.21 on powerpc)
Date: Wed, 05 Sep 2007 21:01:28 +0200 [thread overview]
Message-ID: <46DEFD08.8060402@s5r6.in-berlin.de> (raw)
In-Reply-To: <46DEEBBE.4070201@s5r6.in-berlin.de>
>>> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <rael@edge.ping.de> wrote:
>>> The kernel is:
>>>> Linux kismet 2.6.22-1-powerpc #1 Sun Jul 29 13:58:06 CEST 2007 ppc GNU/Linux
>>> The relveant debian package:
>>>> linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb
>>> I'm running a mixture of debian testing/unstable.
At the moment, distributors should not provide the experimental
firewire-* drivers as the only or primary FireWire drivers, unless they
know exactly what the gotchas are. As a hint, CONFIG_FIREWIRE currently
depends on EXPERIMENTAL, CONFIG_IEEE1394 does not. Some basic
information can be found at http://wiki.linux1394.org/JujuMigration.
--
Stefan Richter
-=====-=-=== =--= --=-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-09-05 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 2:37 Sleep problems with kernels >= 2.6.21 on powerpc Rogério Brito
2007-08-26 23:21 ` Michal Piotrowski
2007-08-27 6:52 ` Rogério Brito
2007-08-27 7:14 ` Tim Teulings
2007-08-30 20:42 ` Tim Teulings
2007-09-05 17:07 ` Andrew Morton
2007-09-05 17:28 ` Randy Dunlap
2007-09-05 17:43 ` Stefan Richter
2007-09-05 17:58 ` Randy Dunlap
2007-09-05 17:47 ` Stefan Richter
2007-09-05 18:06 ` [PATCH] " Stefan Richter
2007-09-05 18:24 ` Stefan Richter
2007-09-05 19:01 ` Stefan Richter [this message]
2007-09-05 19:44 ` Andrew Morton
2007-09-05 20:12 ` Stefan Richter
2007-09-06 7:50 ` [PATCH update] " Stefan Richter
2007-08-27 8:37 ` Michel Dänzer
2007-08-27 9:55 ` Pavel Machek
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=46DEFD08.8060402@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=debian-powerpc@lists.debian.org \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rael@edge.ping.de \
--cc=rbrito@gmail.com \
--cc=rjw@sisk.pl \
/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).