linux-kernel - Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200705262149.09948.mb@bu3sch.de>
Date:	Sat, 26 May 2007 21:49:09 +0200
From:	Michael Buesch <mb@...sch.de>
To:	Uwe Bugla <uwe.bugla@....de>
Cc:	"Benoit Boissinot" <bboissin@...il.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Maximilian Engelhardt" <maxi@...monizer.de>,
	linux-wireless@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)

On Saturday 26 May 2007 21:39:54 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> > Uwe, please try the following patch:
> >
> > Index: bu3sch-wireless-dev/drivers/net/b44.c
> > ===================================================================
> > --- bu3sch-wireless-dev.orig/drivers/net/b44.c	2007-05-18
> > 18:09:50.000000000 +0200 +++
> > bu3sch-wireless-dev/drivers/net/b44.c	2007-05-26 21:18:28.000000000 +0200
> > @@ -2201,10 +2201,12 @@ static int __devinit b44_init_one(struct
> >  		printk("%2.2x%c", dev->dev_addr[i],
> >  		       i == 5 ? '\n' : ':');
> >
> > +#if 0
> >  	/* Initialize phy */
> >  	spin_lock_irq(&bp->lock);
> >  	b44_chip_reset(bp);
> >  	spin_unlock_irq(&bp->lock);
> > +#endif
> >
> >  	return 0;
> 
> Against what kernel please?
> Just try to be a bit more eloquent, man!

Against a kernel which does not work for you, of course.

Sometimes I wonder... (no better not say that).

-- 
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/