[Bcm43xx-dev] sprommod.sh convenience
This little convenience change in sprommod.sh allows you to call sprommod.sh eth1 --all --verbose (not in the other order, but that will give an error). I thought it was easier to add this to sprommod.sh instead of the C tool. It relies on the fact that all gettable options are printed out as [beginning of line][space][space]--option[space][ignored stuff] This might be useful when we want to see the sprom values people have... johannes --- sprom.orig/sprommod.sh +++ sprom/sprommod.sh @@ -11,6 +11,12 @@ device=$1 shift +args=$@ +if [ $1 = --all ] ; then + shift + args=`bcm43xx_sprom --help 21| sed 's/ \(--[^ ]*\).*/\1 GET/;t;d' | tr '\n' ' '` $@ +fi + if [ -z $device ]; then echo No DEVICE given exit 1 @@ -22,7 +28,7 @@ echo Could not read SPROM ($err) exit 1 fi -mod_data=$(echo $orig_data | bcm43xx_sprom $@) +mod_data=$(echo $orig_data | bcm43xx_sprom $args) err=$? if [ $err -ne 0 ]; then echo Could not modify SPROM data ($err) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bcm43xx-dev] wireless: the contenders
On Wed, 2006-01-18 at 15:06 -0500, 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. I guess that branch also contains my enhancements to ieee80211, do you have any intentions of pulling those over to your upstream tree? I suppose I should rather post them as a series of patches to netdev for wider consideration. johannes signature.asc Description: This is a digitally signed message part
Re: [Bcm43xx-dev] wireless: the contenders
On Thu, Jan 19, 2006 at 01:19:40AM +0100, Johannes Berg wrote: On Wed, 2006-01-18 at 15:06 -0500, 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. I guess that branch also contains my enhancements to ieee80211, do you have any intentions of pulling those over to your upstream tree? I suppose I should rather post them as a series of patches to netdev for wider consideration. I pulled from the softmac-2.6.git tree. I think there was ieee80211 stuff in there as well, but you probably know better than I do. :-) The history in your tree isn't formatted properly for the kernel, so something would have to be done before that went upstream anyway. I think it would be best for you to post the patches to netdev, including patches covering softmac if you are so inclined. Please be sure to follow kernel patch posting conventions: http://linux.yyz.us/patch-format.html Thanks, John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bcm43xx-dev] Interface name
On 1/19/06, Kyle Moffett [EMAIL PROTECTED] wrote:
On Jan 18, 2006, at 13:47, Lorenzo Milesi wrote:
You can use ifrename or edit /etc/udev/rules.d/30-
net_persistent_names.rules?
udev rule to rename iface:
#wifi broadcomm
KERNEL=eth*, SYSFS{address}=00:13:aa:bb:cc:dd, name=bcm0
On my PowerMac, I also rename my eth1394 interface based on SYSFS
{device/../../devspec} (effectively a hardware path given by
OpenFirmware), and the builtin ethernet interface similarly, because
I occasionally change those addresses in the firmware.
You can also use NAME=net_wfi, or net_bcm, or
some_unusual_broadcom_wireless_interface if you feel like it. You
just have to remember what name you use so you can stick it in your
ifupdown config (or whatever your distro uses).
i confgured hotplug to change the order modules are loaded added a
file in /etc/modprobe.d/ containig this line:
install bcm43xx /sbin/modprobe sungem; /sbin/modprobe eth1394;
/sbin/modprobe --ignore-install bcm43xx
(all on the same line :-))
(owning a pb, sungem is my wired eth driver)
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[Bcm43xx-dev] /proc/net/wireless?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a reason we are not registering device completely yet? Main reason behind me finding this is I can not use my normal network configuration without an entry being in /proc/net/wireless. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD0Bm3GDfjNg8unQIRAsU9AJ99aK5lny0mFCQmoadU8tsjqX+PrwCgiUew mUBcY5P1neX+jwb4XF2oTc4= =2vJV -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
