On Thu, 03 Apr 2008, maximilian attems wrote:
On Thu, Apr 03, 2008 at 07:35:38AM +0200, Frans Pop wrote:
A post on lkml today [1] by one of the people working on it makes clear
that
the new firewire stack will not get into shape in time for lenny.
the third fedora release happens with
[ dropping release cc ]
On Thu, Apr 03, 2008 at 07:35:38AM +0200, Frans Pop wrote:
A post on lkml today [1] by one of the people working on it makes clear that
the new firewire stack will not get into shape in time for lenny.
the third fedora release happens with juju firewire stack only.
A post on lkml today [1] by one of the people working on it makes clear that
the new firewire stack will not get into shape in time for lenny.
At the same time, there is quite a big demand from users for the old stack
because there hardware is not supported by the new one. Some of the
relevant
On 29/07/07 10:50, maximilian attems wrote:
so your bugreport needs to reach upstream,
so that your chipset regains support on the new stack.
http://wiki.linux1394.org/ToDo states:
Come up with a quirk fix for NForce2. The person to do so will most
certainly require direct access to this
On Thu, Sep 13, 2007 at 01:32:41AM +0200, Mourad De Clerck wrote:
It would be nice if we could activate (by blacklist) the old stack for
only those devices that used to work but not anymore, and the new stack
for the rest.
no way dream on.
the old stack sucks sooo much that beeing in the
On 13/09/07 01:42, maximilian attems wrote:
On Thu, Sep 13, 2007 at 01:32:41AM +0200, Mourad De Clerck wrote:
It would be nice if we could activate (by blacklist) the old stack for
only those devices that used to work but not anymore, and the new stack
for the rest.
no way dream on.
the
On Thu, Sep 13, 2007 at 01:56:18AM +0200, Mourad De Clerck wrote:
Why not follow upstream recommendation on this one?
Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux
distributors (kernel packagers) as well as to regular users is: Build
only the old IEEE 1394 drivers.
-- M
On 13/09/07 02:06, maximilian attems wrote:
lenny will _not_ release with any of these versions.
and it is very much now on the time to push for such changes.
also such regressions are expected in a new more powerful stack.
if both are available such regressions never get tracked,
see alsa
On 29/07/07 10:50, maximilian attems wrote:
please file aboves report in bugzilla.kernel.org
and inform us of your bug nr.
Done, see:
http://bugzilla.kernel.org/show_bug.cgi?id=8828
Thanks,
-- Mourad DC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
On Sun, Jul 29, 2007 at 05:19:53AM +0200, Mourad De Clerck wrote:
After upgrading to 2.6.22, my firewire controller just stopped working
altogether. It had been working perfectly in all previous versions. I was
looking to manually load the old stack/sbp2 modules, but I see you chose
not to
Package: linux-image-2.6.22-1-k7
Version: 2.6.22-2
Severity: important
After upgrading to 2.6.22, my firewire controller just stopped working
altogether. It had been working perfectly in all previous versions. I was
looking to manually load the old stack/sbp2 modules, but I see you chose
not to
11 matches
Mail list logo
