On Tuesday 23 March 2010 00:45:28 Larry Finger wrote:
(2) In drivers/ssb/pci.c, the firmware loading process reads the file, then
modifies it using the bus address.
No. You don't need firmware loading at all.
udev can just set the mac address through the standard ioctl calls.
Just like how
On Tuesday 23 March 2010 09:55:39 Florian Fainelli wrote:
Why not use random_ether_addr and only use the digits that you are interested
in?
Because it's not constant across reboots.
--
Greetings, Michael.
___
Bcm43xx-dev mailing list
On 03/23/2010 03:52 AM, Michael Buesch wrote:
On Tuesday 23 March 2010 00:45:28 Larry Finger wrote:
(2) In drivers/ssb/pci.c, the firmware loading process reads the file, then
modifies it using the bus address.
No. You don't need firmware loading at all.
udev can just set the mac address
Some recent BCM43XX devices lack an on-board SPROM. The pertinent data
from the SPROM could be included in the kernel; however, this presents
a problem in the generation of a unique, reproducible MAC address. The
solution is to use a file in /lib/firmware/ssb, which has some random
information
On 03/22/2010 09:57 PM, Frank Middleton wrote:
Had some really great experiences with your software recently, especially
using a public Wifi system with really weak/out of range signals. I could
still get emails even when Windows couldn't find any unencrypted APs,
and it worked like a champ
Hi,
I had a perfectly working Dell system running Windows Vista and using
version 5.60.188.1 of the Broadcom windows driver (distributed by
Dell) for what Windows calls the Dell Wireless 1397 WLAN Mini-Card,
which is actually 14e4:4315.
I booted Parted Magic 4.9 from a USB flash drive, which
On 03/23/2010 02:30 PM, Chris Lopes wrote:
Hi,
I had a perfectly working Dell system running Windows Vista and using
version 5.60.188.1 of the Broadcom windows driver (distributed by
Dell) for what Windows calls the Dell Wireless 1397 WLAN Mini-Card,
which is actually 14e4:4315.
I booted
On 03/23/2010 02:53 PM, Chris Lopes wrote:
Thanks for the quick reply. So are you saying that it is impossible
that the b43 driver could have somehow made my wireless card unable to
detect any networks after a reboot (in either Windows or Linux)?
I don't know of any way that b43 could have
Ok. I got my wireless card to detect networks again. I also had a
theory and tried to reproduce the problem, and was successful in doing
so. Here are my steps to reproduce:
1) Have Vista running and connected to a wireless network
2) Hibernate Vista
3) Boot Parted Magic from a USB drive
4)
On 03/23/2010 03:31 PM, Chris Lopes wrote:
Ok. I got my wireless card to detect networks again. I also had a
theory and tried to reproduce the problem, and was successful in doing
so. Here are my steps to reproduce:
1) Have Vista running and connected to a wireless network
2) Hibernate
What does (or might) Wake On LAN have to do with this problem, exactly?
2010/3/24 Larry Finger larry.fin...@lwfinger.net:
On 03/23/2010 03:31 PM, Chris Lopes wrote:
Ok. I got my wireless card to detect networks again. I also had a
theory and tried to reproduce the problem, and was successful
The wireless access point (AP), also sometimes called a router, is not
relevant to my problem. It was not the cause and it did not need to
be rebooted.
My problem was not one of connectivity, per se. My wireless card was
unable to see any SSID's (networks), including ones that are always
present
On Tuesday 23 March 2010 21:58:22 Calvin Walton wrote:
On Tue, 2010-03-23 at 09:25 -0500, Larry Finger wrote:
Will someone please write me udev rule(s) that do the following:
1. Detect a MAC address of FF:FF:FF:FF:FF:FF
2. If this is the first time for this bus address, then generate a
On Wed, 24 Mar 2010 03:31:42 +0700
Chris Lopes clo...@gmail.com wrote:
Ok. I got my wireless card to detect networks again. I also had a
theory and tried to reproduce the problem, and was successful in doing
so. Here are my steps to reproduce:
1) Have Vista running and connected to a
I didn't try a cold reboot that did not involve the removal of
battery and power supply, so maybe it would work.
Honestly I am still perplexed (given modern hardware and software), as
to why/how:
1) Hibernate and un-hibernate, regardless of what happens in between
with the wireless card, could
On Tue, Mar 23, 2010 at 11:23 PM, Chris Lopes clo...@gmail.com wrote:
I didn't try a cold reboot that did not involve the removal of
battery and power supply, so maybe it would work.
Honestly I am still perplexed (given modern hardware and software), as
to why/how:
1) Hibernate and
On Tue, 23 Mar 2010 23:37:45 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
(On 2.6.33, b43 works around this by falling back to PIO.)
I think it requires 2.6.34 for this (currently 2.6.34-rc2).
Chris
___
Bcm43xx-dev mailing list
On Mon, 22 Mar 2010 20:54:14 -0400
Celejar cele...@gmail.com wrote:
Hi,
I have been using my 4318 successfully with b43 (thanks, Michael and
all devs / reverse engineers!) for many kernel revisions now, both as a
client, as well as in monitor mode (kismet, airodump). With
2.6.34-rc1, I
Michael Buesch wrote:
On Monday 22 March 2010 22:56:44 Larry Finger wrote:
Does anyone have any suggestions on what characteristic could be used to
generate a unique MAC address for a box in a udev rule?
/dev/urandom
Yeah, there's the chance of clashes. In practice there won't be
19 matches
Mail list logo
