NVidia module, so that most likely changes a lot of
things. I'll see if I can find time tonight to test 2.6.25-rc3 + nv,
and report back.
--
Kind regards
Klaus S. Madsen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
find time tonight to test 2.6.25-rc3 + nv,
and report back.
--
Kind regards
Klaus S. Madsen
--
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
> (everyone gets this btw - some weird bluetooth-vs-usb thing which we don't
> know how to fix).
This is actually fixed by upgrading to the newest version of the BIOS.
I'm currently running version 7LETA7WW (2.07), and haven't seen the
problem since I upgraded.
--
Med venlig hilsen
Klaus
bluetooth-vs-usb thing which we don't
know how to fix).
This is actually fixed by upgrading to the newest version of the BIOS.
I'm currently running version 7LETA7WW (2.07), and haven't seen the
problem since I upgraded.
--
Med venlig hilsen
Klaus S. Madsen
--
To unsubscribe from this list
ing the mapped memory and do not change when there have been
> > no write references between the mmap() and msync() system calls.
So essentially the problem is that mtime stamps are _never_ changed when
the file is only modified through mmap. Not even when calling msync().
--
Kind regards,
references between the mmap() and msync() system calls.
So essentially the problem is that mtime stamps are _never_ changed when
the file is only modified through mmap. Not even when calling msync().
--
Kind regards,
Klaus S. Madsen
--
To unsubscribe from this list: send the line
6 matches
Mail list logo
