Garrett D'Amore ??: > Michael Li wrote: >> Garrett D'Amore ??: >> >>> Michael Li wrote: >>> >>>> Neal Pollack ??: >>>> >>>>> neha goel wrote: >>>>> >>>>>> the result of all the three commands is given >>>>>> below................ plz help me out >>>>>> >>>>> here is your problem/bug/virus: >>>>> Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card >>>>> >>>>> Try replacing that module with a supported Atheros or Intel part. >>>>> ebay is your friend. >>>>> Broadcom is *not* >>>>> >>>> Absolutely agree with what Neal mentioned, Broadcom is not friently >>>> with Opensource Community. I am investigating Broadcom 43xx native >>>> driver(bwi) in BSD world as well, it seems bwi is still in very >>>> early stage in chipsets coverage and quality, it is not a good time >>>> point to bring it to Solaris, I think. >>>> If anyone has some good news about bwi or Broadcom, please let me >>>> know. >>>> >>> <The following remarks are my own, and don't necessarily represent >>> the views of my employer.> >>> >> I would like to borrow above statement for my comments below: >> >>> I almost object to having a reverse engineered bwi in principle. The >>> basis for this is not that I'm opposed to reverse engineering, but >>> that if bwi ever reaches the point of usability, it will allow >>> people to continue to use these broadcom WLAN parts despite the fact >>> that broadcom has done everything it can to make it impossible for >>> anyone to use their parts on anything other than Windows. >>> >>> Put another way, I object on a matter of principle to allowing sales >>> of these NICs to continue for use in our platform. I'd feel totally >>> different if broadcom were able to offer even limited technical >>> specs so that design of OSS software could proceed without >>> extraordinary measures like those undertaken by bwi or NDIS. >>> >> gdamore, I can understand your pain on OSS project from PSARC >> discussion. >> > In case it was clear, by OSS I really meant FOSS -- free and open > source software. > >> Before I "+1" to support the "wonderful" activities happen, we need >> to think for those people that have already paid for some hardware >> from vendors like Broadcom but has no chance to replace it without >> additional charge, such user is not a small amount, that's why we >> trying to find a better solution from software side as a S/W >> Engineer. $10 is also money. :-) >> > > $10 is money, yes. But at the end of the day, is it better for those > people to have purchased an alternative and supportable WLAN NIC, or > is it better for them to have a part-way functional, unsupportable > product? Sometimes, we need to help people see where decisions may be > penny-wise, but pound-foolish. When $10x10000... it is not a samll amount. When I walk in the street, no one will give me even $1 forwardly, if I ask them money, they will call police mostly. I am afraid what we can do really is to try to make Solaris s/w fit for all the situation. I believe you are not first person want to throw away broadcom WLAN NIC, but most people are thinking why it is so hard to get their support, while Microsfot can. say something is easy than do something that one can do. Follow your idea, I am not sure how many hardwares or something else we should give up, I believe Broadcom WLAN should not be the first. It's more appropriate to send your prosoal to Bigger Opensource commnunity, I think. > > > Sometimes software engineers need to look beyond their immediate > project to the larger picture. I think this is one of those cases. > While the work on NDIS wrapper and reverse engineering projects may be > technically interesting, and it may allow some users to hobble along, > at the end of the day, I think the efforts actually become a > disservice to the larger community, and maybe even to the users whom > you are trying to enable. (Its also important to note that NDIS > wrapper and the reverse engineering work will never be suitable for > mainstream distributions, because of the very shaky legal ground on > which they stand.) NDISwrapper doesn't equal to reverse engineering project, don't mess them together, although it seems our current ndiswrapper has similar focus as bwi, cur status was determined by Sun's strategy. I will be more than happy to see community's contribution on ndiswrapper, since it is really a big project in opensource community, and, OpenSolaris doesn't equal to available Solaris product! Google "ndiswrapper" you can get 1,200,000 records, while "ndiswrapper + solaris" get 91,000 records(google.cn), it looks NDIS/Solaris port is on the way to be an important part of OpenSource communtiy, although we just provided/enabled part functions in it with our limited resource. I have said I am also looking for better solution for bcm43xx and even other unsupported WiFi adapter, which doesn't means the solution will be limited in a driver or just by ndiswrapper, I believe there are much works have already been done by Sun's SUPPORTABLE S/W product, although the original goal is not for bcm43xx. However, by now, I can't guarantee anything before I have really understand the deliverbility.
- Michael > > I have two dreams. In one of them, Broadcom has given up, and > supplied the community specifications or source code, and we all > rejoice because we are able to develop a first class Solaris driver > for their parts. Broadcom is cheered as an Open Source partner in > this dream. > > In the other dream, there is a great big bonfire, and people have > lined up to throw their Broadcom WLAN parts into the fire. There are > literally millions of the parts, and blaze reaches ever higher. > People are dancing around the fire half naked, chanting "Down with > Broadcom!" > > I don't know if either dream will come to pass, but I can't stop > dreaming... Certainly if Broadcom doesn't like the second, then they > have the power to prevent it by enabling the first. Right now though, > they are not motivated to change their practice at all. > > -- Garrett >> just my 2 cents, >> Michael >> >>> By the way, for much the same reason I *hate* the NDIS hacks that >>> some people use. Yeah, it sort of works. But not very well in many >>> cases, and the very fact that the NDIS hack was created is a >>> testament to the fact that Broadcom is *impossible* to work with. >>> >>> I think it would be *wonderful* if everyone who is current limping >>> along with an NDIS hack for borgcom NICs sent them back to their >>> supplier, and publicly promised to refuse to buy any more products >>> containing broadcom WLAN parts until Broadcom figures out how to >>> enable open source developers to write drivers for their parts. >>> (Hell, I'd even settle for a redistributable *closed* source solution!) >>> >>> If you are even *thinking* of purchasing a mobile computer, please >>> tell your supplier that you will not purchase any model with a >>> broadcom WLAN part. (If you want to support OpenSolaris, please do >>> this even *if* you will be using the mobile computer with another >>> operating system!) The only way for Borgcom to feel the pain is to >>> get people to boycott them indirectly through laptop vendors. If >>> Toshiba, IBM, Gateway, and Dell were to stop purchasing Borgcom >>> parts because they were losing sales due to their presence in units, >>> then I suspect Borgcom would start rethink their open source >>> strategy for WLAN parts. (Or they would fade away into irrelevance. >>> Either result is perfectly acceptable in my opinion.) >>> >>> -- Garrett >>> >>> >>>> - Michael >>>> >>>>>> # svcadm enable nwam >>>>>> >>>>>> # /usr/X11/bin/scanpci >>>>>> >>>>>> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device >>>>>> 0x27a0 >>>>>> >>>>>> Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express >>>>>> Memory Controller Hub >>>>>> >>>>>> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device >>>>>> 0x27a2 >>>>>> >>>>>> Intel Corporation Mobile 945GM/GMS/940GML Express Integrated >>>>>> Graphics Controller >>>>>> >>>>>> pci bus 0x0000 cardnum 0x02 function 0x01: vendor 0x8086 device >>>>>> 0x27a6 >>>>>> >>>>>> Intel Corporation Mobile 945GM/GMS/940GML Express Integrated >>>>>> Graphics Controller >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device >>>>>> 0x27d8 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) High Definition Audio >>>>>> Controller >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device >>>>>> 0x27d0 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1c function 0x02: vendor 0x8086 device >>>>>> 0x27d4 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1c function 0x03: vendor 0x8086 device >>>>>> 0x27d6 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device >>>>>> 0x27c8 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) USB UHCI #1 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1d function 0x01: vendor 0x8086 device >>>>>> 0x27c9 >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) USB UHCI #2 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1d function 0x02: vendor 0x8086 device >>>>>> 0x27ca >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) USB UHCI #3 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1d function 0x03: vendor 0x8086 device >>>>>> 0x27cb >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) USB UHCI #4 >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1d function 0x07: vendor 0x8086 device >>>>>> 0x27cc >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1e function 0x00: vendor 0x8086 device >>>>>> 0x2448 >>>>>> >>>>>> Intel Corporation 82801 Mobile PCI Bridge >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device >>>>>> 0x27b9 >>>>>> >>>>>> Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1f function 0x01: vendor 0x8086 device >>>>>> 0x27df >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) IDE Controller >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device >>>>>> 0x27c4 >>>>>> >>>>>> Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage >>>>>> Controller IDE >>>>>> >>>>>> pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device >>>>>> 0x27da >>>>>> >>>>>> Intel Corporation 82801G (ICH7 Family) SMBus Controller >>>>>> >>>>>> pci bus 0x0005 cardnum 0x00 function 0x00: vendor 0x14e4 device >>>>>> 0x4311 >>>>>> >>>>>> Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card >>>>>> >>>>>> pci bus 0x0008 cardnum 0x08 function 0x00: vendor 0x8086 device >>>>>> 0x1092 >>>>>> >>>>>> Intel Corporation PRO/100 VE Network Connection >>>>>> >>>>>> pci bus 0x0008 cardnum 0x09 function 0x00: vendor 0x1180 device >>>>>> 0x0832 >>>>>> >>>>>> Ricoh Co Ltd Device unknown >>>>>> >>>>>> pci bus 0x0008 cardnum 0x09 function 0x01: vendor 0x1180 device >>>>>> 0x0822 >>>>>> >>>>>> Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter >>>>>> >>>>>> pci bus 0x0008 cardnum 0x09 function 0x02: vendor 0x1180 device >>>>>> 0x0843 >>>>>> >>>>>> Ricoh Co Ltd Device unknown >>>>>> >>>>>> pci bus 0x0008 cardnum 0x09 function 0x03: vendor 0x1180 device >>>>>> 0x0592 >>>>>> >>>>>> Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter >>>>>> >>>>>> pci bus 0x0008 cardnum 0x09 function 0x04: vendor 0x1180 device >>>>>> 0x0852 >>>>>> >>>>>> Ricoh Co Ltd xD-Picture Card Controller >>>>>> >>>>>> # >>>>>> >>>>>> >>>>>> >>>>>> # ifconfig -a >>>>>> >>>>>> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> >>>>>> mtu 8232 index 1 >>>>>> >>>>>> inet 127.0.0.1 <http://127.0.0.1/> netmask ff000000 >>>>>> >>>>>> iprb0: flags=201000802<BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 >>>>>> index 2 >>>>>> >>>>>> inet 0.0.0.0 <http://0.0.0.0/> netmask 0 >>>>>> >>>>>> ether 0:16:d3:a7:85:52 >>>>>> >>>>>> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> >>>>>> mtu 8252 index 1 >>>>>> >>>>>> inet6 ::1/128 >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> laptop-discuss mailing list >>>>>> laptop-discuss at opensolaris.org >>>>>> >>>>> _______________________________________________ >>>>> laptop-discuss mailing list >>>>> laptop-discuss at opensolaris.org >>>>> >>>> _______________________________________________ >>>> laptop-discuss mailing list >>>> laptop-discuss at opensolaris.org >>>> >> >> _______________________________________________ >> laptop-discuss mailing list >> laptop-discuss at opensolaris.org >
