: NVIDIA FreeBSD kernel feature requests
That is puzzling - I running using on a Nvidia Nforce 590 SLI based machine
with no problems using Raid - Mind you this Dell implementation uses only Raid0
- What release are you running? - I have had success With both 6.2, 7.0-Current
and AMD-6.2 and AMD
On Fri, Mar 30, 2007 at 10:16:37AM +0200 I heard the voice of
MOUILLE Jean Pierre Ext OF/DT, and lo! it spake thus:
. 1 RAID 5 for data on nForce chip, with 3 maxtor/seagate 250 GB
disks (~450 GB data)
ataraid(4):
CAVEATS
RAID5 is not supported at this time. Code exists, but it neither
Hello,
Do you plan for a driver for nForce 590sli RAID controller on FreeBSD ? The
disks are recognized but not the RAID arrays.
On Motherboard ECS KN3-SLI2, JMicron JMB363 driver is already included in
FreeBSD 6.2 (ar0) but in kernel, it goes up to nForce 4.
Perhaps have you got later
MOUILLE Jean Pierre Ext OF/DT [EMAIL PROTECTED] writes:
Do you plan for a driver for nForce 590sli RAID controller on
FreeBSD ? The disks are recognized but not the RAID arrays.
It's not so much a matter of writing a driver as one of teaching the
existing driver (ataraid) to recognize the
: NVIDIA FreeBSD kernel feature requests
Hello,
Do you plan for a driver for nForce 590sli RAID controller on FreeBSD ?
The disks are recognized but not the RAID arrays.
On Motherboard ECS KN3-SLI2, JMicron JMB363 driver is already included
in FreeBSD 6.2 (ar0) but in kernel, it goes
Hi I have got , a geforce 6600gt 256mb/ddr3
can you tell me ? if it will play hd games if ,I BUY a hd ready monitor, [EMAIL
PROTECTED]
your faithfully , d
___
freebsd-hackers@freebsd.org mailing list
On Sun, 02 Jul 2006 23:51:35 +0200
Michal Mertl [EMAIL PROTECTED] wrote:
Hi,
I'm going to reply to this, once, just to make my argument clear.
I think that this reaction wasn't called for. Modern GPUs are
extraordinarily complex HW and to write a decent driver will take
appropriate effort. I
I found your manifesto for free software interesting, although I didn't
really see anything new there so I snipped it. In my opinion, you can always
vote with your wallet, and if you feel that strongly about needing all the
parts of your system to be free, well, knock yourself out.
On the other
In message: [EMAIL PROTECTED]
Kip Macy [EMAIL PROTECTED] writes:
: Producing a driver for a GPU card, especially one that possibly converts
from
: GL-foo to foo appropriate to program and feed an ASIC on a video card, is
: quite different matter entirely.
:
: I'm all for open
On Monday 03 July 2006 00:02, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Christian Zander [EMAIL PROTECTED] writes:
: This summary makes an attempt to describe the kernel interfaces needed by
: the NVIDIA FreeBSD i386 graphics driver to achieve feature parity with
: the
John Baldwin wrote:
On Monday 03 July 2006 00:02, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Christian Zander [EMAIL PROTECTED] writes:
: This summary makes an attempt to describe the kernel interfaces needed by
: the NVIDIA FreeBSD i386 graphics driver to achieve feature
On Wednesday 05 July 2006 19:30, Sam Leffler wrote:
John Baldwin wrote:
On Monday 03 July 2006 00:02, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Christian Zander [EMAIL PROTECTED] writes:
: This summary makes an attempt to describe the kernel interfaces needed by
:
On Mon, Jul 03, 2006 at 08:42:42AM +0530, Joseph Koshy wrote:
In the less benign one that convenient binary driver that
you loaded into the kernel would contain a silent security
vulnerability. Google for Sony DRM rootkit.
I think the difference here is that NVIDIA are a little more trusted
Producing a driver for a GPU card, especially one that possibly converts from
GL-foo to foo appropriate to program and feed an ASIC on a video card, is
quite different matter entirely.
I'm all for open source drivers, and would also encourage NVIDIA to continue
to reconsider their closed source
On Sun, 2 Jul 2006, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Kip Macy [EMAIL PROTECTED] writes:
: IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Can you describe the proper semantics here? A cdev is a cdev, and when we
do things like dup we
On Sun, 2 Jul 2006, Sam Smith wrote:
On Sun, 2 Jul 2006, Michal Mertl wrote:
And - again - it will probably take a couple of very skilled
programmers' years' time to write good driver from scratch.
It took someone far less than that
On Sun, Jul 02, 2006 at 10:02:17PM -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Christian Zander [EMAIL PROTECTED] writes:
: This summary makes an attempt to describe the kernel interfaces needed by
: the NVIDIA FreeBSD i386 graphics driver to achieve feature parity
On Mon, Jul 03, 2006 at 10:33:29AM +0100, Robert Watson wrote:
On Sun, 2 Jul 2006, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Kip Macy [EMAIL PROTECTED] writes:
: IIRC lack of per instance cdevs also limits Freebsd to one vmware
instance.
Can you describe the
On Thu, 29 Jun 2006 13:12:31 +0200
Christian Zander [EMAIL PROTECTED] wrote:
Hi,
I just saw an article on OSNews about this, seems I missed it.
NVIDIA has been looking at ways to improve its graphics driver for the
FreeBSD i386 platform, as well as investigating the possibility of adding
Miguel Mendez wrote:
On Thu, 29 Jun 2006 13:12:31 +0200
Christian Zander [EMAIL PROTECTED] wrote:
Hi,
I just saw an article on OSNews about this, seems I missed it.
NVIDIA has been looking at ways to improve its graphics driver for the
FreeBSD i386 platform, as well as investigating
On Sun, 2 Jul 2006, Michal Mertl wrote:
And - again - it will probably take a couple of very skilled
programmers' years' time to write good driver from scratch.
It took someone far less than that
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_nfe.c
That's their commercial decision - as a result, if you
their cards, you may end up with a particularly expensive
paperweight the day they decide you need to buy a new card
for your new version of freebsd which has different
internals; or someone finds bugs in their drivers that
they wont fix.
In message: [EMAIL PROTECTED]
Kip Macy [EMAIL PROTECTED] writes:
: IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Can you describe the proper semantics here? A cdev is a cdev, and
when we do things like dup we just copy the reference to that cdev.
This
In message: [EMAIL PROTECTED]
Christian Zander [EMAIL PROTECTED] writes:
: This summary makes an attempt to describe the kernel interfaces needed by
: the NVIDIA FreeBSD i386 graphics driver to achieve feature parity with
: the Linux/Solaris graphics drivers, and/or required to make
Kip Macy writes:
| IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Really? Don't tell my vmware multiple instances! I used to run 10 on
one FreeBSD host.
Doug A.
___
freebsd-hackers@freebsd.org mailing list
WOW THATS GREAT DOUG! \0/ - it didn't work for me.
-Kip
On 6/30/06, Doug Ambrisko [EMAIL PROTECTED] wrote:
Kip Macy writes:
| IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Really? Don't tell my vmware multiple instances! I used to run 10 on
one FreeBSD host.
Kip Macy writes:
| WOW THATS GREAT DOUG! \0/ - it didn't work for me.
This was with the last patched driver for vmware 2. I'm not sure if
it every made it into the port.
http://www.mindspring.com/~vsilyaev/vmware/files/changes
28 Jan 01 Version 0.99-1-0.22
Support for multiple vmware
Hi all,
NVIDIA has been looking at ways to improve its graphics driver for the
FreeBSD i386 platform, as well as investigating the possibility of adding
support for the FreeBSD amd64 platform, and identified a number of
obstacles. Some progress has been made to resolve them, and NVIDIA would
like
Christian Zander wrote:
Hi all,
# Task:implement mechanism to allow character drivers to
maintain per-open instance data (e.g. like the Linux
kernel's 'struct file *').
Motivation: allows per thread NVIDIA notification delivery; also
IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
-Kip
On 6/29/06, Oleksandr Tymoshenko [EMAIL PROTECTED] wrote:
Christian Zander wrote:
Hi all,
# Task:implement mechanism to allow character drivers to
maintain per-open instance
On Thu, Jun 29, 2006 at 09:32:42AM -0700, Kip Macy wrote:
IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
-Kip
On 6/29/06, Oleksandr Tymoshenko [EMAIL PROTECTED] wrote:
Christian Zander wrote:
Hi all,
# Task:implement mechanism to allow
On Thu, Jun 29, 2006 at 12:49:10PM -0400, Alexander Kabaev wrote:
On Thu, Jun 29, 2006 at 09:32:42AM -0700, Kip Macy wrote:
IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
-Kip
On 6/29/06, Oleksandr Tymoshenko [EMAIL PROTECTED] wrote:
Christian
Alexander Kabaev wrote:
WHY it smells like a hack? It was designed precisely to do that. I am
using cloned devices in our product with great success. Every client
opening 'magic' device gets its own exclusive cloned device instance
and everything works like a charm. I am yet to hear any single
Christian Zander wrote:
On Thu, Jun 29, 2006 at 12:49:10PM -0400, Alexander Kabaev wrote:
On Thu, Jun 29, 2006 at 09:32:42AM -0700, Kip Macy wrote:
IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
-Kip
On 6/29/06, Oleksandr Tymoshenko [EMAIL PROTECTED]
34 matches
Mail list logo
