Can you give 2.6.16 a try? The diff is not that big and we might
be able to find out what broke if you find out 2.6.16 works.
You can also try later kernels like .17, .18, .19 to further
reduce the patch. (You could also git-bisect, if you have the time).
git-diff v2.6.16..v2.6.22-rc3
Can you also test the following patch?
I think there's a bug in b44 that is doesn't properly discard
shared IRQs, so it might possibly generate a NAPI storm, dunno.
Worth a try.
Index: linux-2.6.22-rc3/drivers/net/b44.c
===
---
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
I already tried your -mm kernel, but it crashes on my machine
for other reasons. (Yeah, I should look into them, too :P )
err, please do. Just the oops trace would be a start.
Sorry, I can't reproduce the crash anymore. :(
But now I
On Monday 28 May 2007 16:12:12 Maximilian Engelhardt wrote:
On Monday 28 May 2007, Michael Buesch wrote:
Can you also test the following patch?
I think there's a bug in b44 that is doesn't properly discard
shared IRQs, so it might possibly generate a NAPI storm, dunno.
Worth a try
On Monday 28 May 2007 16:09:46 Maximilian Engelhardt wrote:
On Monday 28 May 2007, Michael Buesch wrote:
Can you give 2.6.16 a try? The diff is not that big and we might
be able to find out what broke if you find out 2.6.16 works.
You can also try later kernels like .17, .18, .19 to further
On Monday 28 May 2007 17:32:51 Thomas Gleixner wrote:
On Mon, 2007-05-28 at 17:14 +0200, Michael Buesch wrote:
The -oldconfig1 is the kernel that had no problems and the other shows
the b44
problem. So if High Resolution Timer Support is disabled everything works
fine and if I
Ok, another question: On which CPU architecture are you?
--
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Sunday 27 May 2007 23:13:32 Michael Buesch wrote:
> On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
> > 2.6.21.1:
> > [ 5] local 192.168.1.2 port 58414 connected with 192.168.1.1 port 5001
> > [ 5] 0.0-60.6 sec 1.13 MBytes157 Kbits/sec
> > [ 4]
On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
> 2.6.21.1:
> [ 5] local 192.168.1.2 port 58414 connected with 192.168.1.1 port 5001
> [ 5] 0.0-60.6 sec 1.13 MBytes157 Kbits/sec
> [ 4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 57837
> [ 4] 0.0-63.1 sec
On Sunday 27 May 2007 22:36:39 Maximilian Engelhardt wrote:
> When I ran 2.6.21.1 or 2.6.22-rc3 without any debugging tools just in normal
> use I didn't notice any problems. It did work fine as I would expect it.
> I think the wget and ping tests here are as they should be.
>
> With
On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
> 2.6.22-rc3:
>
> [ 5] local 192.168.1.2 port 46557 connected with 192.168.1.1 port 5001
> [ 5] 0.0-60.4 sec 58.9 MBytes 8.18 Mbits/sec
> [ 4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 51633
> [ 4] 0.0-63.1 sec
On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
2.6.22-rc3:
[ 5] local 192.168.1.2 port 46557 connected with 192.168.1.1 port 5001
[ 5] 0.0-60.4 sec 58.9 MBytes 8.18 Mbits/sec
[ 4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 51633
[ 4] 0.0-63.1 sec 7.27
On Sunday 27 May 2007 22:36:39 Maximilian Engelhardt wrote:
When I ran 2.6.21.1 or 2.6.22-rc3 without any debugging tools just in normal
use I didn't notice any problems. It did work fine as I would expect it.
I think the wget and ping tests here are as they should be.
With 2.6.22-rc2-mm1 I
On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
2.6.21.1:
[ 5] local 192.168.1.2 port 58414 connected with 192.168.1.1 port 5001
[ 5] 0.0-60.6 sec 1.13 MBytes157 Kbits/sec
[ 4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 57837
[ 4] 0.0-63.1 sec 2.82
On Sunday 27 May 2007 23:13:32 Michael Buesch wrote:
On Sunday 27 May 2007 21:25:17 Maximilian Engelhardt wrote:
2.6.21.1:
[ 5] local 192.168.1.2 port 58414 connected with 192.168.1.1 port 5001
[ 5] 0.0-60.6 sec 1.13 MBytes157 Kbits/sec
[ 4] local 192.168.1.2 port 5001 connected
Ok, another question: On which CPU architecture are you?
--
Greetings Michael.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Sunday 27 May 2007 01:00:04 [EMAIL PROTECTED] wrote:
> From: Divy Le Ray <[EMAIL PROTECTED]>
>
> Bump FW version to 4.1.
> Modify chip tuning in consequence.
>
> Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
> ---
> @@ -2496,11 +2500,11 @@ static void __devinit init_mtus(unsigned
>*
r people like me and others.
Oh, poor poor guy.
I lack knowledge about b44? Oh, I suppose that was a typo and you
meant yourself.
> Hello my dear Andrew Morton,
>
> Could you please do me and the rest of the world two favours?
>
> A. Rip Michael Buesches code out of the mm-tree
On Saturday 26 May 2007 22:33:13 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 21:57 schrieben Sie:
> > Uwe Bugla wrote:
> > > OK, applied this one against 2.6.22-rc3, assuming a typo error by you,
> > > Andrew.
> > >
> > > Result is: No change: non functionable b44 device!
> >
> > Could you please
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
> > ===
> > ---
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.0
+0200
+++ bu3sch-wireless-dev/drivers/net/b44.c 2007-05-26
On Saturday 26 May 2007 20:58:37 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 20:41 schrieben Sie:
> > On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > > Yes, sure! But the
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
> > I ask to try wireless-dev, as the driver works perfectly fine
> > for me there, but he refuses to try it, too. So I'm stuck.
>
> I don't think he knows how to obtain it.
>
> Uwe, http://userweb.kernel.org/~akpm/git-wireless.patch.gz is
On Saturday 26 May 2007 20:41:09 Benoit Boissinot wrote:
> On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > clear
&
On Saturday 26 May 2007 19:24:33 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 19:18 schrieben Sie:
> > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > clear enough in the sense of being distinctive enough, just
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> Yes, sure! But the help text is very unlucky and humble, and it is not clear
> enough in the sense of being distinctive enough, just clear and
> comprehensive.
Why don't you simply submit a patch to change the helptext then?
I'm not sure why
On Saturday 26 May 2007 18:26:06 Uwe Bugla wrote:
> > I think we don't have IRQ assignment problems. Uwe simply disabled
> > b44-PCI support in his first bugreport (I guess).
>
> Yes!
>
> > So there was
> > no b44-PCI driver loaded.
>
> Well, not exactly: b44 plus ssb were in fact produced,
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
> > I already tried your -mm kernel, but it crashes on my machine
> > for other reasons. (Yeah, I should look into them, too :P )
>
> err, please do. Just the oops trace would be a start.
Yes, I will look into it. I think it was related to
Andrew,
I am going to ignore Uwe from now on. It's simply impossible
to debug the problem the way he is responding.
Well, I'm not the first person in the Linux community adding
him to the killfile, ... .
I ask to try wireless-dev, as the driver works perfectly fine
for me there, but he refuses to
On Saturday 26 May 2007 12:40:54 Uwe Bugla wrote:
> Yes! This sort of mistakes is completely impossible, as I use to work with
> aliases rather than IP adresses. The machine I tried to ping (i. e. my
> router) is called Jerry (as a reminiscence to Mr. "Captan Trips" from
> Grateful Dead), and
On Saturday 26 May 2007 12:40:54 Uwe Bugla wrote:
Yes! This sort of mistakes is completely impossible, as I use to work with
aliases rather than IP adresses. The machine I tried to ping (i. e. my
router) is called Jerry (as a reminiscence to Mr. Captan Trips from
Grateful Dead), and thus
Andrew,
I am going to ignore Uwe from now on. It's simply impossible
to debug the problem the way he is responding.
Well, I'm not the first person in the Linux community adding
him to the killfile, ... .
I ask to try wireless-dev, as the driver works perfectly fine
for me there, but he refuses to
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
I already tried your -mm kernel, but it crashes on my machine
for other reasons. (Yeah, I should look into them, too :P )
err, please do. Just the oops trace would be a start.
Yes, I will look into it. I think it was related to my
On Saturday 26 May 2007 18:26:06 Uwe Bugla wrote:
I think we don't have IRQ assignment problems. Uwe simply disabled
b44-PCI support in his first bugreport (I guess).
Yes!
So there was
no b44-PCI driver loaded.
Well, not exactly: b44 plus ssb were in fact produced, but did not
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
Yes, sure! But the help text is very unlucky and humble, and it is not clear
enough in the sense of being distinctive enough, just clear and
comprehensive.
Why don't you simply submit a patch to change the helptext then?
I'm not sure why you
On Saturday 26 May 2007 19:24:33 Uwe Bugla wrote:
Am Samstag, 26. Mai 2007 19:18 schrieben Sie:
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
Yes, sure! But the help text is very unlucky and humble, and it is not
clear enough in the sense of being distinctive enough, just clear and
On Saturday 26 May 2007 20:41:09 Benoit Boissinot wrote:
On 5/26/07, Michael Buesch [EMAIL PROTECTED] wrote:
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
Yes, sure! But the help text is very unlucky and humble, and it is not
clear
enough in the sense of being distinctive enough
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
I ask to try wireless-dev, as the driver works perfectly fine
for me there, but he refuses to try it, too. So I'm stuck.
I don't think he knows how to obtain it.
Uwe, http://userweb.kernel.org/~akpm/git-wireless.patch.gz is the
On Saturday 26 May 2007 20:58:37 Uwe Bugla wrote:
Am Samstag, 26. Mai 2007 20:41 schrieben Sie:
On 5/26/07, Michael Buesch [EMAIL PROTECTED] wrote:
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
Yes, sure! But the help text is very unlucky and humble, and it is not
clear enough
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.0
+0200
+++ bu3sch-wireless-dev/drivers/net/b44.c 2007-05-26
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
===
---
On Saturday 26 May 2007 22:33:13 Uwe Bugla wrote:
Am Samstag, 26. Mai 2007 21:57 schrieben Sie:
Uwe Bugla wrote:
OK, applied this one against 2.6.22-rc3, assuming a typo error by you,
Andrew.
Result is: No change: non functionable b44 device!
Could you please send the following:
Andrew Morton,
Could you please do me and the rest of the world two favours?
A. Rip Michael Buesches code out of the mm-tree
B. Give Michael Buesch a fair chance to revise his disfunctionable code
outside the mm-tree and / or the vanilla mainline.
Andrew, I see that you are in a bad
On Sunday 27 May 2007 01:00:04 [EMAIL PROTECTED] wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Bump FW version to 4.1.
Modify chip tuning in consequence.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
@@ -2496,11 +2500,11 @@ static void __devinit init_mtus(unsigned
* it can
On Friday 25 May 2007 21:40, Uwe Bugla wrote:
> Am Freitag, 25. Mai 2007 20:48 schrieben Sie:
> > On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote:
> > > Perhaps someone reading this could try to reproduce that problem on his
> > > machine.
> > > Now who of the readers owes a Broadcom 4401 NIC
On Friday 25 May 2007 17:59:29 Uwe Bugla wrote:
> Am Freitag, 25. Mai 2007 16:52 schrieben Sie:
> > On Friday 25 May 2007 15:59:49 Uwe Bugla wrote:
> > > Well if you're so clever in software development then please provide an
> > > exception handling for the ssb module which is specifically NOT
On Friday 25 May 2007 15:59:49 Uwe Bugla wrote:
> Well if you're so clever in software development then please provide an
> exception handling for the ssb module which is specifically NOT needed by my
> onboard controller, OK?
> Just provide compatibility to non-wireless NICs, i. e. to non-ssb
On Friday 25 May 2007 15:12:09 Michael Buesch wrote:
> On Thursday 24 May 2007 22:06:59 Andrew Morton wrote:
> > On Thu, 24 May 2007 21:56:16 +0200
> > "Uwe Bugla" <[EMAIL PROTECTED]> wrote:
> >
> > > Hi everybody,
> >
> > (added
On Thursday 24 May 2007 23:16:48 Uwe Bugla wrote:
> Above that, the commiter DID IGNORE your baselines of testing, but at the
> same
> time got highly profile-neurotic regarding the copyright issue of 2007,
> didn't he (Let's call this a basic instinct of our precedents: the apes:
> shouting:
On Thursday 24 May 2007 22:06:59 Andrew Morton wrote:
> On Thu, 24 May 2007 21:56:16 +0200
> "Uwe Bugla" <[EMAIL PROTECTED]> wrote:
>
> > Hi everybody,
>
> (added linux-wireless, others)
>
> > The patch against b44.c contained in 2.6.22-rc2-mm1 has two consequences:
> >
> > 1. a tight binding
On Thursday 24 May 2007 22:06:59 Andrew Morton wrote:
On Thu, 24 May 2007 21:56:16 +0200
Uwe Bugla [EMAIL PROTECTED] wrote:
Hi everybody,
(added linux-wireless, others)
The patch against b44.c contained in 2.6.22-rc2-mm1 has two consequences:
1. a tight binding to module ssb
On Friday 25 May 2007 15:12:09 Michael Buesch wrote:
On Thursday 24 May 2007 22:06:59 Andrew Morton wrote:
On Thu, 24 May 2007 21:56:16 +0200
Uwe Bugla [EMAIL PROTECTED] wrote:
Hi everybody,
(added linux-wireless, others)
The patch against b44.c contained in 2.6.22-rc2-mm1
On Thursday 24 May 2007 23:16:48 Uwe Bugla wrote:
Above that, the commiter DID IGNORE your baselines of testing, but at the
same
time got highly profile-neurotic regarding the copyright issue of 2007,
didn't he (Let's call this a basic instinct of our precedents: the apes:
shouting: I, I,
On Friday 25 May 2007 15:59:49 Uwe Bugla wrote:
Well if you're so clever in software development then please provide an
exception handling for the ssb module which is specifically NOT needed by my
onboard controller, OK?
Just provide compatibility to non-wireless NICs, i. e. to non-ssb
On Friday 25 May 2007 17:59:29 Uwe Bugla wrote:
Am Freitag, 25. Mai 2007 16:52 schrieben Sie:
On Friday 25 May 2007 15:59:49 Uwe Bugla wrote:
Well if you're so clever in software development then please provide an
exception handling for the ssb module which is specifically NOT needed by
On Friday 25 May 2007 21:40, Uwe Bugla wrote:
Am Freitag, 25. Mai 2007 20:48 schrieben Sie:
On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote:
Perhaps someone reading this could try to reproduce that problem on his
machine.
Now who of the readers owes a Broadcom 4401 NIC and can
On Saturday 05 May 2007 20:48:11 Andrew Morton wrote:
> On Sat, 05 May 2007 17:48:28 +0200 Maciej Rutecki <[EMAIL PROTECTED]> wrote:
>
> > Andrew Morton pisze:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/
> > >
> > >
> >
> > CC [M]
On Saturday 05 May 2007 20:48:11 Andrew Morton wrote:
On Sat, 05 May 2007 17:48:28 +0200 Maciej Rutecki [EMAIL PROTECTED] wrote:
Andrew Morton pisze:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/
CC [M] lib/zlib_deflate/deflate_syms.o
LD
the option for s390.
> Goes on top of git-wireless.patch.
>
> Cc: Michael Buesch <[EMAIL PROTECTED]>
> Cc: John W. Linville <[EMAIL PROTECTED]>
> Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Acked-by: Michael Buesch <[EMAIL PROTECTED]>
> ---
>
>
On Monday 23 April 2007 16:14, Martin Schwidefsky wrote:
> From: Martin Schwidefsky <[EMAIL PROTECTED]>
>
> Add HAS_IOMEM dependency to the "Sonics Silicon Backplane" menu.
> This hides the menu for s390.
> Goes on top of git-wireless.patch.
>
> Cc: Michael
On Monday 23 April 2007 13:48, Arnd Bergmann wrote:
> On Monday 23 April 2007, Martin Schwidefsky wrote:
> >
> > > Isn't B44 already behind a WIRELESS or IEEE80211 or similar option that
> > > can't be selected on s390?
> >
> > No, the option can be found in drivers/net/Kconfig under menu
On Monday 23 April 2007 13:48, Arnd Bergmann wrote:
On Monday 23 April 2007, Martin Schwidefsky wrote:
Isn't B44 already behind a WIRELESS or IEEE80211 or similar option that
can't be selected on s390?
No, the option can be found in drivers/net/Kconfig under menu Ethernet
(10 or
On Monday 23 April 2007 16:14, Martin Schwidefsky wrote:
From: Martin Schwidefsky [EMAIL PROTECTED]
Add HAS_IOMEM dependency to the Sonics Silicon Backplane menu.
This hides the menu for s390.
Goes on top of git-wireless.patch.
Cc: Michael Buesch [EMAIL PROTECTED]
Cc: John W. Linville
-wireless.patch.
Cc: Michael Buesch [EMAIL PROTECTED]
Cc: John W. Linville [EMAIL PROTECTED]
Signed-off-by: Martin Schwidefsky [EMAIL PROTECTED]
Acked-by: Michael Buesch [EMAIL PROTECTED]
---
drivers/net/Kconfig |1 +
1 files changed, 1 insertion(+)
diff -urpN linux-2.6/drivers/net/Kconfig
On Sunday 22 April 2007 09:53, Martin Schwidefsky wrote:
> On Sun, 2007-04-22 at 01:19 +0200, Arnd Bergmann wrote:
> > > diff -urpN linux-2.6/drivers/ssb/Kconfig
> > > linux-2.6-patched/drivers/ssb/Kconfig
> > > --- linux-2.6/drivers/ssb/Kconfig 2007-04-19 15:24:40.0
> > > +0200
>
On Sunday 22 April 2007 09:53, Martin Schwidefsky wrote:
On Sun, 2007-04-22 at 01:19 +0200, Arnd Bergmann wrote:
diff -urpN linux-2.6/drivers/ssb/Kconfig
linux-2.6-patched/drivers/ssb/Kconfig
--- linux-2.6/drivers/ssb/Kconfig 2007-04-19 15:24:40.0
+0200
+++
On Friday 20 April 2007 13:35, Martin Schwidefsky wrote:
> From: Martin Schwidefsky <[EMAIL PROTECTED]>
>
> Make the "Sonics Silicon Backplane" menu dependent on the two buses
> it can be found on.
> Goes on top of git-wireless.patch.
>
> Cc: Michael Bu
On Friday 20 April 2007 13:35, Martin Schwidefsky wrote:
From: Martin Schwidefsky [EMAIL PROTECTED]
Make the Sonics Silicon Backplane menu dependent on the two buses
it can be found on.
Goes on top of git-wireless.patch.
Cc: Michael Buesch [EMAIL PROTECTED]
Cc: John W. Linville [EMAIL
Hi Greg,
looking through the pl2303 driver, it seems you know about
the internals.
So I'm contacting you to ask if you got specification for this device.
I have got a pl2305 (usb to parport) device and it seems there's no
driver for it. On the Prolific page there is a datasheet download,
but it
Hi Greg,
looking through the pl2303 driver, it seems you know about
the internals.
So I'm contacting you to ask if you got specification for this device.
I have got a pl2305 (usb to parport) device and it seems there's no
driver for it. On the Prolific page there is a datasheet download,
but it
On Saturday 07 April 2007 19:44, Larry Finger wrote:
> Johannes Berg wrote:
> > On Sat, 2007-04-07 at 15:51 +0200, Michael Buesch wrote:
> >> On Saturday 07 April 2007 02:01, Larry Finger wrote:
> >>> The current mb and wireless-dev git trees
On Saturday 07 April 2007 19:44, Larry Finger wrote:
Johannes Berg wrote:
On Sat, 2007-04-07 at 15:51 +0200, Michael Buesch wrote:
On Saturday 07 April 2007 02:01, Larry Finger wrote:
The current mb and wireless-dev git trees both get a kernel NULL pointer
in param_set_copystring
when
the bcm43xx
> chip contains a USB (dangling) core. This bug has been fixed in Michael
> Buesch's tree, but
> apparently not yet in Linville's wireless-dev tree. The patch is as follows:
>
> commit 08531ff130bcc8181d9294a66e25010f48eefb97
> Author: Michael Buesch <[EMAIL PR
08531ff130bcc8181d9294a66e25010f48eefb97
Author: Michael Buesch [EMAIL PROTECTED]
Date: Wed Mar 7 23:01:08 2007 +0100
ssb: Don't freeze unregistered devices.
No, that's a different fix for suspend.
This is the fix:
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf
Pull
On Monday 05 March 2007 19:42, David Brownell wrote:
> On Monday 05 March 2007 3:26 am, Michael Buesch wrote:
>
> > > Actually, it seems like I will run into other kinds of nasty problems
> > > due to stupid design of the HCD code. The OHCI code #includes
> > >
On Monday 05 March 2007 11:57, Michael Buesch wrote:
> > > CC drivers/usb/host/ohci-hcd.o
> > > In file included from
> > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931:
> > > /home/bunk/linux/kernel-2.6/linux-2.6.21
On Monday 05 March 2007 11:49, Michael Buesch wrote:
> On Monday 05 March 2007 02:47, Adrian Bunk wrote:
> > On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.20-mm2:
> > >...
> > >
On Monday 05 March 2007 02:47, Adrian Bunk wrote:
> On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.20-mm2:
> >...
> > git-wireless.patch
> >...
> > git trees
> >...
>
> <-- snip -->
>
> ...
> CC drivers/usb/host/ohci-hcd.o
> In file
On Monday 05 March 2007 02:47, Adrian Bunk wrote:
> On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.20-mm2:
> >...
> > git-wireless.patch
> >...
> > git trees
> >...
>
> Multiple copies of the same drivers are a problem:
>
> <-- snip -->
>
> ...
>
On Monday 05 March 2007 05:21, Miles Lane wrote:
> WARNING: "pcmcia_access_configuration_register" [drivers/ssb/ssb.ko]
> undefined!
> WARNING: "pccard_parse_tuple"
> [drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko] undefined!
> WARNING: "pcmcia_register_driver"
>
On Monday 05 March 2007 05:21, Miles Lane wrote:
WARNING: pcmcia_access_configuration_register [drivers/ssb/ssb.ko]
undefined!
WARNING: pccard_parse_tuple
[drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko] undefined!
WARNING: pcmcia_register_driver
On Monday 05 March 2007 02:47, Adrian Bunk wrote:
On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-mm2:
...
git-wireless.patch
...
git trees
...
Multiple copies of the same drivers are a problem:
-- snip --
...
LD
On Monday 05 March 2007 02:47, Adrian Bunk wrote:
On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-mm2:
...
git-wireless.patch
...
git trees
...
-- snip --
...
CC drivers/usb/host/ohci-hcd.o
In file included from
On Monday 05 March 2007 11:49, Michael Buesch wrote:
On Monday 05 March 2007 02:47, Adrian Bunk wrote:
On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-mm2:
...
git-wireless.patch
...
git trees
...
-- snip --
...
CC
On Monday 05 March 2007 11:57, Michael Buesch wrote:
CC drivers/usb/host/ohci-hcd.o
In file included from
/home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931:
/home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47:
error
On Monday 05 March 2007 19:42, David Brownell wrote:
On Monday 05 March 2007 3:26 am, Michael Buesch wrote:
Actually, it seems like I will run into other kinds of nasty problems
due to stupid design of the HCD code. The OHCI code #includes
the various drivers, which have a module_init
On Saturday 03 March 2007 22:03, Larry Finger wrote:
> Michael Buesch wrote:
> > On Saturday 03 March 2007 20:03, Sam Ravnborg wrote:
> >> Replacing use of UTS_RELEASE with utsname()->release
> >> avoids that this module is rebuild each
> >> time the ke
On Saturday 03 March 2007 20:03, Sam Ravnborg wrote:
> Replacing use of UTS_RELEASE with utsname()->release
> avoids that this module is rebuild each
> time the kernel version changes.
>
> Compile tested only.
I vote to get rid of the whole bcm43xx_ethtool.c file, as it's useless.
It will vanish
On Saturday 03 March 2007 20:03, Sam Ravnborg wrote:
Replacing use of UTS_RELEASE with utsname()-release
avoids that this module is rebuild each
time the kernel version changes.
Compile tested only.
I vote to get rid of the whole bcm43xx_ethtool.c file, as it's useless.
It will vanish with
On Saturday 03 March 2007 22:03, Larry Finger wrote:
Michael Buesch wrote:
On Saturday 03 March 2007 20:03, Sam Ravnborg wrote:
Replacing use of UTS_RELEASE with utsname()-release
avoids that this module is rebuild each
time the kernel version changes.
Compile tested only.
I vote
On Saturday 10 February 2007 17:22, Theodore Tso wrote:
> On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
> > Please hold all questions until I am done with this email. Thank you.
> >
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wireless
On Saturday 10 February 2007 17:22, Theodore Tso wrote:
On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
Please hold all questions until I am done with this email. Thank you.
We are pleased to announce the availability of a new driver for the
Intel PRO/Wireless 3945ABG
On Sunday 04 February 2007 07:26, Larry Finger wrote:
> What is true is that none of the OFDM rates work
> because of some unknown bug, probably in initialization. As a result, we are
> limited to a maximum
> data rate of 11Mbs, but it is still running in 802.11g mode!
That's also not true for
On Sunday 04 February 2007 07:26, Larry Finger wrote:
What is true is that none of the OFDM rates work
because of some unknown bug, probably in initialization. As a result, we are
limited to a maximum
data rate of 11Mbs, but it is still running in 802.11g mode!
That's also not true for me.
On Tuesday 30 January 2007 23:23, Lennart Sorensen wrote:
> On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
>
> And seems to do 802.11b only and screw up the eeprom settings so that
> the windows driver gets
On Tuesday 30 January 2007 23:23, Lennart Sorensen wrote:
On Tue, Jan 30, 2007 at 05:12:31PM -0500, Jeff Garzik wrote:
You mean the bcm43xx wireless driver that's been upstream for months?
And seems to do 802.11b only and screw up the eeprom settings so that
the windows driver gets confused
ed hangs on some systems not having an
FWH and thus also not having a respective RNG).
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
--- linux-2.6.20-rc4/drivers/char/hw_random/intel-rng.c 2006-11-29
22:57:37.0 +0100
+++ 2.6.20-r
systems not having an
FWH and thus also not having a respective RNG).
Signed-off-by: Jan Beulich [EMAIL PROTECTED]
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
--- linux-2.6.20-rc4/drivers/char/hw_random/intel-rng.c 2006-11-29
22:57:37.0 +0100
+++ 2.6.20-rc4-intel-rng-skip-fhw-detect/drivers
On Wednesday 03 January 2007 10:18, Jan Beulich wrote:
> Add a load option to intel-rng to allow skipping the FWH detection,
> necessary in case the BIOS has locked read-only the firmware hub space.
> Also prevent any attempt to write to firmware space if it cannot be
> write enabled (apparently
On Wednesday 03 January 2007 10:18, Jan Beulich wrote:
Add a load option to intel-rng to allow skipping the FWH detection,
necessary in case the BIOS has locked read-only the firmware hub space.
Also prevent any attempt to write to firmware space if it cannot be
write enabled (apparently
301 - 400 of 419 matches
Mail list logo
