|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Dell really gets Linux - at last
|
I've tried to think of the drivers as part of the hardware. That is I really
have no need to distribute them or copy them. They just come with the card.
But the more the more I think about it, this would be like saying "XP just
comes with the machine". So relatively, it is the same problem, or even worse
since I think we don't get access to the API's of the card. Or do we?
Still, ndiswrapper is quite elegant at least in it's purpose. Perhaps saving
the Linux community from a serious temporary problem (or making them (me) lazy?).
> Yup, it's an ugly hack that is unfortunately sometimes necessary. Being
> forced to use ndiswrappers on a machine that was never intended for
> Linux is one thing, but having to use it on a machine that *was*
> intended for Linux is another. It isn't quite that bad, since the
> binary blob driver does more or less work. It just really bugs me that
> a machine expressly designed (at least in part) to run Linux **can't**
> run on all open source.
>
----- Original Message ----
> From: JP Vossen <jp@jpsdomain.org>
> To: plug@lists.phillylinux.org
> Sent: Friday, July 10, 2009 10:57:37 AM
> Subject: Re: [PLUG] Dell really gets Linux - at last
>
> > Date: Wed, 8 Jul 2009 13:27:28 -0700 (PDT)
> > From: Edmond Rodriguez
> >
> > Are you saying the Broadcom chips are no good because of lack of
> > Linux support, or the hardware is no good? Mine (on an HP) seems to work
> > perfectly on the Windows side of things. Linux is another story, and I
> > mostly stopped trying to get Linux drivers to work for it, after
> > learning ndiswrapper.
>
> Mostly the F/OSS hostile nature of the card and the company, though I
> seem to recall reading about a fair number of hardware issues a while
> ago too.
>
> Sorry, I should have been more clear about that.
>
>
> > I've been using my broadcom with ndiswrapper on Linux for years
> > reliably. I have some quirks starting the wpa_supplicant, but once
> > I get it going, it is very stable and I wonder if wpa_supplicant has
> > much to do with the hardware anyway. I think most of the issues I
> > have to get it started are related to software.
> >
> > ndiswrapper breaks sometimes as kernels get updated, but if that
> > concern were addressed, it would be fine. Ndiswrapper seems to
> > generate lots of controversy in the Linux world.
>
> Yup, it's an ugly hack that is unfortunately sometimes necessary. Being
> forced to use ndiswrappers on a machine that was never intended for
> Linux is one thing, but having to use it on a machine that *was*
> intended for Linux is another. It isn't quite that bad, since the
> binary blob driver does more or less work. It just really bugs me that
> a machine expressly designed (at least in part) to run Linux **can't**
> run on all open source.
>
> Later,
> JP
> ----------------------------|:::======|-------------------------------
> JP Vossen, CISSP |:::======| http://bashcookbook.com/
> My Account, My Opinions |=========| http://www.jpsdomain.org/
> ----------------------------|=========|-------------------------------
> "Microsoft Tax" = the additional hardware & yearly fees for the add-on
> software required to protect Windows from its own poorly designed and
> implemented self, while the overhead incidentally flattens Moore's Law.
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|