From: Diego Calleja <diegocg@gmail.com>
To: Toon van der Pas <toon@hout.vanvergehaald.nl>
Cc: rostedt@goodmis.org, arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 3D video card recommendations
Date: Mon, 7 Nov 2005 18:00:45 +0100 [thread overview]
Message-ID: <20051107180045.ec86a7f2.diegocg@gmail.com> (raw)
In-Reply-To: <20051107152009.GA20807@shuttle.vanvergehaald.nl>
El Mon, 7 Nov 2005 16:20:09 +0100,
Toon van der Pas <toon@hout.vanvergehaald.nl> escribió:
> > MS folks would have the same problem.
>
> ...which proves the point Arjan is making.
>
> For one, I have an ISDN-adapter which doesn't work with any version of
> MS-Windows from this millennium (no drivers available), while it's still
> working great on current Linux kernels.
agreed, I have the same problems with a creative (a well know vendor)
webcam. Stopped working on SP2.
The problem in windows (and linux closed-sourced drivers) is _much_ bigger
than it seems. Soon all CPUs will be 64-bit capable and dual core, and that
brings two problems: 64-bit-compatible drivers and SMP-safe drivers. I used
to have a cheap winmodem which would deadlock my smp machine. There're lots
of crappy windows drivers which haven't been even tested in a smp machine
it seems. If you buy a dual-core machine and your vendor has gone out of
bussines or the "support period" is expired you migh need to buy new
hardware :(
The 64-bit driver issue is bigger: Even HP has already a (somewhat long)
list of printers which HP is definitively _never_ going to support in 64 bit
platforms (and that's HP, you can imagine what small vendors are doing).
It seems that most of desktop hardware makers are supporting the 64 bit
windows platform just for new devices - unless you had 64 bit in mind when
you created it (which is not possible, because nobody knew what was going to
happen in the 64 bit desktop land until intel supported x86-64) supporting
64 bit may be very well impossible, since they need to port the drivers
of all the thousands of devices they've made through years, and the windows
platform doesn't make it easier (pointers are obviously 64-bit long in the
windows 64 bit platform but longs are still 32 bit for compatibility and
driver programmers don't find it helpful I've heard)
I wish there was opensource drivers for windows. Maybe the fact that some
companies are opening them in linux will make that easier in the future :/
next prev parent reply other threads:[~2005-11-07 17:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 13:56 Steven Rostedt
2005-11-04 15:10 ` Mark Knecht
2005-11-04 15:14 ` Paweł Sikora
2005-11-04 15:22 ` Steven Rostedt
[not found] ` <ec92bc30511040730g2ad412ddsb3ac63f701de6c97@mail.gmail.com>
2005-11-04 15:39 ` Anshuman Gholap
2005-11-06 23:46 ` Nix
2005-11-07 7:42 ` Arjan van de Ven
2005-11-07 12:42 ` Steven Rostedt
2005-11-07 12:55 ` Hugo Mills
2005-11-07 14:22 ` Paweł Sikora
2005-11-07 15:07 ` Paweł Sikora
2005-11-07 14:51 ` Ville Syrjälä
2005-11-07 15:50 ` Jerome Glisse
2005-11-07 16:24 ` Gerhard Mack
2005-11-07 16:35 ` Ian Romanick
2005-11-07 16:41 ` Ville Syrjälä
2005-11-07 14:24 ` Alan Cox
2005-11-07 13:59 ` Xavier Bestel
2005-11-07 16:17 ` Gerhard Mack
2005-11-07 15:20 ` Toon van der Pas
2005-11-07 15:31 ` Arjan van de Ven
2005-11-07 17:35 ` Steven Rostedt
2005-11-08 22:08 ` Matthias Andree
2005-11-08 22:18 ` John Stoffel
2005-11-08 22:37 ` Tue, 8 Nov 2005 23:37:43 +0100
2005-11-09 1:34 ` Alan Cox
2005-11-07 17:00 ` Diego Calleja [this message]
2005-11-07 17:30 ` Steven Rostedt
2005-11-07 17:44 ` Gerhard Mack
2005-11-07 17:53 ` Steven Rostedt
2005-11-07 17:56 ` Gerhard Mack
2005-11-07 18:01 ` Mark Knecht
2005-11-07 18:15 ` Steven Rostedt
2005-11-07 18:31 ` Mark Knecht
2005-11-07 19:08 ` Gerhard Mack
2005-11-07 19:09 ` Mark Knecht
2005-11-07 19:05 ` Lee Revell
2005-11-07 19:23 ` Mark Knecht
2005-11-07 19:47 ` Steven Rostedt
2005-11-12 9:11 ` Lee Revell
2005-11-07 18:19 ` Joel Jaeggli
2005-11-08 18:59 ` Stefan Seyfried
2005-11-08 19:06 ` Lennart Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051107180045.ec86a7f2.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=toon@hout.vanvergehaald.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®