On Mon, Sep 17, 2007 at 02:21:27PM -0300, Otavio Salvador wrote:
> dann frazier <[EMAIL PROTECTED]> writes:
>
> > Both #317258 and #410817 are showing activity now, but its difficult
> > to predict when they will be resolved. In the meantime, I'm going to
> > upload our current set of changes to p
dann frazier <[EMAIL PROTECTED]> writes:
> Both #317258 and #410817 are showing activity now, but its difficult
> to predict when they will be resolved. In the meantime, I'm going to
> upload our current set of changes to proposed-updates so we can
> increase the testing pool. If these issues get
[This is becoming off-topic for debian-release, and is redundant for
debian-kernel (which already receives bug traffic), so removing both
from To:]
On Sat, Sep 15, 2007 at 09:50:13AM +0200, Bastian Blank wrote:
> On Fri, Sep 14, 2007 at 07:03:32PM -0600, dann frazier wrote:
> > I've modified the
On Tue, Sep 11, 2007 at 11:20:35AM +0200, Luk Claes wrote:
> dann frazier wrote:
>> hey,
>> I think we're nearly ready for a kernel upload to proposed-updates.
>> Here's the current list of changes queued for a stable upload.
>
> Can you please consider fixing #317258 again? It's only about PCI ID
On Fri, Sep 14, 2007 at 03:42:50PM +0200, Frederik Schueler wrote:
> Hello,
>
> I think we should add patches to update the forcedeth and e1000 drivers
> to the latest version, too. Those are many changes, but also many new
> boxes require those new drivers: obviously most nvidia based athlon
> a
On Fri, Sep 14, 2007 at 07:03:32PM -0600, dann frazier wrote:
> I've modified the patch to also blacklist these controllers in the
> megaraid_mbox driver to avoid an overlap. I tested this patch on one
> of the 2M cards I have (which, for whatever reason, all work just fine
> with either driver).
On Fri, Sep 14, 2007 at 07:12:52PM +0200, Bastian Blank wrote:
> On Fri, Sep 14, 2007 at 10:53:50AM -0600, dann frazier wrote:
> > Have you verified that this fix works in 2.6.18? It seems like its
> > adding support for megaraid3s w/ specific subsystem devices, while
> > 2.6.18 (and current upstre
On Fri, Sep 14, 2007 at 10:53:50AM -0600, dann frazier wrote:
> Have you verified that this fix works in 2.6.18? It seems like its
> adding support for megaraid3s w/ specific subsystem devices, while
> 2.6.18 (and current upstream) claim megaraid3 devices w/ *any*
> subsystem ids. (Although there d
On Tue, Sep 11, 2007 at 11:20:35AM +0200, Luk Claes wrote:
> dann frazier wrote:
>> hey,
>> I think we're nearly ready for a kernel upload to proposed-updates.
>> Here's the current list of changes queued for a stable upload.
>
> Can you please consider fixing #317258 again? It's only about PCI ID
Frederik Schueler wrote:
Hello,
Hi
I think we should add patches to update the forcedeth and e1000 drivers
to the latest version, too. Those are many changes, but also many new
boxes require those new drivers: obviously most nvidia based athlon
and opteron boards, and many xeon board (superm
Hello,
I think we should add patches to update the forcedeth and e1000 drivers
to the latest version, too. Those are many changes, but also many new
boxes require those new drivers: obviously most nvidia based athlon
and opteron boards, and many xeon board (supermicro, tyan).
What is the chance
On Fri, Sep 14, 2007 at 02:18:48PM +0200, Holger Levsen wrote:
> Is there?
The patch needs to be applied upstream until it can appear again. It
moves devices between two different drivers, which obviously are not
compatible.
Both megaraid drivers looks not really good maintained.
Bastian
--
A
Hi,
On Tuesday 11 September 2007 12:16, Luk Claes wrote:
> Bastian Blank wrote:
> > On Tue, Sep 11, 2007 at 11:20:35AM +0200, Luk Claes wrote:
> >> Can you please consider fixing #317258 again? It's only about PCI ID
> >> mappings that got lost while splitting the megaraid and megaraid_mbox
> >> d
Bastian Blank wrote:
On Tue, Sep 11, 2007 at 11:20:35AM +0200, Luk Claes wrote:
Can you please consider fixing #317258 again? It's only about PCI ID
mappings that got lost while splitting the megaraid and megaraid_mbox
drivers. At one point this bug got fixed, but it was reverted later on,
no
On Tue, Sep 11, 2007 at 11:20:35AM +0200, Luk Claes wrote:
> Can you please consider fixing #317258 again? It's only about PCI ID
> mappings that got lost while splitting the megaraid and megaraid_mbox
> drivers. At one point this bug got fixed, but it was reverted later on,
> no idea why?
No p
dann frazier wrote:
hey,
I think we're nearly ready for a kernel upload to proposed-updates.
Here's the current list of changes queued for a stable upload.
Can you please consider fixing #317258 again? It's only about PCI ID
mappings that got lost while splitting the megaraid and megaraid_mbo
hey,
I think we're nearly ready for a kernel upload to proposed-updates.
Here's the current list of changes queued for a stable upload.
I've reverted the forcedeth changes for #439219 until we get some
testers for them.
The last thing I'm waiting for is some final feedback about a
backported fix
17 matches
Mail list logo
