On Sunday 27 November 2005 22:53, Larry Finger wrote:
Michael Buesch wrote:
On Sunday 27 November 2005 03:44, you wrote:
I am trying to help the bcm43xx project develop a driver for the
Broadcom 43xx wireless chips, using my Linksys WPC54G card.
Unfortunately, since the group got far
On Monday 28 November 2005 22:07, lothwen wrote:
Larry W. Finger wrote:
At 08:07 AM 11/28/2005, Michael Buesch wrote:
On Monday 28 November 2005 12:28, Jérémy Bobbio wrote:
On Sunday 27 November 2005 22:53, Larry Finger wrote:
At the moment, I am unable to load the bcm430x module
On Thursday 01 December 2005 15:27, Johannes Berg wrote:
It just occurred to me that two u8's for the data rates are not enough --
the fallback rate for broad-/multicast might not be what you want it to be
if that rate is not in the bssBasicRateSet. Thus, both should be lists of
rates.
On Sunday 04 December 2005 22:30, Saladino wrote:
Hi,
Sorry if my question is too basic, but ive not found any instructions
on how to compile softmac, i've just try with make after extracting
in my home but fails.
When i do make depend complains me about net/ieee80211softmac.h,
but below
Hi,
Daily snapshots of the BCM43xx driver are
now available at
ftp://ftp.berlios.de/pub/bcm43xx/snapshots/
The snapshots are generated at UTC 5:00am
(or should be, at least. :) Let's wait until tomorrow,
if I got the crontab correct.)
Have Fun.
PS: It seems like Distributions begin to ship the
Hi,
I ported the bcm43xx driver (http://bcm43xx.berlios.de) to the
devicescape ieee802.11 stack.
This port is a project branch, so softmac is still supported
and developed.
bcm43xx now supports software-side encryption functionality.
(The hardware supports encryption, but that's not completely
On Thursday 22 December 2005 18:49, Martin Tessun wrote:
Johannes Berg wrote:
On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
At least you get them inserted ;) When I try to modprobe rate_control I
get the following:
insmod 80211 first.
johannes
No, this ist not the
On Friday 23 December 2005 16:27, Ralf Hildebrandt wrote:
scheduling while atomic: bcm43xx_wq/0/0x0002/5827
[c031a026] schedule+0x566/0x630
[c012dbf5] worker_thread+0x295/0x2d0
^
Which kernel are you running?
Which architecture?
This is strange, because
On Tuesday 27 December 2005 10:43, Ralf Hildebrandt wrote:
scheduling while atomic: bcm43xx_wq/0/0x0001/5414
[c02fff55] schedule+0x585/0x640
[c01190ab] __wake_up+0x4b/0x80
[c012d725] worker_thread+0x255/0x290
[c0101ac9] __switch_to+0x19/0x220
[e0bb95a0]
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
On Sunday 01 January 2006 19:35, David Woodhouse wrote:
On Sun, 2006-01-01 at 08:54 -0600, Matteo Frigo wrote:
I would appreciate if other people could confirm whether
handle_irq_transmit_status() is called on their system, so that I can
try to further diagnose the problem.
It's not
On Sunday 01 January 2006 22:21, Matteo Frigo wrote:
Michael Buesch [EMAIL PROTECTED] writes:
You have a device with a wlcore rev 5, which uses
one DMA engine for TX status blobs.
This code is untested and indeed likely to be wrong.
I have no facilities to test it (neither has any
On Sunday 01 January 2006 23:52, you wrote:
This patch seems to do the trick. I am ignoring the
bcm43xx_rx_transmitstatus() mechanism and calling
bcm43xx_dma_handle_xmitstatus() directly.
Ok, very good. I will apply this patch and also remove
the dead bcm43xx_rx_transmitstatus code.
Thanks.
On Thursday 05 January 2006 03:05, Jory A. Pratt wrote:
bcm43xx: XMIT ERROR
bcm43xx: Generic Reason: 0x4d80
bcm43xx: DMA reasons:0x, 0x, 0x, 0x
bcm43xx: DMA TX status: 0x2000, 0x36802368, 0x2000, 0x2000
bcm43xx: XMIT ERROR
bcm43xx:
On Wednesday 11 January 2006 00:32, Carlo Marcelo Arenas Belon wrote:
On Tue, Jan 10, 2006 at 02:43:10PM -0600, Larry Finger wrote:
While reviewing the softmac version of r0utine bcm43xx_wx_get_rangeparams,
I found the following code snippit:
switch (bcm-current_core-phy-type)
On Wednesday 11 January 2006 03:13, Shreyas Ananthan wrote:
However, the script sta_up.sh caused the kernel to crash (can someone
tell me what to dump from xmon. I am not sure what information in
there is relevant).
That is simple. Everything is relevant.
All I can do with the information you
On Wednesday 18 January 2006 21:06, John W. Linville wrote:
The tree also has softmac and dscape branches. The softmac
branch includes the Johannes Berg softmac code as well as the the
BCM43xx driver based upon that code. The dscape branch includes
the DeviceScape patches from Jiri Benc as
Stefano, please go to the list admin page and remove the
useless [Bcm43xx-dev] prefix from the topic.
It messes up threads on reply. _Especially_ if foreign lists are CCed.
This annoys people.
Thanks.
--
Greetings Michael.
pgpYOj7Ul5yzn.pgp
Description: PGP signature
On Monday 30 January 2006 09:28, Jason Lunz wrote:
This patch contains the beginnings of ethtool support for bcm43xx.
Thanks, applied.
--
Greetings Michael.
pgptSTc3Lef15.pgp
Description: PGP signature
On Thursday 02 February 2006 15:36, David Woodhouse wrote:
On Mon, 2006-01-30 at 07:53 -0500, Dan Williams wrote:
On Mon, 2006-01-30 at 21:51 +1100, David Woodhouse wrote:
I believe the bcm43xx driver should support WPA.
Technically, yes. However, it needs a patch like the one attached
Please do a
git pull git://bu3sch.de/wireless-2.6 softmac-upstream
to pull latest bcm43xx updates into softmac-all:
Michael Buesch:
[bcm43xx] add DEBUG Kconfig option. Also fix indention.
[bcm43xx] Fix makefile. Remove all the out-of-tree stuff.
[bcm43xx] Add more initvals
Please do a
git pull git://bu3sch.de/wireless-2.6 dscape-upstream
to pull latest bcm43xx updates into dscape-all:
Michael Buesch:
[bcm43xx] add DEBUG Kconfig option. Also fix indention.
[bcm43xx] fix Kconfig depends on typo.
[bcm43xx] Fix makefile. Remove all the out-of-tree
On Saturday 04 February 2006 06:46, Larry Finger wrote:
On Jan. 14, I submitted a patch for softmac/bcm43xx that implemented the
get_wireless_stats call. To
date, I have not received any response to my patch. I use it with the
Wireless Network Information
applet in KDE to tell me when my
Index: bcm43xx_wx.c
===
--- bcm43xx_wx.c(revision 1113)
+++ bcm43xx_wx.c(working copy)
@@ -262,13 +262,13 @@
range-max_qual.qual = 100;
/* TODO: Real max RSSI */
- range-max_qual.level
On Sunday 05 February 2006 18:13, [EMAIL PROTECTED] wrote:
Do you also add support for linksys technology for improving signalstrenght
by using two or more antennas ?
I personally use a debian system with a Linksys WMP54G card.
Could you tell me if , and if yes , at what time , this
On Wednesday 08 February 2006 17:47, you wrote:
On Wed, Feb 08, 2006 at 03:18:24PM +0100, Michael Buesch wrote:
[...]
Well, I did not publish the URL on the homepage, because it is not
really needed for everyone to clone my repository.
Currently, there are all-in-one snapshots available
On Wednesday 08 February 2006 20:10, you wrote:
The new standalone isn't working for me. Compilation and syntax
errors all over the place - mostly near the error handling gotos.
Attached is the results of a compilation attempt.
I'm going to give a look at see if I can figure out the issue.
On Wednesday 08 February 2006 21:05, Joseph Jezak wrote:
Michael Buesch wrote:
On Wednesday 08 February 2006 18:20, you wrote:
Michael Buesch wrote:
Ok, I think your fix is more or less correct.
The original driver does not have any timeout in mac suspend. It just spins
until
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any obvious
effect either.
The set_xmitpower section is still a TODO.
On Saturday 11 February 2006 17:55, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any
On Saturday 11 February 2006 18:46, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:55, you wrote:
Michael Buesch wrote:
On Saturday 11 February 2006 17:22, Larry Finger wrote:
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem
On Wednesday 15 February 2006 20:21, you wrote:
This patch fixes an oops when bcm43xx-d80211 module is unloaded.
This is already fixed in my tree.
Signed-off-by: Jiri Benc [EMAIL PROTECTED]
--- dscape.testing.orig/drivers/net/wireless/bcm43xx-d80211/bcm43xx_main.c
2006-02-15
On Wednesday 15 February 2006 17:58, Larry Finger wrote:
What has happened to the wireless statistics patch for bcm43xx-softmac? I
keep having to reapply it
every time I get a new copy.
Attached is a fresh copy of the patch rediffed against the 060215 snapshot.
I am sorry. I thought I did
On Thursday 16 February 2006 10:35, you wrote:
On Wed, 15 Feb 2006 22:34:35 +0100, Michael Buesch wrote:
On Wednesday 15 February 2006 20:21, you wrote:
This patch fixes an oops when bcm43xx-d80211 module is unloaded.
This is already fixed in my tree.
Is the tree available somewhere
On Thursday 16 February 2006 04:09, Larry Finger wrote:
The current version of the bcm43xx-softmac driver scans 14 channels, even
though channels greater
than 11 are not permitted in the US and Canada. Similarly only channels 1-13
are allowed in Europe.
AFAIK, channel 14 is only allowed
On Thursday 16 February 2006 16:08, Larry Finger wrote:
I agree, but placed the patch where I did because I couldn't find any code in
ieee80211 that even
sets frequencies.
I will formulate a patch that puts the domain regulations into ieee80211 and
submit it to Linville,
then suggest
On Thursday 16 February 2006 21:25, Andrea Lusuardi - UoVoBW wrote:
Hi everyone,
i'm back with one of possibly stupid questions of mine.
I have a wireless net at home, and i want to understand if, with a
standard card, it is possibile to get inside my WLAN.
I've been walking around my house
On Friday 17 February 2006 17:28, Daniel Gryniewicz wrote:
On Fri, 2006-02-17 at 11:11 +0100, Michael Buesch wrote:
Hi,
I got complaints from people, that the driver does
not compile cleanly on a 64bit arch. But I can not
fix this, because I don't have a 64bit machine.
So, someone
On Tuesday 21 February 2006 15:50, you wrote:
It is still the wrong firmware directory.
Read your distro's documentation on where to put firmware.
I think I have corrected this issue (I have made symlinks
in /usr/lib/hotplug/firmware too).
Now the script says:
On Tuesday 21 February 2006 16:41, you wrote:
http://bu3sch.de/git?p=wireless-2.6.git;a=blob;h=6d5384008f944bb9a7ec1650426c6fcfb3e9f6ef;hb=dscape;f=Documentation/networking/bcm43xx-d80211-HOWTO.txt
You can optionally try with -Dwext. That _should_ be supported, too,
without patching. But I
possible.
A patch against bcm43xx for your testing pleasure can be found at:
ftp://ftp.bu3sch.de/misc/bcm43xx-d80211-hwrng.patch
Oops, I forgot:
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Sorry.
--
Greetings Michael.
pgpEJGwIxaaig.pgp
Description: PGP signature
On Wednesday 01 March 2006 03:57, you wrote:
Hi, I'll email you the patchset off-list so you can look at the API
and write the bcm43xx driver against it. They are a few months old
and
need updating to 2.6.latest and it is on my 2.6.18 TODO. If you
search the
archives there were a
Hi John,
It took a little longer than promised, but a broken harddisk in
my server delayed my plans. ;)
Please pull branches softmac-upstream and dscape-upstream
from my repository at:
git://bu3sch.de/wireless-2.6.git
This introduces the following changesets:
Michael Buesch:
bcm43xx
Please, don't waste your time by doing experiments with
the 4318 device, yet.
== It is broken.
== We _know_ that.
And we are in the progress to fix this.
I will announce on this mailing list, when the driver
is ready for testing on the 4318. Until this announcement,
please _don't_ send 4318
On Sunday 02 April 2006 18:11, Jon Masters wrote:
On 4/2/06, Jon Masters [EMAIL PROTECTED] wrote:
I have to sometimes do an extra ifconfig up to turn the radio on
again and I have seen one lockup so far - so it's not all perfect,
David: FYI, my kernel locked hard over at MIT yesterday. I
On Friday 07 April 2006 18:59, Rafael J. Wysocki wrote:
Hi,
I've just tried the version of the driver included in 2.6.17-rc1 on an
x86_64 box (Asus L5D) with a built-in PCI BCM4306 adapter (Broadcom
Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)), and
unfortunately it doesn't
This reduces codesize.
--- a/drivers/net/wireless/bcm43xx/bcm43xx.h
+++ b/drivers/net/wireless/bcm43xx/bcm43xx.h
@@ -648,7 +648,6 @@ struct bcm43xx_private {
unsigned int irq;
void __iomem *mmio_addr;
- unsigned int mmio_len;
/* Do not use the lock directly. Use
Hi,
I looked into the symbol clash problems between bcm43xx and bcm43xx-d80211
you mentioned at the wireless summit.
Well, IMHO it is pretty hard to find a good solution to this.
The situation is: We have several nonstatic functions in the bcm driver. These
functions have the same name in the
diff --git a/drivers/net/wireless/bcm43xx-d80211/bcm43xx_main.c
b/drivers/net/wireless/bcm43xx-d80211/bcm43xx_main.c
index 043a5cf..f0f4f78 100644
--- a/drivers/net/wireless/bcm43xx-d80211/bcm43xx_main.c
+++ b/drivers/net/wireless/bcm43xx-d80211/bcm43xx_main.c
@@ -4128,15 +4128,19 @@ static int
On Tuesday 11 April 2006 03:46, you wrote:
Yes, I know they hit the message, that's from a message in some forum
that i got interested in the issue. It probably comes from an allocation
from:
http://www.linux-m32r.org/lxr/http/source/arch/powerpc/kernel/pci_direct_iommu.c#L32
Either
On Tuesday 11 April 2006 07:49, you wrote:
From: Benjamin Herrenschmidt [EMAIL PROTECTED]
Date: Tue, 11 Apr 2006 11:46:12 +1000
But ppc64 hits the problem and at this point, there is nothing
I can do other than either implementing a split zone allocation mecanism
in the ppc64
On Tuesday 11 April 2006 08:39, Johannes Berg wrote:
On Mon, 2006-04-10 at 02:16 +0200, Michael Buesch wrote:
Does kbuild perhaps have some magic to handle that?
This needs to be solved soon, but I have no idea how.
You want to have bcm43xx and bcm43xx-dscape conflict anyway, since
On Tuesday 11 April 2006 18:42, Johannes Berg wrote:
On Tue, 2006-04-11 at 18:35 +0200, Michael Buesch wrote:
Sure. I would probably say that both m should conflict, too.
Nah, you probably want both m for testing.
I am OK with this, but it fucks up module autoloading.
But that is probably
On Wednesday 12 April 2006 00:21, you wrote:
I still think we shouldn't reward shit hardware by complicating
up our DMA mappings internals. :-)
BTW. In the meantime, can't that driver work in PIO only mode ?
No, because I did not finish debugging that, yet. ;)
And a second half-no,
This should also go in before 2.6.17
---
This cleans up the bcm43xx sysfs code and makes it compliant
with the unwritten sysfs rules (at least I hope so).
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/bcm43xx/bcm43xx.h
On Sunday 16 April 2006 21:09, Marc Singer wrote:
I'm using a 3 year old notebook computer with a built-in BCM 4306
chip. When I turn-up the interface, I see this in the dmesg log.
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: Chip initialized
bcm43xx: DMA initialized
Hi John,
I already sent these three patches for inclusion into
the softmac version of the driver. Here are the devicescape
port versions for inclusion in your wireless-dev tree.
--
Greetings Michael.
Index: wireless-dev-ds/drivers/net/wireless/bcm43xx-d80211/bcm43xx.h
On Saturday 22 April 2006 17:18, you wrote:
bcm43xx_lock_mmio(bcm, flags);
+
+ txctl = bcm43xx_pio_read(queue, BCM43xx_PIO_TXCTL);
+ if (txctl BCM43xx_PIO_TXCTL_SUSPEND)
+ return;
Ah, and yes, I see the bug here. :)
But that normally does not trigger anyway. So no
-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
===
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
2006-04-11 06:26:46.0 +0200
+++ wireless-2.6/drivers/net
On Sunday 30 April 2006 06:33, Matej Cepl wrote:
Hi,
I have upgraded my kernel to 2.6.17-rc3 (on Debian/unstable) and
found that native driver (THANKS!!!) works just on every other
reboot. So, for example attached /var/log/messages contains
couple of oopses and other problems.
Can
Hi,
Jiri, please review this patch for things that might look
strange to you. :)
--
This replaces the bcm43xx-d80211 virtual interfaces hack by
a correct implementation with support for monitor during oper.
Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h
This should go into 2.6.17, as it fixes a user exploitable crash.
--
This fixes a crash when
iwconfig ethX mode foo
is done before
ifconfig ethX up
or after
ifconfig ethX down
Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_wx.c
(Second attempt, now unmangled and with signed-off-by line, uh...)
This should go into 2.6.17, as it fixes a user exploitable crash.
--
This fixes a crash when
iwconfig ethX mode foo
is done before
ifconfig ethX up
or after
ifconfig ethX down
Signed-off-by: Michael Buesch [EMAIL PROTECTED
Hi John,
This is not really a patch, because it is easier for you
to do it manually. :)
Please remove the file
scripts/bcm43xx-d80211-sta_up.sh
from the wireless-dev tree, as the d80211 user interface has
been fixed and it is not really needed anymore.
While you are at it, please also remove
Hi John,
Please apply to wireless-dev.
--
Rewrite the virtual interface handling.
With this monitor_during_oper is made possible.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h
Measure the channel change time with the
bcm43xx tsf timer and remove the guesswork constant. ;)
Tests on my 4306 show that the time comes damn
close to reality.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
expectations, by
using the proper constants.
Signed-off-by: Jean Delvare [EMAIL PROTECTED]
[mb]: Reduce stack usage by kzalloc-ing ieee80211_geo
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
John, this is the same patch as before, but for d80211.
Please apply to wireless-dev.
--
Fix the conditions under which we poke at the APHY registers in
bcm43xx_phy_initg() to avoid a machine check on chips where they don't
exist.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
diff --git
On Friday 05 May 2006 20:18, you wrote:
On Fri, 2006-05-05 at 19:42 +0200, Michael Buesch wrote:
Signed-off-by: David Woodhouse [EMAIL PROTECTED]
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
John, please apply. I will also send a patch for d80211.
Would be good to get
On Friday 05 May 2006 21:59, Stefano Brivio wrote:
Fix whitespace.
Signed-off-by: Stefano Brivio [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===
---
This patch series replaces the old non-generic Hardware Random Number Generator
support by a fully generic RNG API.
This makes it possible to register additional RNGs from modules. With this
patch series applied, Laptops with
a bcm43xx chip (PowerBook) have a HW RNG available now.
Additionally
Remove the old H/W RNG support.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/Kconfig
===
--- hwrng.orig/drivers/char/Kconfig 2006-05-07 01:29:34.0 +0200
+++ hwrng/drivers/char/Kconfig 2006-05
Add a new generic H/W RNG core.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/Kconfig
===
--- hwrng.orig/drivers/char/Kconfig 2006-05-07 01:35:45.0 +0200
+++ hwrng/drivers/char/Kconfig 2006-05
Add a driver for the x86 RNG.
This driver is ported from the old hw_random.c
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-07
Add ixp4xx H/W RNG driver.
Driver written by Deepak Saxena.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-07 01:51:25.0
Add bcm43xx H/W RNG support.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/net/wireless/bcm43xx/Kconfig
===
--- hwrng.orig/drivers/net/wireless/bcm43xx/Kconfig 2006-05-07
01:53:13.0 +0200
+++ hwrng
On Sunday 07 May 2006 07:45, Alexander V. Tsvyashchenko wrote:
not really matter for this patch to work, the main reason I had to add
interfaces handling was to allow more than one
interface to be brought up (this is required for hostapd)
Why does hostapd require more than one interface per
On Sunday 07 May 2006 15:03, you wrote:
This does not handle the case of partial read correctly - the code
should be
return ret ? : -ERESTARTSYS;
+ if (!current_rng) {
+ mutex_unlock(rng_mutex);
+ return -ENODEV;
Remove the old H/W RNG support.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/Kconfig
===
--- hwrng.orig/drivers/char/Kconfig 2006-05-07 01:29:34.0 +0200
+++ hwrng/drivers/char/Kconfig 2006-05
Add a driver for the x86 RNG.
This driver is ported from the old hw_random.c
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-07
Add ixp4xx H/W RNG driver.
Driver written by Deepak Saxena.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-07 15:50:22.0
Add bcm43xx H/W RNG support.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/net/wireless/bcm43xx/Kconfig
===
--- hwrng.orig/drivers/net/wireless/bcm43xx/Kconfig 2006-05-07
15:47:21.0 +0200
+++ hwrng
On Sunday 07 May 2006 17:22, you wrote:
On Sun, May 07, 2006 at 04:38:09PM +0200, Michael Buesch wrote:
Add a driver for the x86 RNG.
This driver is ported from the old hw_random.c
[skip]
+static int __init intel_init(struct hwrng *rng)
Cannot be __init anymore - now rng-init could
On Sunday 07 May 2006 20:39, you wrote:
On Sunday 07 May 2006 16:38, Michael Buesch wrote:
Second try. Various fixes included. This does even compile (and work) now.
:)
It would be good to give the patches more descriptive names, currently
they all have the same subject lines, which
On Friday 12 May 2006 13:05, you wrote:
[EMAIL PROTECTED] wrote:
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-08
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/Kconfig
===
--- hwrng.orig/drivers/char/Kconfig 2006-05-07 01:29:34.0 +0200
+++ hwrng/drivers/char/Kconfig 2006-05-07 01:35:45.0 +0200
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-14 16:06:53.0
+0200
+++ hwrng/drivers/char/hw_random/Kconfig2006
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/Kconfig
===
--- hwrng.orig/drivers/char/Kconfig 2006-05-07 01:53:30.0 +0200
+++ hwrng/drivers/char/Kconfig 2006-05-07 01:55:11.0 +0200
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-08 00:15:58.0
+0200
+++ hwrng/drivers/char/hw_random/Kconfig2006
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-08 00:12:08.0
+0200
+++ hwrng/drivers/char/hw_random/Kconfig2006
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/net/wireless/bcm43xx/Kconfig
===
--- hwrng.orig/drivers/net/wireless/bcm43xx/Kconfig 2006-05-12
12:07:13.0 +0200
+++ hwrng/drivers/net/wireless/bcm43xx
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng/drivers/char/hw_random/Kconfig
===
--- hwrng.orig/drivers/char/hw_random/Kconfig 2006-05-14 16:12:02.0
+0200
+++ hwrng/drivers/char/hw_random/Kconfig2006
I will send patches for the following stuff, on top
of your current -mm, which has my previous patches applied.
On Tuesday 16 May 2006 00:02, you wrote:
Michael Buesch [EMAIL PROTECTED] wrote:
+static inline
+int hwrng_init(struct hwrng *rng)
+static inline
+void hwrng_cleanup(struct
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng.fixes/drivers/char/hw_random/core.c
===
--- hwrng.fixes.orig/drivers/char/hw_random/core.c 2006-05-16
21:50:04.0 +0200
+++ hwrng.fixes/drivers/char/hw_random
Cleanup some nonsense and codingstyle related stuff.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng.fixes/drivers/char/hw_random/core.c
===
--- hwrng.fixes.orig/drivers/char/hw_random/core.c 2006-05-16
20:37
cpu_has_xstore only exists on X86_32 (for now).
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: hwrng.fixes/drivers/char/hw_random/Kconfig
===
--- hwrng.fixes.orig/drivers/char/hw_random/Kconfig 2006-05-16
20:37
On Thursday 25 May 2006 04:29, Daniel Gryniewicz wrote:
On Fri, 2006-05-19 at 22:38 -0400, Daniel Gryniewicz wrote:
Just a heads up: I have a bcm4318, and today I upgraded from 1GB of RAM
to 2GB. Now, whenever the interface goes up, the machine panics. This
happens with my current
On Thursday 25 May 2006 16:16, Jason Lunz wrote:
On Thu, May 25, 2006 at 02:02:37PM +0200, Michael Buesch wrote:
Uh, don't let me dangling like this. :)
Could you please try to reproduce the lockup and catch
an oops? It's important, because it may be caused by bcm43xx.
I will, but I've
On Sunday 28 May 2006 18:37, you wrote:
On Sun, May 28, 2006 at 06:29:01PM +0200, Michael Buesch wrote:
Well, I would like to know it for sure. ;)
Could you load the kernel which crashed and look there. It is
quite important to know if it is caused by a shared IRQ or not.
OK, i'm running
On Monday 29 May 2006 22:40, you wrote:
On Monday 29 May 2006 17:51, you wrote:
On Mon, May 29, 2006 at 12:44:05AM +0200, Michael Buesch wrote:
Ok Jason, could you please test the following patch and try to reproduce
with it?
This patch crashes immediately:
http://gehennom.net
1 - 100 of 1753 matches
Mail list logo
