On Monday 22 March 2010 07:28:23 Calvin Walton wrote:
Hi,
On Sat, 2010-03-20 at 19:14 -0500, Larry Finger wrote:
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
On 03/22/2010 03:37 AM, Michael Buesch wrote:
On Monday 22 March 2010 07:28:23 Calvin Walton wrote:
Hi,
On Sat, 2010-03-20 at 19:14 -0500, Larry Finger wrote:
Some recent BCM43XX devices lack an on-board SPROM. The pertinent data
from the SPROM could be included in the kernel; however, this
On 03/22/2010 04:55 PM, Michael Buesch wrote:
I don't see a problem for udev to distinguish the cards. It can do it merely
on
the bus-ID. That's unique. Yeah, it might change if you change the hardware.
But do we care? I say no, because you cannot actually change the hardware in
real life
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 any clashes,
however. If you think
On Monday 22 March 2010 23:19:54 Larry Finger wrote:
On 03/22/2010 04:55 PM, Michael Buesch wrote:
I don't see a problem for udev to distinguish the cards. It can do it
merely on
the bus-ID. That's unique. Yeah, it might change if you change the hardware.
But do we care? I say no,
Michael,
Would the following be sufficient?
(1) The utility /bin/dbus-uuidgen is used to create a file
/lib/firmware/ssb/mac_address. The command to create this file if it does not
exist could be added to the scripts that use fwcutter.
(2) In drivers/ssb/pci.c, the firmware loading process
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 can't get monitor mode to work successfully - I get
errors like this:
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 even at one site where there were 14 APs.
FWIW it