Announce: ndiswrapper
Quoted 10 lines · Jeff Garzik
Quoted 3 lines · Pontus Fuchs
Please! I don't want to start a flamewar if this is a good thing to do. I'm just trying to scratch my own itch and I doubt that this project changes the way Broadcom treats Linux users.
Then help us reverse engineer the driver :)
Jeff
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Regards,
Jean
Quoted 11 lines · Jean Tourrilhes
Quoted 1 line · Jeff Garzik
Then help us reverse engineer the driver :)
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
Jeff
Quoted 14 lines · Jeff Garzik
Quoted 11 lines · Jean Tourrilhes
Quoted 1 line · Jeff Garzik
Then help us reverse engineer the driver :)
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 2 lines
Unfortunately that leaves users without support for any recent wireless hardware.
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).
Quoted 2 lines
It gets more and more difficult to even find Linux-supported
wireless at Fry's and other retail locations...
If you are careful, you can even buy at Fry's. I bought
recently some Microsoft cards ;-)
Quoted 1 line
Jeff
Jean
Quoted 9 lines · Jean Tourrilhes
Quoted 9 lines
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 6 lines
Quoted 2 lines
Unfortunately that leaves users without support for any recent wireless hardware.
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).
And Realtek (I own one such card) and ADMtek (I bought one by accident in Canada) and Atheros and ... basically anything CardBus doesn't work.
Well, you might say that those have Linux drivers, although they're binary only, but that's about as useful as none if one has a 2.6 kernel.
Quoted 7 lines
Quoted 2 lines
It gets more and more difficult to even find Linux-supported
wireless at Fry's and other retail locations...If you are careful, you can even buy at Fry's. I bought
recently some Microsoft cards ;-)Quoted 1 line
Jeff
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 8 lines · Vojtech Pavlik
Quoted 3 lines · Jean Tourrilhes
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).And Realtek (I own one such card) and ADMtek (I bought one by accident in Canada) and Atheros and ... basically anything CardBus doesn't work.
Wrong. There are wireless drivers for RealTek, ADMtek and
Atheros.
I may repeat myself like a parrot, but "Have you looked at the
Howto lately ?". I think you exactly prove my point ;-)
Jean
Quoted 9 lines · Jean Tourrilhes
Quoted 7 lines · Vojtech Pavlik
Quoted 3 lines · Jean Tourrilhes
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).
Quoted 8 lines
Quoted 2 lines
And Realtek (I own one such card) and ADMtek (I bought one by accident in Canada) and Atheros and ... basically anything CardBus doesn't work.
Wrong. There are wireless drivers for RealTek, ADMtek and
Atheros.
I may repeat myself like a parrot, but "Have you looked at the
Howto lately ?". I think you exactly prove my point ;-)
Last I checked, none of these were 100% open source. I am certain this is true for Atheros, but IIRC it's also the case for the other two?
Anyway, WRT RealTek, they gave me (and others) docs. If I can locate a card, I'll do a driver (or merge an existing one, if any). RealTek's been pretty supportive of open source in the past, what with 8139too/8139cp/r8169 stuff.
Jeff
Quoted 3 lines · Jeff Garzik
Last I checked, none of these were 100% open source. I am certain this is true for Atheros, but IIRC it's also the case for the other two?
Ha ! Now we are talking ;-) But this as well is fully
specified in the Howto... Yes, all those cards have binary drivers made for Linux (which is much better than nothing).
Quoted 2 lines
Anyway, WRT RealTek, they gave me (and others) docs. If I can locate a card, I'll do a driver (or merge an existing one, if any).
Another link from the Howto ;-)
http://www.linux-wlan.org/docs/wlan_adapters.html
Quoted 3 lines
RealTek's
been pretty supportive of open source in the past, what with 8139too/8139cp/r8169 stuff.
That would be real cool ;-) Thanks for your work Jeff.
Quoted 1 line
Jeff
Jean
Quoted 20 lines · Jeff Garzik
Quoted 9 lines · Jean Tourrilhes
Quoted 7 lines · Vojtech Pavlik
Quoted 3 lines · Jean Tourrilhes
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).Quoted 8 lines
Quoted 2 lines
And Realtek (I own one such card) and ADMtek (I bought one by accident in Canada) and Atheros and ... basically anything CardBus doesn't work.
Wrong. There are wireless drivers for RealTek, ADMtek and
Atheros.
I may repeat myself like a parrot, but "Have you looked at the
Howto lately ?". I think you exactly prove my point ;-)
Quoted 7 lines
Last I checked, none of these were 100% open source. I am certain this is true for Atheros, but IIRC it's also the case for the other two?
Anyway, WRT RealTek, they gave me (and others) docs. If I can locate a card, I'll do a driver (or merge an existing one, if any). RealTek's been pretty supportive of open source in the past, what with 8139too/8139cp/r8169 stuff.
If you want, I will send you one. The Edimax EW-7106PC is a Realtek based card.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 7 lines · Jean Tourrilhes
Quoted 6 lines · Vojtech Pavlik
Quoted 3 lines · Jean Tourrilhes
Excuse me ? Have you looked at the Howto lately ? There is
only Broadcom and Intel which are not supported, which leaves plenty of choice (including many 802.11g and 802.11a cards).
Quoted 7 lines
Quoted 2 lines
And Realtek (I own one such card) and ADMtek (I bought one by accident in Canada) and Atheros and ... basically anything CardBus doesn't work.
Wrong. There are wireless drivers for RealTek, ADMtek and
Atheros.
I may repeat myself like a parrot, but "Have you looked at the
Howto lately ?". I think you exactly prove my point ;-)
Yes, I've looked at the howto several times, and even downloaded the drivers.
Quoted 2 lines · You may have missed the second paragraph I
Quoted 2 lines
Quoted 2 lines
Well, you might say that those have Linux drivers, although they're binary only, but that's about as useful as none if one has a 2.6 kernel.
Now I was wrong in a couple points:
As Linus pointed to me, the Atheros driver now works even with 2.6.
They're not binary only, but part-binary, which is somewhat better (not dependent on exact kernel version, just on compiler version and kernel major version).
But still both the Realtek and ADMtek drivers are useless with 2.6.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 7 lines · Jean Tourrilhes
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 3 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
No, it's not my call to make, but basically, I don't see many benefits left. The additional drivers we got out of this were highly version- dependent, extremely fragile, and have been generating massive numbers of bugreports nonstop on a daily basis since their inception.
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever.
Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
-- wli
Quoted 29 lines · William Lee Irwin III
Quoted 8 lines · Jean Tourrilhes
Quoted 8 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.Quoted 2 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
No, it's not my call to make, but basically, I don't see many benefits left. The additional drivers we got out of this were highly version- dependent, extremely fragile, and have been generating massive numbers of bugreports nonstop on a daily basis since their inception.
Quoted 8 lines
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever.
Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
You have to admit its good for end users though. And indirectly, what is good for them is good for us. Take the nvidia example: end users get either a binary driver or nothing. If we were somehow able to stop nvidia from distributing their binary driver, they would say "OK".
I don't advocate making it easy to do non native drivers of course.
Quoted 5 lines · On Thursday November 20, [email protected] wrote:
You have to admit its good for end users though. And indirectly, what is good for them is good for us. Take the nvidia example: end users get either a binary driver or nothing. If we were somehow able to stop nvidia from distributing their binary driver, they would say "OK".
Is it good for end users? It allows them to buy a computer with an nvidia graphics controller because "NVidia supply drivers", and then discover that support is only as good as NVidia are willing to make it. I'm still waiting for some sort of power management support for the nvidia controller in my notebook. If the driver and the specs were open, I could possibly do it myself. On the other hand if there were no NVidia drivers, I never would have made the (arguable) mistake of buying this notebook.
Ofcourse we cannot and should not stop people from providing the option of binary only drivers, but I'm not convinced that we should acknowlege that people who provide binary-only drivers are doing a useful service for anyone but themselves.
(fortuantely I could buy an alternate wireless card which does have open-source drives. It's not so easy to buy an alternate video controler for a notebook - yet).
NeilBrown
Quoted 8 lines · Neil Brown
Quoted 5 lines · On Thursday November 20, [email protected] wrote:
You have to admit its good for end users though. And indirectly, what is good for them is good for us. Take the nvidia example: end users get either a binary driver or nothing. If we were somehow able to stop nvidia from distributing their binary driver, they would say "OK".
Quoted 9 lines
Is it good for end users? It allows them to buy a computer with an nvidia graphics controller because "NVidia supply drivers", and then discover that support is only as good as NVidia are willing to make it. I'm still waiting for some sort of power management support for the nvidia controller in my notebook. If the driver and the specs were open, I could possibly do it myself. On the other hand if there were no NVidia drivers, I never would have made the (arguable) mistake of buying this notebook.
I'm all for open specs, but in reality that doesn't always happen. (out of interest, are there any OS 3d drivers for any current cards?)
I know what you mean, but I would find nvidia more at fault for not providing power management than no OS drivers.
Quoted 6 lines
Ofcourse we cannot and should not stop people from providing the option of binary only drivers, but I'm not convinced that we should acknowlege that people who provide binary-only drivers are doing a useful service for anyone but themselves.
No I wouldn't say that, I meant the Linux Kernel is doing the end users a favour by allowing binary modules.
On Thu, 20 Nov 2003 15:49:05 +1100 Nick Piggin <[email protected]> wrote:
| Neil Brown wrote: | | >On Thursday November 20, [email protected] wrote: | > | >>You have to admit its good for end users though. And indirectly, what | >>is good for them is good for us. Take the nvidia example: end users get | >>either a binary driver or nothing. If we were somehow able to stop | >>nvidia from distributing their binary driver, they would say "OK". | >> | > | >Is it good for end users? It allows them to buy a computer with an | >nvidia graphics controller because "NVidia supply drivers", and then | >discover that support is only as good as NVidia are willing to make | >it. I'm still waiting for some sort of power management support for | >the nvidia controller in my notebook. If the driver and the specs | >were open, I could possibly do it myself. On the other hand if there | >were no NVidia drivers, I never would have made the (arguable) mistake | >of buying this notebook. | > | | I'm all for open specs, but in reality that doesn't always happen. | (out of interest, are there any OS 3d drivers for any current cards?) | | I know what you mean, but I would find nvidia more at fault for not | providing power management than no OS drivers. | | > | >Ofcourse we cannot and should not stop people from providing the | >option of binary only drivers, but I'm not convinced that we should | >acknowlege that people who provide binary-only drivers are doing a | >useful service for anyone but themselves. | > | | No I wouldn't say that, I meant the Linux Kernel is doing the end users | a favour by allowing binary modules.
that's questionable since we can't support them (i.e. fix bugs/problems with them).
--
~Randy
Quoted 14 lines · Randy.Dunlap
On Thu, 20 Nov 2003 15:49:05 +1100 Nick Piggin <[email protected]> wrote:
| Neil Brown wrote:
|| > | >Ofcourse we cannot and should not stop people from providing the | >option of binary only drivers, but I'm not convinced that we should | >acknowlege that people who provide binary-only drivers are doing a | >useful service for anyone but themselves. | > | | No I wouldn't say that, I meant the Linux Kernel is doing the end users | a favour by allowing binary modules.
Quoted 3 lines
that's questionable since we can't support them (i.e. fix bugs/problems with them).
We don't, nvidia does (directly or through a distro). We provide choice, right?
Quoted 3 lines
We don't, nvidia does (directly or through a distro). We provide choice, right?
To x86 users only :(
Ben.
Quoted 4 lines · Nick Piggin
I'm all for open specs, but in reality that doesn't always happen. (out of interest, are there any OS 3d drivers for any current cards?) I know what you mean, but I would find nvidia more at fault for not providing power management than no OS drivers.
The rationales for closed specs are bogus, so I have zero sympathy. It's generally a braindead encoding for commands to carry out well- understood operations. There is nothing to hide, except, of course, the ability to use the hardware.
-- wli
Quoted 9 lines · William Lee Irwin III
Quoted 4 lines · Nick Piggin
I'm all for open specs, but in reality that doesn't always happen. (out of interest, are there any OS 3d drivers for any current cards?) I know what you mean, but I would find nvidia more at fault for not providing power management than no OS drivers.
The rationales for closed specs are bogus, so I have zero sympathy.
Definitely agreed.
When I am forced to sign NDAs to get hardware specs, the hardware IP "revealed" is inevitably something that some other company has done before, and done better. NDAs and closed specs are IMO only used by vendors to save face, when their hardware design is stupid, and their errata innumerable.
Jeff
Quoted 8 lines · William Lee Irwin III
Quoted 5 lines · Nick Piggin
I'm all for open specs, but in reality that doesn't always happen. (out of interest, are there any OS 3d drivers for any current cards?) I know what you mean, but I would find nvidia more at fault for not providing power management than no OS drivers.
Quoted 5 lines
The rationales for closed specs are bogus, so I have zero sympathy. It's generally a braindead encoding for commands to carry out well- understood operations. There is nothing to hide, except, of course, the ability to use the hardware.
Well OK, but whether the manufacturers are bad or good, there will be some that aren't going to release specs or open source drivers. I think it is *mostly* positive that the Linux kernel allows them to support Linux though binary drivers.
Note, I'm talking about the kernel. We are all agreed that closed specs are a bad move by manufacturers.
Quoted 6 lines · William Lee Irwin III
Quoted 6 lines
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever. Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
Quoted 5 lines · Nick Piggin
You have to admit its good for end users though. And indirectly, what is good for them is good for us. Take the nvidia example: end users get either a binary driver or nothing. If we were somehow able to stop nvidia from distributing their binary driver, they would say "OK". I don't advocate making it easy to do non native drivers of course.
I'm not convinced it is good for end users. They _think_ they're getting something that's supported by Linux, but are instead getting something highly problematic that ties them to specific kernel versions and cuts off most, if not all, avenues of support available.
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode. They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
-- wli
Quoted 19 lines · William Lee Irwin III
Quoted 7 lines · William Lee Irwin III
Quoted 7 lines
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever. Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
Quoted 6 lines · Nick Piggin
You have to admit its good for end users though. And indirectly, what is good for them is good for us. Take the nvidia example: end users get either a binary driver or nothing. If we were somehow able to stop nvidia from distributing their binary driver, they would say "OK". I don't advocate making it easy to do non native drivers of course.
Quoted 5 lines
I'm not convinced it is good for end users. They _think_ they're getting something that's supported by Linux, but are instead getting something highly problematic that ties them to specific kernel versions and cuts off most, if not all, avenues of support available.
Well what they get is hardware accelerated 3d graphics under Linux. If they didn't need 3d, they can use the open source drivers. If someone downloads and installs the drivers themselves, they should know enough to contact nvidia for support (I think nvidia have been pretty good). Others will contact their ditro support.
There might be a problem where they percieve that Linux is unstable while it is actually binary drivers.
Quoted 10 lines
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode. They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
I must say that I've been using the same nvidia drivers on my desktop system for maybe a year, and never had a crash including going through countless versions of 2.5/6. True you need to recompile the intermediate layer, but then, nobody who knows less than me will know or care about kernel versions. Their distro will upgrade kernel+drivers if needed, and presumably the distro has done some sort of testing / QA.
Quoted 4 lines · William Lee Irwin III
Quoted 4 lines
I'm not convinced it is good for end users. They _think_ they're getting something that's supported by Linux, but are instead getting something highly problematic that ties them to specific kernel versions and cuts off most, if not all, avenues of support available.
Quoted 5 lines · Nick Piggin
Well what they get is hardware accelerated 3d graphics under Linux. If they didn't need 3d, they can use the open source drivers. If someone downloads and installs the drivers themselves, they should know enough to contact nvidia for support (I think nvidia have been pretty good). Others will contact their ditro support.
"cuts off most, if not all, avenues of support available" == any and all problems with the things around are untraceable. We won't touch tainted bugreports and rightly so. And nvidia isn't supporting the whole kernel.
Quoted 2 lines · Nick Piggin
There might be a problem where they percieve that Linux is unstable while it is actually binary drivers.
Yes, that's one I'm very concerned about.
Quoted 8 lines · William Lee Irwin III
Quoted 8 lines
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode. They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
Quoted 6 lines · Nick Piggin
I must say that I've been using the same nvidia drivers on my desktop system for maybe a year, and never had a crash including going through countless versions of 2.5/6. True you need to recompile the intermediate layer, but then, nobody who knows less than me will know or care about kernel versions. Their distro will upgrade kernel+drivers if needed, and presumably the distro has done some sort of testing / QA.
They're rather sensitive to VM changes, and I've had people with significantly less know-how than either of us come back after trying VM patches in combination with nvidia stuff report things ranging from oopsen, to reboots, to fs corruption. The insulation layers are only partially effective at best. And end-users are fiddling with whiz bang patches for their kernels and upgrading versions by means other than distros. Heck, the distros aren't even shipping 2.6, and they're running 2.6 plus patches.
And besides, nvidia is really just the most commonly reported issue due to the hordes of end users, there are many other offenders on this front (e.g. certain FC drivers, and apparently some wireless drivers).
-- wli
Quoted 17 lines · William Lee Irwin III
Quoted 5 lines · William Lee Irwin III
Quoted 5 lines
I'm not convinced it is good for end users. They _think_ they're getting something that's supported by Linux, but are instead getting something highly problematic that ties them to specific kernel versions and cuts off most, if not all, avenues of support available.
Quoted 6 lines · Nick Piggin
Well what they get is hardware accelerated 3d graphics under Linux. If they didn't need 3d, they can use the open source drivers. If someone downloads and installs the drivers themselves, they should know enough to contact nvidia for support (I think nvidia have been pretty good). Others will contact their ditro support.
Quoted 6 lines
"cuts off most, if not all, avenues of support available" == any and all problems with the things around are untraceable. We won't touch tainted bugreports and rightly so. And nvidia isn't supporting the whole kernel.
I guess they're tracable for nvidia. I'm not aware of how nvidia Linux development works. I assumed from the lack of bug reports that they had done something about it. I concede that bad support from a vendor might cause a bad perception of Linux.
Quoted 9 lines · Nick Piggin
Quoted 4 lines
There might be a problem where they percieve that Linux is unstable while it is actually binary drivers.
Yes, that's one I'm very concerned about.
Bad problem.
Quoted 24 lines
Quoted 9 lines · William Lee Irwin III
Quoted 9 lines
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode. They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
Quoted 7 lines · Nick Piggin
I must say that I've been using the same nvidia drivers on my desktop system for maybe a year, and never had a crash including going through countless versions of 2.5/6. True you need to recompile the intermediate layer, but then, nobody who knows less than me will know or care about kernel versions. Their distro will upgrade kernel+drivers if needed, and presumably the distro has done some sort of testing / QA.
Quoted 9 lines
They're rather sensitive to VM changes, and I've had people with significantly less know-how than either of us come back after trying VM patches in combination with nvidia stuff report things ranging from oopsen, to reboots, to fs corruption. The insulation layers are only partially effective at best. And end-users are fiddling with whiz bang patches for their kernels and upgrading versions by means other than distros. Heck, the distros aren't even shipping 2.6, and they're running 2.6 plus patches.
I didn't mean that in an elitist way (you shouldn't be compiling kernels unless you are taller than the sign) - I just mean the knowledge required to recompile the kernel and nvidia drivers. And the people with that know how should generally know that the binary modules can be unstable. Again I concede this won't always be the case.
Quoted 1 line · Nick Piggin
I guess they're tracable for nvidia.
Unless the system has a second binary only driver loaded, from another vendor.
Then the system is essentially unsupportable, regardless of how much money the user has paid for the support contract.
In that case the "good support" advantage of Linux disappears.
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 3 lines · El Thu, 20 Nov 2003 15:59:46 +1100 Nick Piggin <[email protected]>…
I must say that I've been using the same nvidia drivers on my desktop system for maybe a year, and never had a crash including going through countless versions of 2.5/6. True you need to recompile the intermediate
You're lucky.
Nvidia drivers are broken, and it's not just linux. Their windows drivers are know to be buggy, too. And this is happening in windows (which has a "windows driver model" abi which doesn't change even between W9x and nt)
Also, they don't support non-x86 architectures in linux (they have drivers for mac os X though)
If there're a lot of binary drivers for linux, we'll have the same hell microsoft has (w2k and XP are rock solid, until you start using crappy drivers, then everybody complains about blue screens). A stable and defined abi (like their driver model) doesn't work for them, it won't work for us.
I don't mind running propietary code...but not in the kernel.
(BTW, are there modern graphics cards with 100% opensource drivers?)
Quoted 1 line · Diego Calleja García
"windows driver model" abi which doesn't change even between W9x and nt)
that's what microsoft PR says. in fact it's rather difficult to have a driver working on win9x and nt without very ugly hacks. And for some driver classes it doesn't work at all.
Quoted 18 lines · Diego Calleja García
Quoted 3 lines · El Thu, 20 Nov 2003 15:59:46 +1100 Nick Piggin <[email protected]>…
I must say that I've been using the same nvidia drivers on my desktop system for maybe a year, and never had a crash including going through countless versions of 2.5/6. True you need to recompile the intermediate
You're lucky.
Nvidia drivers are broken, and it's not just linux. Their windows drivers are know to be buggy, too. And this is happening in windows (which has a "windows driver model" abi which doesn't change even between W9x and nt)Also, they don't support non-x86 architectures in linux (they have drivers for mac os X though)
If there're a lot of binary drivers for linux, we'll have the same hell microsoft has (w2k and XP are rock solid, until you start using crappy drivers, then everybody complains about blue screens). A stable and defined abi (like their driver model) doesn't work for them, it won't work for us.
Quoted 4 lines
I don't mind running propietary code...but not in the kernel.
(BTW, are there modern graphics cards with 100% opensource drivers?)
None of the new chips (r300, any nvidia, matrox, etc) has opensource 3D drivers.
If you want good 3D support (OpenGL) you need to use binary drivers :(
DRI (opensource) opengl-drivers have support for only ati r200 and older cards.. so nothing new. And DRI drivers don't support the advanced features of these cards.. so no shaders etc :(
OpenGL support in DRI drivers feels also more buggy than Nvidia/ATI binary drivers :(
So the situation is not good..
-- Pasi Kärkkäinen
^
. .
Linux
/ - \
Choice.of.the
.Next.Generation.Quoted 8 lines · William Lee Irwin III
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode. They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
On the flip side, if I go back as far as 2.5.4<mumble>, I've had a lot more days where the open-source drivers for my Xircom ethernet/modem card were broken than days where my binary NVidia driver was broken. Also, the Xircom has been the cause of a lot more "hang before even single user mode" problems, and several times the Xircom didn't start working again until there was a complete overhaul of the Cardbus support, while there's not been that much activity on the NVidia patch on www.minion.de.
It's certainly seemed like I've ended up "stuck waiting for a specific small set of individuals" when the Cardbus support has broken (not to slight them, they're all great guys and do support the stuff) - how many people on this list *really* understand that code? And it's not just the Cardbus stuff - there's a LOT of stuff in the kernel that's only really understood by a very small number of people.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Quoted 2 lines · William Lee Irwin III
It's very much a second-class flavor of open source. They dare not change the kernel version lest the binary-only trainwreck explode.
We already have a second-class flavor of open source in the kernel right now. There are drivers that do "magic value at magic address" in a quite sophisticated manner. Combine this with firmware load from Windows DLLs and you basically HAVE closed source, since the driver is on the device itself and we just invoke it via i2c commands.
On NVidia drivers we might complain, that we don't see, which kernel functions are used and for what. On these drivers we don't even see what is done, since the device can issue DMA at will and thus scribble over random kernel memory on firmware malfunction. And maybe this scribbling is not that lethal to Windows for some reasons (e.g. area never used or reserved area) so it will never be fixed.
Just have a look at some DVB hardware drivers. As much as I like *what* is done there, I don't like how it is done.
What you call second-class is third-class already, since it also freezes the kernel ABI and behavior forcably.
Quoted 6 lines
They dare not run with the whiz-bang patches going around they're interested in lest the binary-only trainwreck explode. It may oops in mainline, and all they can do is wait for a tech support line to answer. Well, they're a little better than that, they have hackers out and about, but you're still stuck waiting for a specific small set of individuals and lose all of the "many eyes" advantages.
This "many eye" advantage is lost already by the type of drivers above in kernel right now. Binary-only just adds to the pain by freezing kernel<->module ABI.
Regards
Ingo Oeser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/vI/xU56oYWuOrkARAubfAJ4kIKlQvGbnPHxebnEQrqcfxOxMzQCeJ1Rz jZ4toSAkd4Ry1LXNReuh2dc=
=zfYZ
-----END PGP SIGNATURE-----
Quoted 13 lines · Ingo Oeser
We already have a second-class flavor of open source in the kernel right now. There are drivers that do "magic value at magic address" in a quite sophisticated manner. Combine this with firmware load from Windows DLLs and you basically HAVE closed source, since the driver is on the device itself and we just invoke it via i2c commands.
On NVidia drivers we might complain, that we don't see, which kernel functions are used and for what. On these drivers we don't even see what is done, since the device can issue DMA at will and thus scribble over random kernel memory on firmware malfunction. And maybe this scribbling is not that lethal to Windows for some reasons (e.g. area never used or reserved area) so it will never be fixed.
Quoted 2 lines
Just have a look at some DVB hardware drivers. As much as I like *what* is done there, I don't like how it is done.
Those drivers (at least the ones in the kernel right now) cannot issue any DMA from inside the firmware. They also cannot crash the system, only themselves. Basically they are like a separate computer connected via a network-like connection (in this case dual ported RAM). The code controlling the PCI bridge is open.
You are right that if the firmware can do things like initiating DMA transfers this is a big problem. Of course this can also happen with hardware which has bugs in permanently burnt-in microcode or even in the silicon itself.
Regards,
Ralph Metzler
Quoted 40 lines · Nick Piggin
Quoted 36 lines · William Lee Irwin III
Quoted 8 lines · Jean Tourrilhes
Quoted 8 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.Quoted 4 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
No, it's not my call to make, but basically, I don't see many benefits left. The additional drivers we got out of this were highly version- dependent, extremely fragile, and have been generating massive numbers of bugreports nonstop on a daily basis since their inception.
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever.
Quoted 6 lines
Quoted 3 lines
Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
You have to admit its good for end users though. And indirectly, what is good for them is good for us.
No. It is bad for the end users - they get sold a bill of goods. And it is bad for developers. And it is bad for developers as users. And it's hopelessly short-sighted as pragmatism often is.
Look, there's basically one thing that has ever historically enabled developers to get specs for writing decent Linux drivers, and that's demand from Linux users. If companies are presented with alternatives that pointy haired folks prefer like binary-only drivers or running their one and only Windows driver on an emulation layer, which are they going to choose and where are they going to tell users to stick their penguin? We'll be in worse shape than we were when no one had ever heard of Linux.
Scenario to think about: an NDIS driver layer ends up getting firmed up and debugged and when the next generation of wireless appears, basically all vendors go the easy route and only ship NDIS drivers, no specs, and buggy as usual. Then they say hey, this worked out well, might as well do this with gigabit. Meanwhile, hardware's changing so quickly that by the time we manage to reverse-engineer any of this stuff (provided the legal climate allows it), it's already off the shelves. Two to three years from now, it's impossible to build a decent server or laptop that doesn't have bug-ridden, untested, low performance network drivers and all the reputation Linux has for being a good network OS goes down the tubes. It's safe to assume that latency and stability will go all to hell as well.
An open operating system without open drivers is pointless and if we don't do something about all this binary crap soon, the above scenario -will- play out. Expect SCSI and perhaps sound to follow soon afterwards. And graphics cards and modems are obviously half-way there already.
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
Quoted 82 lines · Matt Mackall
Quoted 40 lines · Nick Piggin
Quoted 36 lines · William Lee Irwin III
Quoted 9 lines · Jean Tourrilhes
Quoted 9 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.Quoted 3 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
No, it's not my call to make, but basically, I don't see many benefits left. The additional drivers we got out of this were highly version- dependent, extremely fragile, and have been generating massive numbers of bugreports nonstop on a daily basis since their inception.
We'd lose a few things, like vmware, but it's not worth the threat of vendors migrating en masse to NDIS/etc. emulation layers and dropping all spec publication and source drivers, leaving us entirely at the mercy of BBB's (Buggy Binary Blobs) to do any io whatsoever.
Quoted 7 lines
Quoted 4 lines
Seriously, the binary-only business has been doing us a disservice, and is threatening to do worse.
You have to admit its good for end users though. And indirectly, what is good for them is good for us.
No. It is bad for the end users - they get sold a bill of goods. And it is bad for developers. And it is bad for developers as users. And it's hopelessly short-sighted as pragmatism often is.
Look, there's basically one thing that has ever historically enabled developers to get specs for writing decent Linux drivers, and that's demand from Linux users. If companies are presented with alternatives that pointy haired folks prefer like binary-only drivers or running their one and only Windows driver on an emulation layer, which are they going to choose and where are they going to tell users to stick their penguin? We'll be in worse shape than we were when no one had ever heard of Linux.
Scenario to think about: an NDIS driver layer ends up getting firmed up and debugged and when the next generation of wireless appears, basically all vendors go the easy route and only ship NDIS drivers, no specs, and buggy as usual. Then they say hey, this worked out well, might as well do this with gigabit. Meanwhile, hardware's changing so quickly that by the time we manage to reverse-engineer any of this stuff (provided the legal climate allows it), it's already off the shelves. Two to three years from now, it's impossible to build a decent server or laptop that doesn't have bug-ridden, untested, low performance network drivers and all the reputation Linux has for being a good network OS goes down the tubes. It's safe to assume that latency and stability will go all to hell as well.
An open operating system without open drivers is pointless and if we don't do something about all this binary crap soon, the above scenario -will- play out. Expect SCSI and perhaps sound to follow soon afterwards. And graphics cards and modems are obviously half-way there already.
Quoted 5 lines
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
Note I 100% disagree with any sort of emulation layer in the kernel.
Quoted 3 lines · Matt Mackall
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
Indeed. What happened to the `works[*] with Linux' labelling proposal we discussed about at the last Linux Kernel Summit?
[*] Meaning providing a decent source under a suitable license.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 3 lines · Matt Mackall
Quoted 3 lines
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
Quoted 3 lines · Geert Uytterhoeven
Indeed. What happened to the `works[*] with Linux' labelling proposal we discussed about at the last Linux Kernel Summit?
[*] Meaning providing a decent source under a suitable license.
We may have to get Linus in on that.
-- wli
Quoted 11 lines · William Lee Irwin III
Quoted 3 lines · Matt Mackall
Quoted 3 lines
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
Quoted 3 lines · Geert Uytterhoeven
Indeed. What happened to the `works[*] with Linux' labelling proposal we discussed about at the last Linux Kernel Summit?
[*] Meaning providing a decent source under a suitable license.We may have to get Linus in on that.
Linux is a trademark. And if you don't defend it you lose it (like asprin and kleenex). So if he doesn't like the "Linux driver" from nvidia he can tell them to stop using the term. I'm not sure that's a good thing, however, they are more likely to drop support than open source IMHO.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 1 line · William Lee Irwin III
Quoted 1 line
We may have to get Linus in on that.
Quoted 4 lines · Bill Davidsen
Linux is a trademark. And if you don't defend it you lose it (like asprin and kleenex). So if he doesn't like the "Linux driver" from nvidia he can tell them to stop using the term. I'm not sure that's a good thing, however, they are more likely to drop support than open source IMHO.
Are we really going to cower when faced like an ultimatum like that?
-- wli
The problem is that they could very easily drop support for linux, then what do we do?
We don't have any form of access to the top-of-the-line hardware needed to run most new games, which means there'll be less incentive to try and port them, so there's less reason to create drivers, ad infintum...
If anything the only thing we can really do is ask *politely* if they could open more of the drivers...
--Oliver
Quoted 28 lines · William Lee Irwin III
Quoted 3 lines · William Lee Irwin III
Quoted 3 lines
We may have to get Linus in on that.
Quoted 6 lines · Bill Davidsen
Linux is a trademark. And if you don't defend it you lose it (like asprin and kleenex). So if he doesn't like the "Linux driver" from nvidia he can tell them to stop using the term. I'm not sure that's a good thing, however, they are more likely to drop support than open source IMHO.
Are we really going to cower when faced like an ultimatum like that?
-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 10 lines · William Lee Irwin III
Quoted 1 line · William Lee Irwin III
Quoted 1 line
We may have to get Linus in on that.
Quoted 4 lines · Bill Davidsen
Linux is a trademark. And if you don't defend it you lose it (like asprin and kleenex). So if he doesn't like the "Linux driver" from nvidia he can tell them to stop using the term. I'm not sure that's a good thing, however, they are more likely to drop support than open source IMHO.
Are we really going to cower when faced like an ultimatum like that?
What you me "we" here? Linus owns the trademark, he makes the decisions. I can give him the name of a lawyer who did patent and trademark for GE for decades, but I can't give him any advice. This is not a gut feel decision, and "cower" sure sounds gut feel to me. That's probably not the optimal consideration in this case. Failing to defend can mean losing a challenge as well as doing nothing, the only advice I have on that is "consult a good lawyer."
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
On Thursday 20 November 2003 01:52, Matt Mackall wrote:
[huge snip of well reasoned arguments]
Quoted 4 lines
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
Hear, hear! I'm still smarting over buying a copy of Wordperfect 8 for linux for $65 back in '98 or '99, only to find it wouldn't even install if it didn't find some old, buggy 2.2.x kernel to run under. The 2.4.x family was by then several generations old.
Shennanigans like that, screwing the customer (who had no recourse but to seriously downgrade his system, no refunds were given) was one of the things that Corel was very good at. And it no doubt heavily contributed to the eventual failure of Corel. Potential Future Customers remember that even if the PHB's can't. I removed my self from that PFC list forthwith.
I keep it on the shelf as a reminder that I was one of those "Suckers born every minute" :(
I'm for it, if it doesn't work with the latest stable kernel release, the labels MUST COME OFF. But howto enforce that legally is the real $64 question. Humm, I guess that dates me, I can remember that radio program. From back in the '40's.
Signature · 7 lines
Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Quoted 13 lines · Matt Mackall
Scenario to think about: an NDIS driver layer ends up getting firmed up and debugged and when the next generation of wireless appears, basically all vendors go the easy route and only ship NDIS drivers, no specs, and buggy as usual. Then they say hey, this worked out well, might as well do this with gigabit. Meanwhile, hardware's changing so quickly that by the time we manage to reverse-engineer any of this stuff (provided the legal climate allows it), it's already off the shelves. Two to three years from now, it's impossible to build a decent server or laptop that doesn't have bug-ridden, untested, low performance network drivers and all the reputation Linux has for being a good network OS goes down the tubes. It's safe to assume that latency and stability will go all to hell as well.
Quoted 5 lines
An open operating system without open drivers is pointless and if we don't do something about all this binary crap soon, the above scenario -will- play out. Expect SCSI and perhaps sound to follow soon afterwards. And graphics cards and modems are obviously half-way there already.
You left out the black helicopters... the reason vendors support Linux is to sell product. If the driver doesn't work well some number of people will either debug and fix the problem (source) or not buy the product (binary). And giving out the spec and letting someone else do the driver is even better, no work, no cost, no liability for bugs.
I think the vendors who feel that they have something to hide are the exception, and rumor has it that fixes in Linux drivers migrate back into Windows drivers, another fringe benefit.
Quoted 3 lines
Personally, I think it's time to do some sort of trademark enforcement or something so that companies can't get away with slapping penguins on devices that only work with 2.2.14 Red Hat kernels.
On that I agree, but remember that only one Penguin has a vote on that. A Trademark must be defended or it will be lost, maybe this would be a good place to start. Let a lawyer advise on stuff like that.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 16 lines · William Lee Irwin III
Quoted 7 lines · Jean Tourrilhes
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.Quoted 1 line · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
Quoted 7 lines
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
Who brought binary drivers into this? And when I have ever advocated binary drivers?
ndiswrapper has one use IMHO (which was pointed out me in this thread)... to assist in reverse engineering.
Jeff
Quoted 6 lines · William Lee Irwin III
Quoted 6 lines
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards. I say we should go the precise opposite direction and take a hard line stance against binary drivers, lest we find there are none left we even have source to and are bombarded with unfixable bugreports.
Quoted 4 lines · Jeff Garzik
Who brought binary drivers into this? And when I have ever advocated binary drivers?
ndiswrapper has one use IMHO (which was pointed out me in this thread)... to assist in reverse engineering.
Hmm, maybe I've gotten the whole purpose of the thread wrong. =(
-- wli
Quoted 5 lines
Quoted 3 lines
ndiswrapper has one use IMHO (which was pointed out me in this thread)... to assist in reverse engineering.
Hmm, maybe I've gotten the whole purpose of the thread wrong. =(
Still, I've looked into possibly reverse engineering the Broadcom one for 802.11g from MacOS X (with 2 machines kernel debugging and functions names embedded in the driver, it's not _that_ bad). But it's a +500k binary .... I didn't go very far and decided I had better ways to spend my time.
I know a lot of you don't care, but I hate in those discussions about binary drivers when what is for me the #1 issue isn't even
mentioned: availability on non-x86 hardware !
Ben.
Quoted 4 lines · Benjamin Herrenschmidt
I know a lot of you don't care, but I hate in those discussions about binary drivers when what is for me the #1 issue isn't even
mentioned: availability on non-x86 hardware !
That's why in the Howto the binary drivers are flagged
accordingly. I even add explicit PPC driver for drivers I know work on PPC. What more do you need ?
I still don't understand why people buy the wrong
hardware. You have a choice, exercise it !
Quoted 1 line
Ben.
Regards,
Jean
Quoted 11 lines · Jean Tourrilhes
Quoted 4 lines · Benjamin Herrenschmidt
I know a lot of you don't care, but I hate in those discussions about binary drivers when what is for me the #1 issue isn't even
mentioned: availability on non-x86 hardware !That's why in the Howto the binary drivers are flagged
accordingly. I even add explicit PPC driver for drivers I know work on PPC. What more do you need ?
I still don't understand why people buy the wrong
hardware. You have a choice, exercise it !
Except when Apple provides built-in Broadcom chipset in all new recent Macs...
Ben.
Quoted 3 lines · Benjamin Herrenschmidt
Except when Apple provides built-in Broadcom chipset in all new recent Macs...
Only one world : monopoly...
Quoted 1 line
Ben.
Jean
Quoted 5 lines · [email protected] said:
Who brought binary drivers into this? And when I have ever advocated binary drivers?
ndiswrapper has one use IMHO (which was pointed out me in this thread)... to assist in reverse engineering.
That may be your intention, but as soon as cards exist that can only be made to work with ndis-wrapped drivers, you can be sure that the masses won't wait for the reverse-engineering to be completed. So all the nvidia-video-type problems _will_ start showing up in a big population of laptops and such too.
Jason
Quoted 4 lines · Jason Lunz
Quoted 2 lines · [email protected] said:
Who brought binary drivers into this? And when I have ever advocated binary drivers?
Quoted 8 lines
Quoted 1 line
ndiswrapper has one use IMHO (which was pointed out me in this thread)... to assist in reverse engineering.
That may be your intention, but as soon as cards exist that can only be made to work with ndis-wrapped drivers, you can be sure that the masses won't wait for the reverse-engineering to be completed. So all the nvidia-video-type problems _will_ start showing up in a big population of laptops and such too.
And we will ignore such bug reports, like we ignore nVidia bug reports now. I welcome choice, including the choice of users to shoot themselves in the foot...
Jeff
Quoted 9 lines · William Lee Irwin III
Quoted 7 lines · Jean Tourrilhes
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 8 lines
Quoted 3 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
What's the point in ruminating academic scenario. There exist
fully open source drivers for quite a wide variety of modern wireless LAN cards. It's not like if you don't have the choice.
Jean
Quoted 19 lines · Jean Tourrilhes
Quoted 9 lines · William Lee Irwin III
Quoted 7 lines · Jean Tourrilhes
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.Quoted 8 lines
Quoted 3 lines · Jeff Garzik
Unfortunately that leaves users without support for any recent wireless hardware. It gets more and more difficult to even find Linux-supported wireless at Fry's and other retail locations...
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
Quoted 5 lines
What's the point in ruminating academic scenario. There exist
fully open source drivers for quite a wide variety of modern wireless LAN cards. It's not like if you don't have the choice.Jean
It's kinda interesting that several Wireless LAN boxen even use Linux.... I suppose they don't want anybody to know that, though....
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
Quoted 3 lines · William Lee Irwin III
Quoted 3 lines
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
Quoted 3 lines · Jean Tourrilhes
What's the point in ruminating academic scenario. There exist
fully open source drivers for quite a wide variety of modern wireless LAN cards. It's not like if you don't have the choice.
I wasn't quite aware of that when I made the post; prior discussions had led me to believe the above scenario to be something approaching the status quo.
-- wli
[ replying to several posts ]
Quoted 5 lines · Jean Tourrilhes
That's why in the Howto the binary drivers are flagged
accordingly. I even add explicit PPC driver for drivers I know work on PPC. What more do you need ?
I still don't understand why people buy the wrong
hardware. You have a choice, exercise it !
Quoted 7 lines · Jean Tourrilhes
Quoted 3 lines
And what good would it be to have an entire driver subsystem populated by binary-only drivers? That's not part of Linux, that's "welcome to nvidia hell" for that subsystem too, and not just graphics cards.
What's the point in ruminating academic scenario. There exist
fully open source drivers for quite a wide variety of modern wireless LAN cards. It's not like if you don't have the choice.
Unfortunately in the real world, many people *don't* have a choice. They are limited to using what they can afford, or what their employer, university, or thesis advisor provides or requires. People also have system with built-in devices which either can't be removed or which will void waranty if the devices are removed.
If the NDIS software allows development of OS drivers for the hardware people *must* use, then they will at least have a choice of the operating system. And if it improves reverse engineering some companies will avoid NDIS just for that reason. Sounds like two good results to me.
The idea that all vendors would drop open spec and open source is totally unrelated to reality, some companies provided that information when the Linux market was tiny, they are not going to change, and neither are the companies who don't release info now.
I'm curious if the NDIS stuff could be run in ring 1 or 2, being an old MULTICS guy. Not for political reasons, just good tech.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Followup to: <[email protected]> By author: Bill Davidsen <[email protected]> In newsgroup: linux.dev.kernel
Quoted 4 lines
I'm curious if the NDIS stuff could be run in ring 1 or 2, being an old MULTICS guy. Not for political reasons, just good tech.
Unfortunately the segmentation and paging were so poorly integrated in i386 that rings 1-2 are pretty much totally useless.
-hpa
Signature · 4 lines
<[email protected]> at work, <[email protected]> in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
Quoted 7 lines · H. Peter Anvin
By author: Bill Davidsen <[email protected]>
Quoted 3 lines
I'm curious if the NDIS stuff could be run in ring 1 or 2, being an old MULTICS guy. Not for political reasons, just good tech.
Unfortunately the segmentation and paging were so poorly integrated in i386 that rings 1-2 are pretty much totally useless.
That may be the politically sensitive (except to Intel) correct answer, but in the end I suspect that the _real_ answer is that ring 1/2 are just fundamentally useless, and it has nothing to do with x86 implementation semantics or anything else.
Any kind of reasonable performance driver requires direct access to the buffers it is going to fill in. And not just the actual data contents, but to the metadata too - the pointers that comprise the skb (or in BSD, mbuf) lists, etc.
So even if you were to use ring1/2 for the driver, you'd really need to give write access to a large portion of the data structures that the "core" kernel networking would use.
Which means that you either put the core kernel in ring1/2 as well (at which point you don't actually use ring0 for anything interesting at all - you could put a microkernel there, but hey, there's no real point), or you map in a _lot_ of ring0 metadata into ring1/2, at which point you lost the whole point of using a different protection domain.
And quite frankly, if you're willing to actually dynamically map all the ranges and be careful, why use ring1/2 at all? You might as well use ring3 and make the whole thing be a user-mode wrapper. You'd never perform really well, but for debugging it is acceptable.
Anyway, whatever way you turn, ring1/2 just don't actually _give_ you anything. Which is, in the end, the _real_ reason nobody uses them.
(I agree, the fact that the x86 paging hardware makes 1/2/3 be equivalent makes it an even _less_ useful abstraction, but I think it is a mistake to think that it would be any more useful even if the page tables wasted precious bits on unnecessary level information).
Multi-ring was a failure. Let it go. The only reason it is making something of a comeback (Palladium-whatever-it-is-called-today) has no good technical reasons, and is purely about other things.
Linus
Quoted 3 lines · Linus Torvalds
(I agree, the fact that the x86 paging hardware makes 1/2/3 be equivalent makes it an even _less_ useful abstraction, but I think it is a mistake to think that it would be any more useful even if the page tables wasted precious bits on unnecessary level information).
Actually, the paging hardware makes 0/1/2 equivalent; some *other* primitives make 1/2/3 equivalent...
Quoted 5 lines
Multi-ring was a failure. Let it go. The only reason it is making something of a comeback (Palladium-whatever-it-is-called-today) has no good technical reasons, and is purely about other things.
No doubt. However, I wish they would have at least taken the few useful thing they had in the i286 botch, like the RPL, and made them available to the paging system. That way i386 would have had "access this as from user space" like most architectures have.
-hpa
Linus Torvalds wrote:
[...]
Quoted 4 lines
That may be the politically sensitive (except to Intel) correct answer, but in the end I suspect that the _real_ answer is that ring 1/2 are just fundamentally useless, and it has nothing to do with x86 implementation semantics or anything else.
(A bit OT, but...)
Hi Linus!
The good people at Cambridge made a (very nice) VMM that exploits ring0/1/3 to let one machine run various kernels independently (the kernels need to be ported to the xen arch).
Xen itself executes in ring0 and the "guest" operating systems execute in ring1. User code runs in ring3, as usual. They have linux running under xen ;)
The project's home page is at http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ and one paper describing the whole thing is here: http://www.cl.cam.ac.uk/netos/papers/2003-xensosp.pdf
Regards,
Nuno Silva
Quoted 4 lines · Nuno Silva
The good people at Cambridge made a (very nice) VMM that exploits ring0/1/3 to let one machine run various kernels independently (the kernels need to be ported to the xen arch).
This is what I alluded to a few lines later - saying that if you move the driver down to ring1, then you should move _everything_ down to ring1 and just leave a microkernel at ring0.
Now, I'm not big on microkernels, but a pure virtual machine abstraction is at least not the distateful academic mental masturbation that we saw in the 80's.
Linus
Hi!
Quoted 8 lines
Quoted 7 lines
Quoted 3 lines · Pontus Fuchs
Please! I don't want to start a flamewar if this is a good thing to do. I'm just trying to scratch my own itch and I doubt that this project changes the way Broadcom treats Linux users.
Then help us reverse engineer the driver :)
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Unfortunately my broadcom came integrated within notebook. More and more notebooks come with wifi installed...
Pavel
Signature · 2 lines
Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
Quoted 18 lines · Pavel Machek
Hi!
Quoted 8 lines
Quoted 7 lines
Quoted 3 lines · Pontus Fuchs
Please! I don't want to start a flamewar if this is a good thing to do. I'm just trying to scratch my own itch and I doubt that this project changes the way Broadcom treats Linux users.
Then help us reverse engineer the driver :)
Quoted 7 lines
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 3 lines
Unfortunately my broadcom came integrated within notebook. More and more notebooks come with wifi installed...
Pavel
Ask TyTso how you can change the MiniPCI card in laptops. I
think he even has a web page on the subject.
Good luck...
Jean
Quoted 7 lines · Jean Tourrilhes
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
You left out the step of "remove or disable the existing hardware in the system." Not everyone has a choice unlimited by budget and politics.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 10 lines · Bill Davidsen
Quoted 7 lines · Jean Tourrilhes
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 2 lines
You left out the step of "remove or disable the existing hardware in the system." Not everyone has a choice unlimited by budget and politics.
Why did you buy a bogus card in the first place ? That's
wasting money.
Jean
Quoted 11 lines · Jean Tourrilhes
Quoted 10 lines · Bill Davidsen
Quoted 7 lines · Jean Tourrilhes
Even better :
1) go to the Wireless LAN Howto
2) find a card are supported under Linux that suit your needs
3) buy this card
I don't see the point of giving our money to vendors that
don't care about us when there are vendors making a real effort toward us.
Quoted 5 lines
Quoted 2 lines
You left out the step of "remove or disable the existing hardware in the system." Not everyone has a choice unlimited by budget and politics.
Why did you buy a bogus card in the first place ? That's
wasting money.
The most common reason is that someone else, like employer or university, specifies or even provides the hardware. After that comes system price, a system with a less-than-perfect device may be much cheaper than the perfect solution. Many people have a low money to time ratio, and when affordable hardware becomes available it's only possible to use it. And in some cases the offending hardware may be unremovable, as in soldered on. Think laptop.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Jean" == Jean Tourrilhes <[email protected]> writes:
Quoted 8 lines · Jean> Jeff Garzik wrote :
Quoted 1 line
Pontus Fuchs wrote:
Please! I don't want to start a flamewar if this is a good thing to do. I'm just trying to scratch my own itch and I doubt that this project changes the way Broadcom treats Linux users.
Quoted 4 lines
Then help us reverse engineer the driver :)
Jeff
Jean> Even better :
Jean> 1) go to the Wireless LAN Howto
Jean> 2) find a card are supported under Linux that suit your needs Jean> 3) buy this card
Jean> I don't see the point of giving our money to vendors that don't Jean> care about us when there are vendors making a real effort toward Jean> us. Regards,
Unfortunately, this means you can't buy a "Centrino"-based laptop. Actually, that pretty much means you can't get any recent laptop.
I'd like on this occasion to remind everyone that Intel left Linux out in the cold in spite of loud announcements of upcoming Linux support for the "Centrino" marketing thing (see for example
http://news.com.com/2100-1006-993896.html or
http://zdnet.com.com/2100-1103-993896.html or
http://www.intel.com/support/notebook/centrino/sb/cs-006059-prd955.htm).
There is of course the "Intel Support of Centrino Under Linux" petition
(http://www.petitiononline.com/xanthan/petition.html), which seems to have done some good as the aforementioned Intel page has been updated to say the drivers are "under development".
Still, even if they are "under development", this means some other operating systems have had an unfair over one-year advantage over Linux. That's a *big, long* advantage.
I'm a bit surprised that nobody has sued Intel yet for unfair market practices, as providing documentation on chipset workings to select vendors certainly constitutes one. But I guess that's politics, nobody wants to mess with the big guys, it's better to play along and get early access to server architectures.
I find it rather sad that Michael Robertson has so far been the only one to speak up: http://www.theregister.co.uk/content/4/29840.html. Why is RedHat (for example) sitting quietly? Whining about lack of success of Linux on the desktop seems to be a silly thing to do if Linux doesn't even WORK properly on the desktop machine.
The reason I wrote this posting is because I think reverse-engineering the drivers forever is not a long-term solution. Vendors should start feeling the pressure.
--J.