;
> That's very sad news. :-(
>
Well, it's not entirely by choice. I have yet to find a system on
which FreeBSD comes back from S3. In any case, the driver paths
taken on FreeBSD are nearly identical to those taken on
Linux, so given a sufficiently stable host, mileage should be the
vers if you're starting it from scratch following
an S4 cycle, or an S3 cycle that involved a POST (either
issued by the SBIOS or via software).
When using the NVIDIA driver, you will need to make sure that
you're using 256.44, you'll need to be running X at the time of
entry to S
th the driver's notification mechanism on FreeBSD 5.3. I'll
need to do more testing and check what implications the mechanism has
(locking, etc.), but it looks like it's a good match.
Thanks,
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
>
> &
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 d
oshenko <[EMAIL PROTECTED]> wrote:
> > >Christian Zander wrote:
> > >> Hi all,
> > >> # Task:implement mechanism to allow character drivers to
> > >> maintain per-open instance data (e.g. like the Linux
> > >
U overhead for notification delivery
from the NVIDIA kernel module to the X driver and to
OpenGL.
Priority: should translate to improved X/OpenGL performance.
Status: has not been started.
Thanks,
--
christian zander
[EMAIL PROTECTED]
_
ath you suspect really is
the one taken in the case of this failure. Is this problem easily
reproducible on your machine? If so, how and with what hard/software
combination?
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Sat, Sep 21, 2002 at 06:50:09AM +0200, Christian Zander wrote:
>
> Maybe it helps to get an idea of what memory allocation sizes we
> are talking about for the NVIDIA driver. For every single OpenGL
> client in the system memory case (no AGP), the resource manager
> has to al
es) and sized in multiples of 1MB.
Even in the AGP memory case, several pages of DMA memory need to
be allocated from general system memory.
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
MTRR support on these processors.
--
christian zander
[EMAIL PROTECTED]
diff -ru cvs/4.6/i386/i386/i686_mem.c sys/i386/i386/i686_mem.c
--- cvs/4.6/i386/i386/i686_mem.cFri Jul 5 16:33:28 2002
+++ sys/i386/i386/i686_mem.cFri Jul 5 16:52:59 2002
@@ -595,7 +595,7 @@
{
/* Try for
>
> Any chance of getting that from BSD/OS? If not, perhaps we could
> reimplement.
>
The Linux gdb kernel stub (kgdb.sourceforge.net) also supports this
behaviour, you don't need to detach explicitely.
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL P
"PnP OS" in the BIOS.
>
Something along these lines occured on my notebook in response to a
kernel configuraton entry for the second serial port on my notebook.
While the port appears to be advertised, it doesn't actually seem to
exist.
--
christian zander
[EMAIL PROTECTED]
To Unsubscrib
honeymoon, etc), so please
> continue to work around my sloth.
>
No problem at all, real life takes preference.
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rwarded, etc), but it is very useful nevertheless.
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
change a few lines in gdb to make it work, this is
included in the original patch, but not in the one I attached.
--
christian zander
[EMAIL PROTECTED]
Binary files 4.5/compile/DEBUG/kernel.debug and sys/compile/DEBUG/kernel.debug differ
diff -ruN 4.5/conf/files sys/conf/files
--- 4.5/conf/fi
of information or have other hints.
Thanks,
--
christian zander
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
16 matches
Mail list logo
